Antanas Kompanas. When scrum is not enough
Download as PPTX, PDF0 likes583 views
The document discusses challenges with using SCRUM for complex software projects and proposes some solutions. It finds that keeping unpredictable tasks like design and evaluation outside sprints and using KANBAN boards split by activity helps address these challenges. Specifically, it recommends designing solutions ahead of development if changes are complex or the system is large, and using KANBAN for design, evaluation, and support work while keeping development work within sprints.
Antanas Kompanas. When scrum is not enough
- 1. When SCRUM Is NOT Enough Antanas Kompanas Solution Architect Baltic Amadeus, Lithuania © UAB Baltic Amadeus, 2014 Harmonious IT Solutions
- 2. ABOUT BALTIC AMADEUS • Software development and related services • Number of employees – 100+ • Microsoft Gold Partner • AGILEdriven company 1988 Baltic Amadeus is founded 1991 1993 1994 2001 2006 2007 Focus on software 2011 2009 2012 © UAB Baltic Amadeus, 2014 2
- 3. • Legacy enterprise system • BIG (7 different layers, 13 000+ files) • .NET C#, Web UI, WS • Technology mix THE PROJECT © UAB Baltic Amadeus, 2014 3
- 4. • Typical User Story: BUSINESS REQUEST – Allow easier registration of business clients Sounds easy, right? © UAB Baltic Amadeus, 2014 4
- 5. • What you get: BUSINESS REQUEST © UAB Baltic Amadeus, 2014 5
- 6. DEVELOPMENT PROCESS • Requirements from client: – Quick estimate – Solution specification – Development – Code review Estimate Specify Confirm Done Review Develop © UAB Baltic Amadeus, 2014 6
- 7. • Project manager – Contact person for client – Local Product Owner • Team Lead – Scrum Master • Developers • Internal QA specialist THE TEAM © UAB Baltic Amadeus, 2014 7
- 8. DEVELOPMENT PROCESS • Requirements from client: – Quick estimate – Solution specification – Development – Code review Estimate Specify Confirm Done Review Develop © UAB Baltic Amadeus, 2014 8
- 9. • How we work: DEVELOPMENT PROCESS – Quick estimate – Solution specification – Development – Code review Estimate Specify Confirm Done Review Develop © UAB Baltic Amadeus, 2014 9
- 10. DEVELOPMENT PROCESS • Specification benefits: – Smoother planning – Improved learning – Less surprises © UAB Baltic Amadeus, 2014 10
- 11. • What takes time: – Quick estimate – Solution specification – Development – Testing – Code review – Bug fixing TIME MANAGEMENT © UAB Baltic Amadeus, 2014 11
- 12. SIMPLE SOLUTION • Everything is a sprint task! © UAB Baltic Amadeus, 2014 12
- 13. SIMPLE SOLUTION • Everything is a sprint task! © UAB Baltic Amadeus, 2014 13
- 14. • Typical burn-down SIMPLE SOLUTION Burned more, done less © UAB Baltic Amadeus, 2014 14
- 15. SIMPLE SOLUTION • Reason: Design specification underestimated Burned more, done less © UAB Baltic Amadeus, 2014 15
- 16. SIMPLE SOLUTION 2.0 • Exclude Design tasks from sprint © UAB Baltic Amadeus, 2014 16
- 17. SIMPLE SOLUTION 2.0 • Exclude Design tasks from sprint © UAB Baltic Amadeus, 2014 17
- 18. SIMPLE SOLUTION 2.0 • Reason: Internal testing starts later 3x speed 4x speed Will we make it? © UAB Baltic Amadeus, 2014 18
- 19. SIMPLE SOLUTION 2.1 • Exclude testing tasks from sprint © UAB Baltic Amadeus, 2014 19
- 20. SIMPLE SOLUTION 2.1 • Reason: Shared code review task Code review task exhausted © UAB Baltic Amadeus, 2014 20
- 21. SIMPLE SOLUTION 2.9 • Include code review as a swim lane © UAB Baltic Amadeus, 2014 21
- 22. SIMPLE SOLUTION 3.0 • Only development hours in sprint • Not included: – Quick evaluation – Design specification – Internal testing © UAB Baltic Amadeus, 2014 22
- 23. SIMPLE SOLUTION 3.0 • Only development hours in sprint • Not included: – Quick evaluation – Design specification – Internal testing © UAB Baltic Amadeus, 2014 23
- 24. ADVANCED SOLUTION © UAB Baltic Amadeus, 2014 24
- 25. ADVANCED SOLUTION © UAB Baltic Amadeus, 2014 25
- 26. ADVANCED SOLUTION • Use KANBAN for Design and evaluation © UAB Baltic Amadeus, 2014 26
- 27. • All necessary states: – Backlog – Rough estimate needed – Rough estimate done – Better estimate needed – Team Review – Better estimate done – Design specification needed – Team Review – Design specification done – Ready for development – Irrelevant ADVANCED SOLUTION © UAB Baltic Amadeus, 2014 27
- 28. ADVANCED SOLUTION 2.0 Business Board © UAB Baltic Amadeus, 2014 28
- 29. ADVANCED SOLUTION 2.0 Design Board © UAB Baltic Amadeus, 2014 29
- 30. ADVANCED SOLUTION 2.0 Sprint Board © UAB Baltic Amadeus, 2014 30
- 31. ADVANCED SOLUTION 2.0 Support Board © UAB Baltic Amadeus, 2014 31
- 32. SUMMARY • Keep unpredictable tasks outside of sprint • Design solution ahead of development* • Use KANBAN for design, evaluation and support • Split KANBAN boards by activity • Trust business but improve your work * If changes are complex or your system is big © UAB Baltic Amadeus, 2014 32
- 33. QUESTIONS Questions Baltic Amadeus Vilnius, Lithuania http://www.baltic-amadeus.lt Antanas Kompanas Solution Architect a.kompanas@baltic-amadeus.lt © UAB Baltic Amadeus, 2014 33
- 34. THE END Thank you! Baltic Amadeus Vilnius, Lithuania http://www.baltic-amadeus.lt Antanas Kompanas Solution Architect a.kompanas@baltic-amadeus.lt © UAB Baltic Amadeus, 2014 34