8 Steps to a Definition of Done in JIRA

Summary:
This article explain what is DoD and its importance. DoD is a set of criteria that must be met before a
task can be called Done/Completed. The criteria is set by the Product Owner and will be applied
globally for all tasks. The article also explain on how to implement DoD in JIRA.
Action Items:
Currently our process doesnt have any standard DoD. We called a task Done if has been tested and
reviewed by Designer. And also we didnt have acceptance criteria which is bad. I suggest that we should
implement this DoD in JIRA. Product Owner must define the DoD globally and Acceptance Criteria for
each task. All teams member must follow this DoD and Acceptance Criteria, and this should not be
changed during the Sprint.

Metrics for a Scrum Team
Summary:
Metrics in Scrum will indicate how the team are performing. One example is Velocity, this metric will
show the capability of the team to complete story point in one sprint. This can help the team to make
decision on how much commitment they can make for next sprints. On conclusion, some metrics will
help the team self-manage their work and increase their effectiveness in delivering value in the form of
working tested software.
Action Items:
We should introduce metrics to our process. It can help us to measure our performance and making
plan for next sprint.

How To: Capacity planning with JIRA
Summary:
Capacity planning is ensuring that everyone on the team have enough work for the entire iteration. In
capacity planning we should estimate every task in man-hours not just in story points. When we have
the estimation in hours, then it will be easy to track the progress each task. In JIRA we can activate the
time tracking system. Each team member must log their work regularly to JIRA. When the sprint end we
can see how we are performing, we can see which task is miss the estimation and finding the problem of
those task. And will help us for planning for the next sprint.
Action Items:
We must activate time tracking in JIRA. And we must estimate our task using hours not only in story
points. Because in some article I read that same story point can be different in hours. When the time
tracking is activated team member must log their work regularly, at least every day. When we have time
tracking, we will be able to see how each task progressing daily.

60 Second Scrum Better Retrospectives
Summary:
Better retrospective should exclude stakeholder. And we can use different technique, like silent writing.
And lastly we can have retrospection in open air to change the atmosphere of the meeting.
Action Items:
When the sprint ends we must have discussion on how the sprint going. The meeting should exclude the
stakeholder including PM. Then we should list what went good and what went bad. And should have
come with conclusion on how we should improve

Backlog Refinement Meeting
Summary:
This video shows an example how the backlog refinement meeting should be done. The product owner
must prioritize the backlog, cut the backlog into smaller items if possible, and define the acceptance
criteria for each item. And the team can estimate the complexity of backlog item.
Action Items:
We should have Backlog Refinement Meeting, so we know what we will do in the next sprint. We also
will have better understanding of the tasks.