<\/p>\n\n\n\n
Story points are related to time, but they are not the same as time.<\/strong><\/p>\n\n\n\n A story point<\/strong> is a relative estimate of the size of a user story. It considers:<\/p>\n\n\n\n Your slides explain that story points are used for relative sizing<\/strong> and consider complexity, effort, uncertainty, and dependencies, while hours are better used for task breakdown inside a sprint.<\/p>\n\n\n\n A 5-point story does not always mean 5 hours<\/strong>. It means the team believes it is roughly bigger than a 3-point story and smaller than an 8-point story.<\/p>\n\n\n\n Story points become useful over multiple sprints through velocity<\/strong>.<\/p>\n\n\n\n Velocity = average story points completed per sprint.<\/strong><\/p>\n\n\n\n For example:<\/p>\n\n\n\n Average velocity = about 24 story points per sprint<\/strong>.<\/p>\n\n\n\n So if the remaining backlog has 96 story points<\/strong>, the team may estimate:<\/p>\n\n\n\n 96 \u00f7 24 = 4 sprints<\/strong><\/p>\n\n\n\n So story points help forecast time at the sprint\/release level<\/strong>, not at the individual-hour level.<\/p>\n\n\n\n You can say:<\/p>\n\n\n\n Story points are not hours. Story points are a relative measure of story size. After a team completes a few sprints, we can use their average velocity to estimate how many sprints are needed to finish the backlog.<\/p>\n<\/blockquote>\n\n\n\n Avoid saying:<\/p>\n\n\n\n 1 story point = 1 hour<\/p>\n<\/blockquote>\n\n\n\n That is usually not correct.<\/p>\n\n\n\n Better:<\/p>\n\n\n\n For this team, based on past performance, 20 story points may usually fit into a 2-week sprint.<\/p>\n<\/blockquote>\n\n\n\n So the relationship is:<\/p>\n\n\n\nFactor<\/th> Meaning<\/th><\/tr><\/thead> Effort<\/td> How much work may be required<\/td><\/tr> Complexity<\/td> How difficult the work is<\/td><\/tr> Uncertainty<\/td> How unclear or risky the work is<\/td><\/tr> Dependencies<\/td> Whether the story depends on other people, teams, systems, or information<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Simple example<\/h3>\n\n\n\n
Story<\/th> Story points<\/th> Possible meaning<\/th><\/tr><\/thead> Add a button label change<\/td> 1 point<\/td> Very small, low risk<\/td><\/tr> Create login page<\/td> 3 points<\/td> Moderate work<\/td><\/tr> Build password reset with email verification<\/td> 5 points<\/td> More effort and testing<\/td><\/tr> Build recommendation engine<\/td> 13 points<\/td> Large, complex, uncertain<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n How story points connect to time<\/h3>\n\n\n\n
Sprint<\/th> Completed story points<\/th><\/tr><\/thead> Sprint 1<\/td> 22<\/td><\/tr> Sprint 2<\/td> 26<\/td><\/tr> Sprint 3<\/td> 24<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Explanation<\/h3>\n\n\n\n
\n
Good classroom warning<\/h3>\n\n\n\n
\n
\n