From the course: Agile at Work: Planning with Agile User Stories
Unlock the full course today
Join today to access over 24,100 courses taught by industry experts.
Ready to implement state
From the course: Agile at Work: Planning with Agile User Stories
Ready to implement state
- Over the project's timeline, most identified stories will become highly prioritized and ordered towards the top of the backlog. Once a story is high in priority and a candidate to pull into the next iteration or two, it needs to be in the state ready to implement. For the story to be in this state, the team must invest time to discuss it, and acceptance criteria must be written. Stories that meet a team's definition of ready are ready to be implemented. This helps ensure that the team has a high level of confidence and probability that if they pull a story into the workflow, they understand what is needed. The product owner constantly refines the backlog, and the team collaborates towards the end of each iteration to ensure readiness to move into the next iteration. This workflow is perpetual for the remainder of the project.
Contents
-
-
-
-
-
(Locked)
Ready to implement1m 56s
-
(Locked)
Identified state1m 15s
-
(Locked)
Sized state1m 5s
-
(Locked)
Relative sizing techniques3m 34s
-
(Locked)
Team estimation5m 37s
-
(Locked)
Size with points vs. estimate with hours2m 13s
-
(Locked)
Understand velocity3m 10s
-
(Locked)
Prioritized state52s
-
(Locked)
Input to backlog prioritization and planning3m 25s
-
(Locked)
Ready to implement state1m
-
(Locked)
Acceptance criteria4m 38s
-
(Locked)
Story quality and the definition of ready4m 39s
-
(Locked)
-
-