As you know Scrum is an iterative and incremental agile software development method for managing software project. Scrum planning start with product backlog identification and story points definitions.
The product backlog is an ordered list of "requirements" that is maintained for a product.The product backlog contains rough estimates of both business value and development effort, these values are often stated in story points using a rounded Fibonacci sequence
Requirements of Project has to be divided into Stories ( need to give story points for each story)
Story should be divided into one or more Tasks ( each task should be given time estimates in hours) Always create a Task to Story even the story is very small and need only single task .Give the estimates in Task.
Regarding Points Vs Time, as there is no fixed definition to exact match between the story points vs time frame. we can follow the below conventions while defining the story points
eg: if the estimated time for a story is 1 day , it will have 2 story points.
if the estimated time for a story is 1.5 day , it will have 3 story points.
Stories are Business Use Case which are standalone in Nature
Three types of Stories
1) Client Side + Server Side changes
eg: server will expose some services, client will call those services and show the results in UI
In this case , there will be some tasks for client and some tasks for server.
2) Only Client Side
eg: customization of UI like styles,fonts etc changes
3) Only Server Side
eg: Utility APIs
*each story should be independently testable.
Depending on your team size , you can allocate certain number of story points for a specific sprint.
remaining stories, will move to the next sprint.
*A sprint is the basic unit of development in Scrum. Sprints last between one week and one month.
The product backlog is an ordered list of "requirements" that is maintained for a product.The product backlog contains rough estimates of both business value and development effort, these values are often stated in story points using a rounded Fibonacci sequence
Requirements of Project has to be divided into Stories ( need to give story points for each story)
Story should be divided into one or more Tasks ( each task should be given time estimates in hours) Always create a Task to Story even the story is very small and need only single task .Give the estimates in Task.
Regarding Points Vs Time, as there is no fixed definition to exact match between the story points vs time frame. we can follow the below conventions while defining the story points
| Story Points | Hours/Days (max) | comments |
|---|---|---|
| 1 | 3 hr | total estimated time for all the tasks created under this story point should not exceed 3 hrs |
| 2 | 1 days | total tasks time should not exceed 1 day |
| 3 | 2 days | total tasks time should not exceed 2 day |
| 5 | 3 days | total tasks time should not exceed 3 day |
| 8 | 5 days | total tasks time should not exceed 5 day, extreme case |
| 13 | 8 days | total tasks time should not exceed 8 day, not acceptable ( too extreme case ) |
eg: if the estimated time for a story is 1 day , it will have 2 story points.
if the estimated time for a story is 1.5 day , it will have 3 story points.
Stories are Business Use Case which are standalone in Nature
Three types of Stories
1) Client Side + Server Side changes
eg: server will expose some services, client will call those services and show the results in UI
In this case , there will be some tasks for client and some tasks for server.
2) Only Client Side
eg: customization of UI like styles,fonts etc changes
3) Only Server Side
eg: Utility APIs
*each story should be independently testable.
Depending on your team size , you can allocate certain number of story points for a specific sprint.
remaining stories, will move to the next sprint.
*A sprint is the basic unit of development in Scrum. Sprints last between one week and one month.
No comments:
Post a Comment