Successfully reported this slideshow.
From Scrum level 0 to 3 in one year<br />FiftyOne’s Case Study<br />Ben Peer<br />Taking Agile to the Next Level<br />
From Scrum level 0 to 3 in one year<br />Scrum-2<br />Scrum-3<br />Scrum-1<br />
ABOUT US<br />SaaS - Internet ecommerce<br />Distributed Teams (TA/NY)<br />
WHY<br />CHANGE? <br />
WHY CHANGE?<br />Quarterly releases were too slow for us<br />
WHY CHANGE?<br />Reaction to requirement changes were too difficult<br />
WHY CHANGE?<br />Heard of better ways to develop software!<br />
BEFORE<br />AGILE…<br />Scrum Level 0<br />
BEFORE AGILE… SCRUM LEVEL 0<br />No Agile knowledge <br />
BEFORE AGILE… SCRUM LEVEL 0<br />Quarterly releases with 2 weeks of regression testing (2/12)<br />
BEFORE AGILE… SCRUM LEVEL 0<br />Build every few days by QA<br />
BEFORE AGILE… SCRUM LEVEL 0<br />Had 3 Teams: Infra, UI and QA<br />
BEFORE AGILE… SCRUM LEVEL 0<br />Automatic Testing – coded by QA and weeks after the feature was coded<br />
BEFORE AGILE… SCRUM LEVEL 0<br />Heavy weight work Gantts<br />
BEFORE AGILE… SCRUM LEVEL 0<br />Bugs Database with hundreds of defects<br />
GETTING<br />READY<br />
GETTING READY<br />Mindset- Scrum workshop <br />
GETTING READY<br />Reorganization - New Multi-Functional Team Formation<br />Product Owners<br />Scrum Master<br />Local P...
GETTING READY<br />Sprint length - 2 weeks<br />With 2/10 days for regression<br />
GETTING READY<br />New Ceremonies - Dailies<br />
GETTING READY<br />New Ceremonies - Planning<br />
GETTING READY<br />New Ceremonies – Sprint Review<br />
GETTING READY<br />New Ceremonies – Retrospective<br />
GETTING READY<br />KANBAN Board<br />
GETTING READY<br />Continuous Integration<br />
GETTING READY<br />Multiple Integration Testing Environments<br />Sanity (Fast Build)<br />Regression(Slow Build)<br />INT...
GETTING READY<br />Burn Down & Up Charts<br />
OK, time to JUMP…<br />
Sprints 1 – 10 <br />Scrum Level 1<br />(Feb 2010 – June 2010)<br />
SPRINTS 1-10:   Scrum Level 1<br />10/10 in Production on Time!<br />
SPRINTS 1-10:   Scrum Level 1<br />Sprint Commitment  a killer<br />
SPRINTS 1-10:   Scrum Level 1<br />Test Automation  Nightmare<br />
SPRINTS 1-10:   Scrum Level 1<br />Planning & Estimation  Painful & Wasteful<br />
GETTING<br />READY #2<br />To Scrum Level 2<br />
GETTING READY #2<br />Mindset– Kanban workshop <br />
GETTING READY #2<br />WIP Limits<br />
GETTING READY #2<br />ATDD new tool<br />
GETTING READY<br />Only Burn Up Charts<br />
GETTING READY #2<br />Code Freeze EOD 9/10<br />
OK, time to JUMP again!<br />
Sprints 11 – 20 <br />From Scrum <br />Level 1  2<br />(July 2010 – Nov 2010)<br />
SPRINTS 11-20:   Scrum Level 2<br />20/20 in Production on Time!<br />
SPRINTS 11-20:   Scrum Level 2<br />No Sprint Commitment! <br />
SPRINTS 11-20:   Scrum Level 2<br />Test Automation Regression Suite  Better<br />
SPRINTS 11-20:   Scrum Level 2<br />Story Estimation  t-shirt by product<br />
SPRINTS 11-20:   Scrum Level 2<br />Regression day 9/10  mostly invested in automation<br />
GETTING READY #3 ?<br />GETTING READY #3 ??<br />JUMP #3 ??<br />NO NEED!<br />CONTINUOUS IMPROVMENT<br />
Sprints 21 – 30 <br />From Scrum <br />Level 2  3<br />(Dec 2010 – Apr 2011)<br />
SPRINTS 21-30:   Scrum Level 3<br />Smaller Scrum Teams<br />Scrum Master<br />Local PO<br />AKADO<br />Code Monkeys<br />...
SPRINTS 21-30:   Scrum Level 3<br />Bye BUG DB, Hello Defects Board <br />
SPRINTS 21-30:   Scrum Level 3<br />Test Automation – Victory!<br />
SPRINTS 21-30:   Scrum Level 3<br />Root Cause Analysis – every production escaped defect<br />
SPRINTS 21-30:   Scrum Level 3<br />Operations Review<br />
WHAT <br />HAVE WE GAINED? <br />
WHAT HAVE WE GAINED?<br />SPEED – Prod Release Every 2 Weeks<br />
WHAT HAVE WE GAINED?<br />FLEXIBILITY – very easy to react to requirement changes<br />
WHAT HAVE WE GAINED?<br />VISIBILITY - Major Improvement in Project Management<br />
WHAT HAVE WE GAINED?<br />Continuous Improvement Infrastructure!<br />
WHAT HAVE WE GAINED?<br />QUALITY– remained the same<br />
SUCESS<br />FACTORS <br />
SUCCESS FACTORS<br />Senior Management Support – Both Business & R&D <br />
SUCCESS FACTORS<br />Help from Experts<br />Guidelines & Support from our Coach<br />
SUCCESS FACTORS<br />Scrum and Kanban –<br />Simple methods that make sense<br />
SUCCESS FACTORS<br />Agile Engineering Practices  & Tools<br />
SUCCESS FACTORS<br />Invested heavily in Automation<br />
Q&A<br />Q&A<br />
Upcoming SlideShare
Loading in …5
×

Benny Peer - Fiftyone.com Scrum Level0->3 in one year - AgileIL11

2,037 views

Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Benny Peer - Fiftyone.com Scrum Level0->3 in one year - AgileIL11

  1. 1. From Scrum level 0 to 3 in one year<br />FiftyOne’s Case Study<br />Ben Peer<br />Taking Agile to the Next Level<br />
  2. 2. From Scrum level 0 to 3 in one year<br />Scrum-2<br />Scrum-3<br />Scrum-1<br />
  3. 3. ABOUT US<br />SaaS - Internet ecommerce<br />Distributed Teams (TA/NY)<br />
  4. 4. WHY<br />CHANGE? <br />
  5. 5. WHY CHANGE?<br />Quarterly releases were too slow for us<br />
  6. 6. WHY CHANGE?<br />Reaction to requirement changes were too difficult<br />
  7. 7. WHY CHANGE?<br />Heard of better ways to develop software!<br />
  8. 8. BEFORE<br />AGILE…<br />Scrum Level 0<br />
  9. 9. BEFORE AGILE… SCRUM LEVEL 0<br />No Agile knowledge <br />
  10. 10. BEFORE AGILE… SCRUM LEVEL 0<br />Quarterly releases with 2 weeks of regression testing (2/12)<br />
  11. 11. BEFORE AGILE… SCRUM LEVEL 0<br />Build every few days by QA<br />
  12. 12. BEFORE AGILE… SCRUM LEVEL 0<br />Had 3 Teams: Infra, UI and QA<br />
  13. 13. BEFORE AGILE… SCRUM LEVEL 0<br />Automatic Testing – coded by QA and weeks after the feature was coded<br />
  14. 14. BEFORE AGILE… SCRUM LEVEL 0<br />Heavy weight work Gantts<br />
  15. 15. BEFORE AGILE… SCRUM LEVEL 0<br />Bugs Database with hundreds of defects<br />
  16. 16. GETTING<br />READY<br />
  17. 17. GETTING READY<br />Mindset- Scrum workshop <br />
  18. 18. GETTING READY<br />Reorganization - New Multi-Functional Team Formation<br />Product Owners<br />Scrum Master<br />Local PO<br />SCRUM TEAM A<br />SCRUM TEAM B<br />Agile Testing<br />NY<br />NY<br />TA<br />
  19. 19. GETTING READY<br />Sprint length - 2 weeks<br />With 2/10 days for regression<br />
  20. 20. GETTING READY<br />New Ceremonies - Dailies<br />
  21. 21. GETTING READY<br />New Ceremonies - Planning<br />
  22. 22. GETTING READY<br />New Ceremonies – Sprint Review<br />
  23. 23. GETTING READY<br />New Ceremonies – Retrospective<br />
  24. 24. GETTING READY<br />KANBAN Board<br />
  25. 25. GETTING READY<br />Continuous Integration<br />
  26. 26. GETTING READY<br />Multiple Integration Testing Environments<br />Sanity (Fast Build)<br />Regression(Slow Build)<br />INTEGRATION 1<br />INTEGRATION 2<br />
  27. 27. GETTING READY<br />Burn Down & Up Charts<br />
  28. 28. OK, time to JUMP…<br />
  29. 29. Sprints 1 – 10 <br />Scrum Level 1<br />(Feb 2010 – June 2010)<br />
  30. 30. SPRINTS 1-10: Scrum Level 1<br />10/10 in Production on Time!<br />
  31. 31. SPRINTS 1-10: Scrum Level 1<br />Sprint Commitment  a killer<br />
  32. 32. SPRINTS 1-10: Scrum Level 1<br />Test Automation  Nightmare<br />
  33. 33. SPRINTS 1-10: Scrum Level 1<br />Planning & Estimation  Painful & Wasteful<br />
  34. 34. GETTING<br />READY #2<br />To Scrum Level 2<br />
  35. 35. GETTING READY #2<br />Mindset– Kanban workshop <br />
  36. 36. GETTING READY #2<br />WIP Limits<br />
  37. 37. GETTING READY #2<br />ATDD new tool<br />
  38. 38. GETTING READY<br />Only Burn Up Charts<br />
  39. 39. GETTING READY #2<br />Code Freeze EOD 9/10<br />
  40. 40. OK, time to JUMP again!<br />
  41. 41. Sprints 11 – 20 <br />From Scrum <br />Level 1  2<br />(July 2010 – Nov 2010)<br />
  42. 42. SPRINTS 11-20: Scrum Level 2<br />20/20 in Production on Time!<br />
  43. 43. SPRINTS 11-20: Scrum Level 2<br />No Sprint Commitment! <br />
  44. 44. SPRINTS 11-20: Scrum Level 2<br />Test Automation Regression Suite  Better<br />
  45. 45. SPRINTS 11-20: Scrum Level 2<br />Story Estimation  t-shirt by product<br />
  46. 46. SPRINTS 11-20: Scrum Level 2<br />Regression day 9/10  mostly invested in automation<br />
  47. 47. GETTING READY #3 ?<br />GETTING READY #3 ??<br />JUMP #3 ??<br />NO NEED!<br />CONTINUOUS IMPROVMENT<br />
  48. 48. Sprints 21 – 30 <br />From Scrum <br />Level 2  3<br />(Dec 2010 – Apr 2011)<br />
  49. 49. SPRINTS 21-30: Scrum Level 3<br />Smaller Scrum Teams<br />Scrum Master<br />Local PO<br />AKADO<br />Code Monkeys<br />Lemmings<br />Agile Testing<br />
  50. 50. SPRINTS 21-30: Scrum Level 3<br />Bye BUG DB, Hello Defects Board <br />
  51. 51. SPRINTS 21-30: Scrum Level 3<br />Test Automation – Victory!<br />
  52. 52. SPRINTS 21-30: Scrum Level 3<br />Root Cause Analysis – every production escaped defect<br />
  53. 53. SPRINTS 21-30: Scrum Level 3<br />Operations Review<br />
  54. 54. WHAT <br />HAVE WE GAINED? <br />
  55. 55. WHAT HAVE WE GAINED?<br />SPEED – Prod Release Every 2 Weeks<br />
  56. 56. WHAT HAVE WE GAINED?<br />FLEXIBILITY – very easy to react to requirement changes<br />
  57. 57. WHAT HAVE WE GAINED?<br />VISIBILITY - Major Improvement in Project Management<br />
  58. 58. WHAT HAVE WE GAINED?<br />Continuous Improvement Infrastructure!<br />
  59. 59. WHAT HAVE WE GAINED?<br />QUALITY– remained the same<br />
  60. 60. SUCESS<br />FACTORS <br />
  61. 61. SUCCESS FACTORS<br />Senior Management Support – Both Business & R&D <br />
  62. 62. SUCCESS FACTORS<br />Help from Experts<br />Guidelines & Support from our Coach<br />
  63. 63. SUCCESS FACTORS<br />Scrum and Kanban –<br />Simple methods that make sense<br />
  64. 64. SUCCESS FACTORS<br />Agile Engineering Practices & Tools<br />
  65. 65. SUCCESS FACTORS<br />Invested heavily in Automation<br />
  66. 66. Q&A<br />Q&A<br />

×