From the course: Agile Analysis Weekly Tips
Unlock this course with a free trial
Join today to access over 22,600 courses taught by industry experts.
Definition of ready/done
From the course: Agile Analysis Weekly Tips
Definition of ready/done
- Do you wish you had a checklist for knowing if your user stories are ready for the team to work on? And when to know if the team is done? Well, it exists, and it's a set of Agile techniques used on scrum teams and it can apply to other Agile ways of working as well. It's called a Definition of Ready and a Definition of Done. Definition of Ready and Definition of Done are checklists that the team works on together. They help the team determine guidelines for when backlog items are ready and when backlog items are done. Let's start with Definition of Ready. Having a good Definition of Ready helps the product owner and business analyst know what pre-conditions make the user story ready for the team to work on. Here are some common things that teams typically put in their Definition of Ready. The user story is understandable to the team. The acceptance criteria is elaborated and clear to the team. The team has estimated the user story and feels they can commit to getting it done. The…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
A healthy backlog2m 4s
-
(Locked)
Who writes backlog items?2m 57s
-
(Locked)
Know your agile business analyst (BA) and product owner roles2m 56s
-
(Locked)
Effective prioritization3m 22s
-
(Locked)
Making feedback loops a focus2m 47s
-
(Locked)
Focus on customer experience3m 41s
-
(Locked)
Collaborate on testing2m 30s
-
(Locked)
Agile planning: Five levels2m 43s
-
(Locked)
Keep the user at the center2m 32s
-
(Locked)
Keep the user action precise2m 45s
-
(Locked)
Work the acceptance criteria4m 5s
-
(Locked)
Collaborate with others2m 42s
-
(Locked)
Make user stories feedback-able2m 18s
-
(Locked)
Definition of ready/done2m 39s
-
(Locked)
Personas1m 48s
-
(Locked)
Primary personas3m 16s
-
(Locked)
Product hierarchy3m 9s
-
(Locked)
What needs to be documented?3m 41s
-
(Locked)
Experiments2m 4s
-
(Locked)
Hypothesis3m
-
(Locked)
User journey mapping2m 30s
-
(Locked)
Story mapping3m 10s
-
(Locked)
Understanding pain points3m 25s
-
(Locked)
Defining what success looks like2m 35s
-
(Locked)
Force rank prioritization3m 54s
-
(Locked)
Identifying user empathy2m 48s
-
(Locked)
Stay ahead of backlog refinement2m 51s
-
(Locked)
Working the scrum master relationship as a product owner2m 7s
-
(Locked)
Saying no to stakeholders2m 47s
-
(Locked)
Leveraging user feedback2m 45s
-
(Locked)
When to let the team ponder2m 55s
-
(Locked)
Asking the team for alternatives2m 12s
-
(Locked)
Information radiators for product owners4m 2s
-
(Locked)
Metrics product owners care about2m 46s
-
(Locked)
Visual backlog management for product owners3m 6s
-
Swarming on current work2m 48s
-
(Locked)
Making your roadmap and release plan visual3m 7s
-
(Locked)
Observing customers3m 55s
-
(Locked)
Dealing with user story creep2m 56s
-
(Locked)
User story splitting patterns3m 42s
-
(Locked)
Delivering value over staying busy2m 8s
-
(Locked)
Solving problems over building features2m 5s
-
(Locked)
Needs vs. guesses3m 3s
-
(Locked)
Planning with stakeholders (mid to long term)2m 59s
-
(Locked)
Encouraging swarming and finishing2m 40s
-
(Locked)
Focus on the problem or outcome, not the solution3m 13s
-
(Locked)
Managing stakeholder expectations of MVP2m 49s
-
(Locked)
Analyzing story maps for gaps4m 10s
-
(Locked)
Outcomes over outputs2m 59s
-
(Locked)
Defining good outcomes2m 48s
-
(Locked)
Create an agile project charter2m 51s
-
(Locked)
Test early and often, even as a product owner3m 30s
-