Proofread_ivan_spresov

Transcript

1. A day in the life of a Scrum Master Challenges and common solutions 20th of April, 2019
2. 2 • 13 years of experience in Software Development • Over 9 years at EPAM Systems • Interested in challenging projects and talented people around me I VA N S P R E S O V Scrum Master
3. 3 Introduction
4. 4 Agile Belarus Community • About the Community: • The community is present in the biggest cities of Belarus. There are 1200 members. Events are held month. 3 conferences were organized: Agile Kitchen and Agile Minds 2018 • Epam System and Agile Belarus Community: • Support with facilitation and leadership • 30% of the speakers are working for EPAM Systems • Organizational and hosting support • Goals: • Improving the skill-set on the market • Gathering best practices • Sharing world-class expertise
5. 5 Engineering Challenges 360o Quality Time-to- market Costs Response to Change Efficiency Transparency Time-to-value
6. 6 Issues Poor code and architecture; outdated technologies Lack of relevant skills (hard and soft) 360o Agile is the default framework Transformation is required All issues are interrelated!
7. 7 EngX 360o Labs: [Holistic] Transformation-as-a-Service Radically improving [performance of] engineering organizations Assessment Transformation Blueprint Execution at scale Holistic rather than partial Execution rather than consulting Focus on Engineering eXcellence
8. 8 EngX 360o Labs Outcomes Deployable product at least every Sprint Continuous ly improving teams From time- to-market to time-to- value Early feedback Increasing productivity Maximizing value to customer EngX – Engineering eXcellence. “X“ times better!
9. 9 What about the calendar?
10. 10 SPRINT CALENDAR ID Monday Tuesday Wednesday Thursday Friday Sprint 3 Week 1 ❑ Daily SCRUM ❑ Retrospective(1h) ❑ Sprint Planning (3h) ❑ Sprint Backlog Refinement (2h) ❑ Daily SCRUM ❑ Sprint Backlog Refinement (1h) ❑ Daily SCRUM ❑ Daily SCRUM ❖ Release to production ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 2 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM Defect Triage BA/QA ❑ Status Report ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 3 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Backlog Refinement(30m) ❑ Daily SCRUM • UAT Smoke Test • QA Greenlight • Deployment to UAT-env ❑ Sprint Review
11. 11 SPRINT CALENDAR ID Monday Tuesday Wednesday Thursday Friday Sprint 3 Week 1 ❑ Daily SCRUM ❑ Retrospective(1h) ❑ Sprint Planning (3h) ❑ Sprint Backlog Refinement (2h) ❑ Daily SCRUM ❑ Sprint Backlog Refinement (1h) ❑ Daily SCRUM ❑ Daily SCRUM ❖ Release to production ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 2 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM Defect Triage BA/QA ❑ Status Report ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 3 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Backlog Refinement(30m) ❑ Daily SCRUM • UAT Smoke Test • QA Greenlight • Deployment to UAT-env ❑ Sprint Review
12. 12 ROADMAP Sprint 1 Sprint 2 Sprint 3 Sprint 4 Feature 1 Feature 2 Feature 3 Feature 4 Feature 5 Feature 6 Feature 7 Customer Demo March April Customer Demo
13. 13 ROADMAP Story 1 Story 2 Story 3 Story 4 Story 5 Story 4 Story 5 Scope Creep Product Owner Scrum Master Negotiation
14. 14 SPRINT CALENDAR ID Monday Tuesday Wednesday Thursday Friday Sprint 3 Week 1 ❑ Daily SCRUM ❑ Retrospective(1h) ❑ Sprint Planning (3h) ❑ Sprint Backlog Refinement (2h) ❑ Daily SCRUM ❑ Sprint Backlog Refinement (1h) ❑ Daily SCRUM ❑ Daily SCRUM ❖ Release to production ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 2 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM Defect Triage BA/QA ❑ Status Report ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 3 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Backlog Refinement(30m) ❑ Daily SCRUM • UAT Smoke Test • QA Greenlight • Deployment to UAT-env ❑ Sprint Review
15. 15 ROADMAP Sprint 1 Sprint 2 Sprint 3 Sprint 4 Customer Demo Release of sub-component March April Story 1 Story 2 Story 3 Story 4 Story 5 Story 6 Story 7 Feature 1 Feature 1 - planned Delay
16. 16 SPRINT CALENDAR ID Monday Tuesday Wednesday Thursday Friday Sprint 3 Week 1 ❑ Daily SCRUM ❑ Retrospective(1h) ❑ Sprint Planning (3h) ❑ Sprint Backlog Refinement (2h) ❑ Daily SCRUM ❑ Sprint Backlog Refinement (1h) ❑ Daily SCRUM ❑ Daily SCRUM ❖ Release to production ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 2 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM Defect Triage BA/QA ❑ Status Report ❑ Daily SCRUM ❑ Backlog Refinement(30m) Sprint 3 Week 3 ❑ Daily SCRUM ❑ Daily SCRUM ❑ Daily SCRUM ❑ Backlog Refinement(30m) ❑ Daily SCRUM • UAT Smoke Test • QA Greenlight • Deployment to UAT-env ❑ Sprint Review
17. 17 ROADMAP Sprint 1 Sprint 2 Sprint 3 Sprint 4 Feature 1 Feature 2 Feature 3 Feature 4 Feature 5 Feature 6 Feature 7 Customer Demo Release of sub-component March April Current State Differ Differ
18. 18 Summary • Use the Calendar as the way to begin communication. • If there is an iterative delivery process, then use the roadmap as the way to manage and negotiate expectations with the stakeholders. • Discuss the priority together with the Product Owner or Product Manager. H I G H L I G H T S
19. 19 What do we do with enhancements and bugs?
20. 20 BUGS Monday Bug 1 Bug 2 Bug 3 Bug 4 Bug 5
21. 21 BUGS Monday Tuesday Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6
22. 22 BUGS Monday Tuesday Wednesday Thursday Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8
23. 23 BUGS Monday Tuesday Wednesday Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Focus on bug fixing
24. 24 BUGS Monday Tuesday Wednesday Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 1 Bug 2 Bug 3 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Focus on bug fixing Thursday Bug 3 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Focus on bug fixing
25. 25 BUGS Monday Tuesday Wednesday Thursday Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8
26. 26 BUGS Monday Tuesday Wednesday Thursday Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Expedite
27. 27 BUGS Monday Tuesday Wednesday Thursday Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Fixed Delivery Date
28. 28 BUGS Monday Tuesday Wednesday Thursday Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Standard
29. 29 BUGS Monday Tuesday Wednesday Thursday Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Bug 3 Bug 1 Bug 2 Bug 4 Bug 5 Bug 6 Bug 7 Bug 8 Expedite Fixed Delivery Date Standard
30. 30 BUGS
31. 31 Summary • You can’t fix all the bugs in one time, unfortunately • There are several options when dealing with with bugs: o Take a portion of the defects and concentrate the team on them o Use a prioritization mechanism to handle the flow o Try to introduce quality gates (or at least try to star a discussion why they are necessary ☺) H I G H L I G H T S
32. 32 What about the Clients? They don’t know what they want.
33. 33 CLIENT Story 1 Story 2 Story 3 Feature 1 Epic 1 Feature 2
34. 34 CLIENT Story 1 Story 2 Story 3 Feature 1 Epic 1 Feature 2 Roadmap
35. 35 CLIENT Story 1 Story 2 Story 3 Feature 1 Epic 1 Feature 2 Roadmap Story 1 Story 2 Story 3 Feature 1 Epic 1 Feature 2
36. 36 CLIENT Work Work Work Work Planning Work Work Work Monday Tuesday Wednesday Thursday Monday Tuesday Wednesday Thursday Demo Demo Demo
37. 37 Summary • If the customer’s business requires sync and feedback more often, then propose the opportunity to show the demos more often, but use relevant instruments for that: • Prioritization of the backlog • Change management through the roadmap • Size of the stories and potential increments H I G H L I G H T S
38. 38 What about the delivery pipeline? How can it affect the roadmap?
39. 39 PROD Planning Integration Review Release Delivery
40. 40 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Customer Demo Customer Demo March April Story 1 Story 2 Story 3 Story 4 Story 5 Story 6 Story 7 Current State Feature 1 Feature 1 - planned Delay Up-to-date Roadmap
41. 41 Summary • The influence of infrastructure is high, and the impact on the project timing can’t be ignored. • As the Scrum Master participates in technical and infrastructure discussions, try to dive deeper than just a requirements observer. It will help you to speak the common language of both the business and the technical people. H I G H L I G H T S
42. 42 Questions?