Agile scrum
- 1. Agile Scrum Understanding & Useful Details - By Venkatesh Gurupura Pai
- 2. What is scrum? • The process of breaking & releasing the product to the market phase wise. • Every phase is called as sprint which can be of the duration of 1 to 4 weeks. • This iteration of sprints are repeated with Increment being done for the shippable product during each sprint.
- 3. Roles in Scrum 1. Product Owner : – Writing & Maximising the value of Product Backlog. – Understand & work with different stake holders – Represents the stakeholders & customers to the Development team. 2. Scrum Master : – Making sure Team is working together. – Promotes & supports scrum as defined in the scrum guide. – Provides guidance & support for the scrum team & Organization. – Coordinates with other teams. 3. Scrum Team – All developers, Testers etc. – Getting things done.
- 4. Documents/Artifacts 1. Product Backlog – Created by Product owner – Holds the requirement of the Product. – Each requirement is written in terms of user story. – User story list is not fully defined at the beginning. The list might get increased or decreased as the Sprint improves. This list evolves & changes priority in every sprint. – User story format : "As a ________________ I need ________ so that __________" – User story contains the requirement & acceptance criteria. – This user story allows the right amount of estimations to perform the task.
- 5. Documents/Artifacts contd.. 2. Sprint Backlog – Plan for current sprint. – Highest prioritized user story gets into the Sprint backlog. – This committed for the next sprint. – Adapted by development team to work on – List of tasks to deliver the Product catalogue against Sprint Goal 3. Increment – Sum of all product backlog items completed during the sprint. – The product is the sum of all increments. – It usable & it works. – Must be DONE 4. Burn Down Chart – Shows the progress of the task. – The chart must reach zero point as work is completed.
- 6. Sprint Ceremonies 1. Backlog Grooming – Grooming of User stories present in the Product Backlog. – Understanding the requirement in detail with the help of Product Owner. 2. Spring Planning – Product Catalogue is inspected. – Sprint Goal is decided & Sprint Backlog is prepared. – Take the items from Product Backlog & put it into the Sprint backlog. Have discussion with scrum team. – Tasks are created against each user story. – Task ownership is performed.
- 7. Sprint Ceremonies contd.. 3. Daily Scrum – Daily stand up call – Inspect progress toward the Sprint Goal. – Inspect how progress is trending in completing work in the Sprint Backlog. – Discussion regarding things team is working from previous stand up call 4. Sprint Review – Performed during end of sprint – Scrum Team & Business stake holders are involved. – Team provides demo to the customer reg product – Discussion happened regarding the betterment of the product – Product Backlog is updated at the end of the Sprint Review
- 8. Sprint Ceremonies contd.. 5. Sprint Retrospective – Full Scrum Team(including Product owner) is involved in the meeting. – Discussion about the previous sprint. – Improvement for next sprint.
- 10. Sprint work flow Product Backlog Backlog Grooming Sprint Planning Sprint Backlogs Sprint Daily Sprint meeting Potential Shippable Product Sprint Review Retrospective 1 Hour 1 Hour 15 Minutes 1 Hour 1 Hour GE MSAT Internal SI # Ceremony/Doc Purpose 1 Product Backlog Written by Product Owner. List of functionality (user stories) that can get into Product. 2 Backlog Grooming Understanding the user stories present in Product Backlog. 3 Sprint Planning Discussion between Product owner, Scrum Master & team reg what user stories(from Product Backlog) can get into coming sprint. 4 Sprint Backlogs Output of Spring Planning. This is the list of user stories which is committed for the following Sprint. Team must have solid understanding on the requirement of each user story. 5 Sprint 1-3 weeks' time line to implement the Sprint Backlog. 6 Daily Sprint meeting Daily stand-up call 7 Potential Shippable Product Outcome of each sprint 8 Sprint Review Occurs at the end of the sprint. Demo is given to the Product Owner. 9 Retrospective What team can do to improve the process.
- 11. Tasks & Story Points • Tasks – Each functionality required to perform the user story. – User story is broken down in multiple tasks like UI development, Services code, Testing, DB component, Integrations etc.. • Story Point – Complexity calculation – Complexity levels • Small, Low, Medium, Large • Fibonacci series – 0,1,1,2,3,5,8,13,21.. – Can not exceed the Story point > 18.
- 12. Velocity • Total sum of story points that can be taken for each sprint. Sprint Duration 10 days Team Size 5 Hours per day 7 Total capacity for Sprint 350 Hours
- 13. Burn Down Chart Sprint Day Expected Burn down Actual Burn down 07/5/2018 315 (350-35) 305 08/5/2018 280 288 09/5/2018 245 255 10/5/2018 210 219 11/5/2018 175 189 14/5/2018 140 155 15/5/2018 105 120 16/5/2018 70 90 17/5/2018 35 55 18/5/2018 0 38 0 50 100 150 200 250 300 350 Burn Down Chart Expected Burn down Actual Burn down – Shows the progress of the task. – The chart must reach zero point as work is completed.
- 14. Responsibility of each Scrum Player • Understand the requirement well during Backlog grooming • Be transparent • Take ownership of User stories/tasks during Sprint Planning. • Log the work hours in Jira for each tasks. • Inform Scrum master regarding planned leaves well in advance.
- 16. Sample Scrum Ceremonies Schedule CEREMONY MEETING SCHEDULE Backlog Grooming Every Monday & Wednesday of 2nd week of previous sprint Sprint Planning Every Monday of 1st week of current sprint Daily Scrum Daily Sprint Review Every Friday of 2nd week of current sprint Sprint Retrospective Every Monday of 1st week of each(next) sprint GE MSAT Internal SUN MON TUES WED THUR FRI SATUR 29 30 Sprint0 Backlog Grooming 1 2 Sprint0 Backlog Grooming 3 4 5 6 7 Sprint0 Sprint Planning 8 9 10 11 12 13 14 Sprint1 Backlog Grooming 15 16 Sprint1 Backlog Grooming 17 18 Sprint0 Sprint Review 19 20 21 Sprint0 Sprint Retrospective Sprint1 Sprint Planning 22 23 24 25 26 27 28 Sprint2 Backlog Grooming 29 30 Sprint2 Backlog Grooming 31 1 Sprint1 Sprint Review 2
- 17. Thank you