O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Who says release planning is not agile - Vered Yeret at Agile Israel 2015

2.445 visualizações

Publicada em

Having a meaningful Sprint #1 has always been a real challenge for us. this was one of the reasons we decided to dedicate two full days for a release planning workshop based on SAFe. In this session I share why and how we did it, what we learnt before, during and after the workshop and tips for making it a success.

Publicada em: Tecnologia
  • Seja o primeiro a comentar

  • Seja a primeira pessoa a gostar disto

Who says release planning is not agile - Vered Yeret at Agile Israel 2015

  1. 1. Who said Release Planning is not Agile?
  2. 2. Let’s  Experiment  –  SAFe  Release  Planning?  
  3. 3. 1.  Clarify  the  Release  context   2.  Understand  the  big  picture   3.  Availability  and  focus  of  all     4.  Reveal  dependencies  early   5.  Honoring  people  8me  
  4. 4. Tip:  Have  a  Product  Management  partner  
  5. 5. Tip:  Predefine  the  Release  Planning  8meline  
  6. 6. Tip:  Share  the  Release  8meline  &   Milestones  ASAP  
  7. 7. Tip:  Visualize  the  Release  content  on  a   Physical  Board  
  8. 8. Agenda  of  the  Day    9:00- 10:00 10:00 - 17:00 18:00- 18:30 17:00- 18:00 ! Squad  leads  &  PO  present  draG  plans,  open   issues,  risks,  and  impediments   ! Squads  raise  open  issues  &  develop  draG  plans   and  idenJfy  risks  and  impediments   ! Architects R&D managers and Product Managers circulate ! Progress & focus check-in twice ! Discussing  open  issues,  challenges,  risks,  and   impediments   1 2 3 4 ! Business  context  By  Product   ! Opening  words  about  the  day  By  R&D   Tip:  Be  dynamic  about  the  agenda  
  9. 9. Day  1  Plan        9:00- 10:30 10:30 - 16:00 17:00- 17:30 16:00- 17:00 ! Squad  leads  &  PO  present  draG  plans   ! Squads  develop  draG  plans     ! Managers circulate ! Progress & focus check-in twice ! Discussing  open  issues,  challenges,  risks,   and  impediments   1 2 3 4 ! Business  context  By  Product   ! Opening  words  about  the  day  by  R&D  
  10. 10. Tip:  Use  Team  Breakouts  for  detailed   Planning  
  11. 11. Tip:  Use  Mid  day  Check-­‐ins  to  Focus  &   Collaborate  
  12. 12. Tip:  Use  a  Risk  Board  For  Visualizing  and   Solving  Risks  early  
  13. 13. Tip:  Con8nue  experimen8ng  
  14. 14. Tip:  invite  all  to  the  Plan  Review  
  15. 15. Tip:  Collect  (early)  Feedback    
  16. 16. Agenda  of  the  Day    9:00- 10:00 10:00 - 17:00 18:00- 18:30 17:00- 18:00 ! Squad  leads  &  PO  present  draG  plans,  open   issues,  risks,  and  impediments   ! Squads  raise  open  issues  &  develop  draG  plans   and  idenJfy  risks  and  impediments   ! Architects R&D managers and Product Managers circulate ! Progress & focus check-in twice ! Discussing  open  issues,  challenges,  risks,  and   impediments   1 2 3 4 ! Business  context  By  Product   ! Opening  words  about  the  day  By  R&D   Tip:  One  Focused  day  can  be  enough  
  17. 17. Was  it  worth  it?         Tip:  Management  buy-­‐in  is  crucial   Itai Mendelsohn VP of R&D
  18. 18. ü  Have a Product Management partner ü  Predefine the Release Planning timeline ü  Share the Release timeline & Milestones ASAP ü  Visualize the Release content on a Physical Board ü  Be dynamic about the agenda ü  Use Team Breakouts for detailed Planning ü  Use Mid day Check-ins to Focus and Collaborate ü  Use a Risk Board for visualizing and solving risks early ü  Continue experimenting ü  Invite all to the Plan review ü  Collect (early) Feedback ü  One Focused day can be enough ü  Management buy-in is crucial Take  away  
  19. 19. QuesJons  

×