From the course: Agile at Work: Planning with Agile User Stories
Unlock this course with a free trial
Join today to access over 25,300 courses taught by industry experts.
Sized state
From the course: Agile at Work: Planning with Agile User Stories
Sized state
- The initial sizing of our stories typically occurs early in the project, once most have been identified. At this point, the teams typically will hold an event where they assign a sizing value to stories. Over time, with experience, most teams can size stories quickly and efficiently. However, the size of a story is not cast in stone. As we learn more through doing a little bit of work in each iteration, teams update assigned sizing values for some of the stories. While stories are being identified, the team may have done some preliminary sizing. However, at this point, they can conduct a sizing event for all the identified stories to do a relative comparison together. Remember, the team does not need to identify all the stories that may be required. Some will be discovered from an ongoing perspective as we learn more, while large stories may be split into two or more stories. Those stories can be sized as needed.
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)
-
-