Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Antanas Kompanas. When scrum is not enough

469 views

Published on

Once you start using SCRUM and its time-boxing approach there is a natural urge to put everything into the sprint to get better control of it: initial analysis, architecture, testing, meetings, etc... However, it turns out that it’s not that simple and some tasks are just not meant to be handled in sprint. In this session we will explore how usage of SCRUM evolved in one of the development teams in Baltic Amadeus while working on a big enterprise solution and how we managed to stabilize sprint scope by offloading particular development tasks to KANBAN. We will also show what stages each user story must pass to make it work well in an enterprise environment.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Antanas Kompanas. When scrum is not enough

  1. 1. When SCRUM Is NOT Enough Antanas Kompanas Solution Architect Baltic Amadeus, Lithuania © UAB Baltic Amadeus, 2014 Harmonious IT Solutions
  2. 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. 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. 4. • Typical User Story: BUSINESS REQUEST – Allow easier registration of business clients Sounds easy, right? © UAB Baltic Amadeus, 2014 4
  5. 5. • What you get: BUSINESS REQUEST © UAB Baltic Amadeus, 2014 5
  6. 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. 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. 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. 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. 10. DEVELOPMENT PROCESS • Specification benefits: – Smoother planning – Improved learning – Less surprises © UAB Baltic Amadeus, 2014 10
  11. 11. • What takes time: – Quick estimate – Solution specification – Development – Testing – Code review – Bug fixing TIME MANAGEMENT © UAB Baltic Amadeus, 2014 11
  12. 12. SIMPLE SOLUTION • Everything is a sprint task! © UAB Baltic Amadeus, 2014 12
  13. 13. SIMPLE SOLUTION • Everything is a sprint task! © UAB Baltic Amadeus, 2014 13
  14. 14. • Typical burn-down SIMPLE SOLUTION Burned more, done less © UAB Baltic Amadeus, 2014 14
  15. 15. SIMPLE SOLUTION • Reason: Design specification underestimated Burned more, done less © UAB Baltic Amadeus, 2014 15
  16. 16. SIMPLE SOLUTION 2.0 • Exclude Design tasks from sprint © UAB Baltic Amadeus, 2014 16
  17. 17. SIMPLE SOLUTION 2.0 • Exclude Design tasks from sprint © UAB Baltic Amadeus, 2014 17
  18. 18. SIMPLE SOLUTION 2.0 • Reason: Internal testing starts later 3x speed 4x speed Will we make it? © UAB Baltic Amadeus, 2014 18
  19. 19. SIMPLE SOLUTION 2.1 • Exclude testing tasks from sprint © UAB Baltic Amadeus, 2014 19
  20. 20. SIMPLE SOLUTION 2.1 • Reason: Shared code review task Code review task exhausted © UAB Baltic Amadeus, 2014 20
  21. 21. SIMPLE SOLUTION 2.9 • Include code review as a swim lane © UAB Baltic Amadeus, 2014 21
  22. 22. SIMPLE SOLUTION 3.0 • Only development hours in sprint • Not included: – Quick evaluation – Design specification – Internal testing © UAB Baltic Amadeus, 2014 22
  23. 23. SIMPLE SOLUTION 3.0 • Only development hours in sprint • Not included: – Quick evaluation – Design specification – Internal testing © UAB Baltic Amadeus, 2014 23
  24. 24. ADVANCED SOLUTION © UAB Baltic Amadeus, 2014 24
  25. 25. ADVANCED SOLUTION © UAB Baltic Amadeus, 2014 25
  26. 26. ADVANCED SOLUTION • Use KANBAN for Design and evaluation © UAB Baltic Amadeus, 2014 26
  27. 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. 28. ADVANCED SOLUTION 2.0 Business Board © UAB Baltic Amadeus, 2014 28
  29. 29. ADVANCED SOLUTION 2.0 Design Board © UAB Baltic Amadeus, 2014 29
  30. 30. ADVANCED SOLUTION 2.0 Sprint Board © UAB Baltic Amadeus, 2014 30
  31. 31. ADVANCED SOLUTION 2.0 Support Board © UAB Baltic Amadeus, 2014 31
  32. 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. 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. 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

×