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.
Size with points vs. estimate with hours
From the course: Agile at Work: Planning with Agile User Stories
Size with points vs. estimate with hours
- There's a difference between sizing and estimating. In the video, Relative Sizing Techniques, we compared stories to each other and then assigned a numeric value called a story point. Are you wondering why hours were not used? This is a common question with teams new to Agile. Estimating is generally individually focused in an absolute value. For example, tasks are usually estimated in hours by the person who will do the task. In Agile approaches, sizing compares relative amounts of effort between different work items, such as a user and technical story. Story points allow individuals with different skills, experience levels, and backgrounds to agree on a size. When done by different team members, a story will take many tasks to complete a task is typically something a single team member will take on and complete. Let me share an example. I'm an avid cyclist and I ride a few times per week. One of the Agile coaches I regularly work with also cycles. We were planning our first ride…
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)
-
-