Agile Scrum Mastery: Learn How To Bring Complex Projects To life!
0 likes42 views
The document outlines the principles and practices of Scrum, a framework for developing software through self-organizing teams. It details Scrum roles, artifacts, and events, as well as the structure and importance of various sprints, including Sprint 0 for project initiation. Challenges and exceptions in the Scrum process are also discussed, emphasizing the collaborative nature and flexibility necessary for successful project management.
Agile Scrum Mastery: Learn How To Bring Complex Projects To life!
- 1. Agile Scrum Mastery By Arun Badole
- 2. About Me ● Head of Engineering ● 10+ years of experience in software development and project management ● Managed more than 30 complex projects with Agile & Scrum methodologies 2
- 3. 1. What is Scrum? 2. Scrum Skeleton 3. Scrum Roles 4. Scrum Artifacts 5. Scrum Events The Basics 3
- 4. 1. Sprint 0 2. Sprint 1..n 3. Sprint 4. Sprint Review 5. Sprint Retrospection 6. Exceptions The Pro Part 4
- 5. What is Scrum? ● A framework for developing & sustaining software products. ● Consist of self organizing cross functional teams. ● A project manager doesn’t control them since their expertise empowers them to make decisions collectively. Together to achieve same output Iterations allow flexibility Deliver a working piece of product. 5
- 6. Scrum ● Team works in chaotic environment to keep control of the ball. 6 ● This can be compared to a team working in a chaotic environment to keep the control of the project.
- 8. Scrum Roles ● Product Owner ● Scrum Master ● Development Team 8
- 9. Scrum Artifacts ● Product Backlog ● Sprint Backlog ● Product Increment (Increment of Releasable Product) 9
- 10. Scrum Events ● Sprint Planning Meeting ● Sprint ● Daily Scrum Meeting ● Sprint Review ● Sprint Retrospective 10
- 11. The Pro Part 11
- 12. Sprint 0 ❖ Most Important Sprint ❖ The problem statement ❖ Why of the project ❖ Client’s Goal/Vision ❖ Client<>Team Intro Meeting ❖ Architecture; Technology preferences ❖ Infrastructure: Tools to be used ❖ Process to be followed eg. JIRA, CI/CD, Codegrip etc. 12
- 13. Sprint 1…n ● Backlogs: Features ● Features Prioritization ● JIRA Epics & User Stories ● Pending items from last sprint 13 Product Backlog Prioritise Product Backlog High Priority Low Priority
- 14. Sprint 1…n Creating User Stories ● Acceptance Criteria: Contains low level details ● Subtasks ● Subtask Estimates ❖ If greater than 4hrs break it further ❖ Story Points Estimation: Usually 8hrs = 1 Story Point 14
- 15. Sprint 1…n Sprint Backlog ❖ Sprint Duration: 2 Weeks ❖ 8 days of development + 2 days for bug fixing and new sprint planning ❖ Based on priority we take only 8 Story Point for each developer ❖ Skip everything else 15
- 16. Sprint Daily Scrum Meeting ● Yesterday’s Tasks: Status of 8 hours tasks taken ● Today’s Tasks: ● Any Blockers ❖ Only take 8 hours of tasks from the estimations provided 16
- 17. Sprint Sprint Progress Check ❖ Work Logs ❖ Estimation on track ❖ Red Flags: Update to client in case of any delay or skipping any of the sprint items 17
- 18. Sprint QA ❖ Frequency of builds: Alternate days or twice in a week ❖ Dates for final dev, stage and production builds 18
- 19. Sprint Review ❖ Internal Sprint Features Demo ❖ Internal Feedback, Suggestions and Improvements ❖ Client Demo ❖ Client Feedback ❖ Sprint Delivery Email 19
- 20. Sprint Retrospection ● What went well? ● What can be improved? ● How to implement the change? ❖ Action Items for the next sprint ❖ Appreciation; Hero of the sprint 20
- 21. Exceptions ● Unplanned Leaves ● Red flags/Blockers ● Urgent fixes for e.g. production issues ● Priority changes For any of such scenarios ❖ No to changes ❖ Remove some low priority items to keep the delivery dates intact ❖ Or delay the sprint delivery (not ideal) 21
- 22. Thank You 22
- 23. Questions You can share your review for this presentation at arun.badole@mindbowser.com 23