1. 1. Priyanka Wadhwa Software Consultant Priyanka Wadhwa Software Consultant
2. 2. What is Scrum? Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" Scrum to improve the profession of software development, up to the level of the enterprise agility of organizations. Scrum is an iterative and incremental agile software development methodology for managing product development. It defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" Scrum to improve the profession of software development, up to the level of the enterprise agility of organizations.
3. 3. Roles A Scrum team has three roles: Product Owner -- holds the vision for the product ScrumMaster -- helps the team best use Scrum to build the product Development team -- builds the product
4. 4. Scrum Framework Product owner creates a wish list Product Backlog. During Sprint Planning, Team picks a small chunk of list from Product Backlog Sprint Backlog. Team has a certain amount of time Sprint (of 1 4 weeks) to complete its work. Also, It meets each day to access its progress Daily Scrum. Scrum Master keeps the team focused of its goal. At the end of Sprint, the work becomes deliverable. Sprint ends with a Sprint Review and Retrospective. A new Sprint, another sprint backog.
5. 5. Product Backlog v/s Sprint Backlog
6. 6. Key Differences Item Product Backlog Sprint Backlog Level of detail Less detailed Very detailed Estimation units Story Points Hours Document ownership Product Owner Team Revised Weekly Daily Duration Project Sprint Workbook Product Backlog workbook Iteration Backlog workbook
7. 7. User story User story capture a description of a software feature from an end-user perspective. User story capture a description of a software feature from an end-user perspective.
8. 8. The user story describes the type of user, what they want and why. The user story describes the type of user, what they want and why.
9. 9. Theme, Epic and Story
10. 10. Theme : groups of related stories. They do not need to encapsulate a specific work flow or be delivered together. Epic : big user story. business value isn't realized until the entire epic is complete. Story : a self-contained unit of work. Theme : groups of related stories. They do not need to encapsulate a specific work flow or be delivered together. Epic : big user story. business value isn't realized until the entire epic is complete. Story : a self-contained unit of work.
11. 11. Story Points
12. 12. Story Points Story points arent a measure of the time needed to complete a feature but a measurement of a features size relative to other features. We may not have enough information to estimate the time to create a feature, but you can immediately begin to compare the sizes of features to each other to determine a relative size.
13. 13. Story point estimation is in Fibonacci scale, which sums the previous two numbers to derive the next number in the sequence. The sequence looks like this: 1, 2, 3, 5, 8, . The main benefit of the Fibonacci scale is that enough separation exists between the numbers to prevent the team from squabbling over slight differences. For example, if the scale was 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, team members might debate whether a feature was a 7 or an 8. Its easier for team members to reach agreement if the scale jumps from 5 to 8.
14. 14. Velocity Velocity is the number of story points completed by a team in an iteration. Calculating Velocity : Our team delivers 3 user stories. The sum of the story points equals 20. Our velocity is then 20. If, in the next iteration, our team delivers 30 story points, then our average velocity is 25, or (20 SP + 30 SP) divided by 2 iterations = 25 SP.
15. 15. Story with Sub-task
16. 16. Sprint Board
17. 17. Sprint Report (Burndown Chart)
18. 18. Sprint Demo During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting. Ideally, the team has completed each product backlog item brought into the sprint, but it's more important that they achieve the overall goal of the sprint. During the sprint review, the project is assessed against the sprint goal determined during the sprint planning meeting. Ideally, the team has completed each product backlog item brought into the sprint, but it's more important that they achieve the overall goal of the sprint. At the end of each sprint, a sprint review meeting is held.
19. 19. Retrospective
20. 20. Discussions
21. 21. Scrum Meetings Daily Scrum
22. 22. Scrum Cycle
23. 23. Demo