While assigning story points in any sprint, every single time one of the team members asks same question:
On what basis story points to be assigned?
I do not have perfect answer but I have come up with following list of factors which should be considered while assigning story point.
• Technical complexity
• Business complexity
• Efforts required to complete the story ( dev +test+ deployment + ...)
• Dependency within scrum team
• Dependency within project (A project might have multiple scrum teams)
• Dependency across different projects ( some of the projects might be running on waterfall model)
• Clarity in requirements
• Clarity in scope
• Urgency of story
While taking help from google, biggest issue I observe that most of the Agile/Scrum experts are talking about what not affect story points but not the what affect.
One more central themes I noticed with respect to story point: In a Scrum team relative value of story points for each story is important not the absolute value.
Any thoughts ?
• Technical complexity
• Business complexity
• Efforts required to complete the story ( dev +test+ deployment + ...)
• Dependency within scrum team
• Dependency within project (A project might have multiple scrum teams)
• Dependency across different projects ( some of the projects might be running on waterfall model)
• Clarity in requirements
• Clarity in scope
• Urgency of story
While taking help from google, biggest issue I observe that most of the Agile/Scrum experts are talking about what not affect story points but not the what affect.
One more central themes I noticed with respect to story point: In a Scrum team relative value of story points for each story is important not the absolute value.
Any thoughts ?
Posts
No comments:
Post a Comment