From the course: Agile at Work: Planning with Agile User Stories
Unlock the full course today
Join today to access over 24,400 courses taught by industry experts.
Ready to implement
From the course: Agile at Work: Planning with Agile User Stories
Ready to implement
- Now that you know how to write a story, let's look at how a story gets implemented. Like many things, stories move through a lifecycle. The first part of that lifecycle is when a story is ready to implement. The first step is to identify stories. Most stories are identified early in the project's timeline. Once most of the stories for our scope of work have been identified, the next step is to size them. Sizing the complexity and level of effort is essential for prioritization and planning. Once the team has assigned a size value, the product owner can use that and other inputs, such as business value, risk, dependencies, et cetera, to make an initial path at prioritizing the backlog of stories. Prioritization provides flexibility and decisions on what to do next. Lower-priority stories can wait to have more investment made in them as we get validated learning on those we're implementing first. At some point, most stories become a high priority, ordered towards the top of 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
-
-
-
-
-
(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)
-
-