Game changers
0 likes770 views
This document outlines four levels of agile implementation: 1) Process, 2) Technical Practices, 3) Product Teams, and 4) Scale. It provides examples for each level, such as Kanban and Scrum for process and Lean Startup for product teams. Additional resources are recommended for further learning. The summary emphasizes that the four levels can reduce waste, empower teams, and create less work if implemented properly during growth and scaling.
Game changers
- 3. DISCLAIMER Those are my personal opinions, different coaches and trainers opinions might differ.
- 4. 4 LEVELS 1. Process ! 2. Technical practises 3. Product (focus on value) 4. SCALE: Alignment & Communication
- 8. KANBAN âą Who is doing what? âą What are the priorities? âą When will it be done? âą âI thought something else need to be doneâ âą We donât have time to fix bugs
- 9. âItâs better to ask for forgiveness then for permissionâ
- 10. WANT TO LEARN MORE? âą Yes we Kanban âą Get Kanban with GetKanban Tomasz Ćasica Mateusz Srebrny
- 11. SCRUM
- 12. SCRUM âą Continuous improvement âą Better communication to stakeholders
- 13. WANT TO LEARN MORE? S c r u m P r i m e r Introduction to Scrum MichaĆ PrzÄ dka
- 14. SCRUM PATTERNS
- 15. SCRUM Patterns www.scrumplop.org JEFF sutherland
- 17. Scrum shock therapy JEFF sutherland ⹠Everyone is trained in Scrum ⹠One week sprints ⹠All ceremonies together up to 4 hours ⹠Stop when team delivers 3 commitments in a row ⹠⊠blah blah blah ⹠Discipline! ⹠(it is not as bad as it sounds)
- 18. Release cycle
- 19. âNothing improves a team morale more than a release to productionâ
- 20. LEVEL 2 Technical PRACTICES
- 21. Implementing âą Training is good, change agent is much better âą Code DOJO is a good start âą There is no better way then pair programming âą Code Review is good (later) âą Technical debt will take consistent effort over time to get rid of
- 22. WANT TO LEARN MORE? e X t r e m e Programming (XP) for beginners Jakub Nabrdalik
- 23. LEVEL 3 Project vs.product teams
- 24. AIM! project team WORKING SOFTWARE PRODUCT team VALUE! PROJECT team WORKING SOFTWARE
- 25. DID A GOOD JOB PROJECT TEAM:! ! ⹠NO BUGS ! ⹠DELIVERED FAST ! ⹠WHAT PRODUCT OWNER WANTED PRODUCT TEAM:! ! ⹠MONEY! ⊠or ! ⹠Validated learning ! ⹠GROWTH ⹠CONVERSIONS ⹠FREE TRIALS ⹠REVENUE
- 26. TEAM MEMBERS PROJECT TEAM! ! ⹠DEVELOPERS ⹠TESTERS ⹠DESIGNERS ! ! ! ! PRODUCT TEAM:! ! ALSO:! ⹠MARKETING ⹠SALES ⹠OTHER� !
- 27. PROCESS PROJECT TEAM! ! âą SCRUM âą KANBAN âą EXTREME PROGRAMMING PRODUCT TEAM âą LEAN STARTUP âą EVO ! ! ! !
- 28. MEASURE OF PROGRESS BURN DOWN CHART FUNNEL
- 29. WANT TO LEARN MORE? The Lean Startup in a corporate practice â validate or die Agata Czopek
- 30. WANT TO LEARN MORE? Lean Startup for Agile Product Management Ăngel Medinilla
- 31. LEVEL 4 Scale
- 32. Scale PROCESS âą You can scale Scrum with LeSS âą Kanban Scale it selfs nicely
- 34. WANT TO LEARN MORE? Scaling Scrum with LeSS Marek Kirejczyk
- 35. WANT TO LEARN MORE? War stories about S c a l e d A g i l e Framework Tomek PajÄ k
- 36. Alignment
- 37. V2MOM âą VISION - What is overall vision âą VALUES - What are our values âą METHODS - What specific methods will I use âą OBSTACLES - What may stop me? âą MEASUREMENTS - How will we know if we achieved a goal? (or in what %?)
- 38. V2mom - NOTES âą CEO starts, then everybody negotiate his V2MOM âą Usually done once a quoter âą I like to stop on team level (by Karol Traczykowski)
- 39. WANT TO LEARN MORE? 5 reasons to use V2MOMs at your company Karol Traczykowski
- 40. Summary
- 41. 4 levels of (my) agile implementation 1. SPEED 1: Process 2. SPEED 2: Technical practises 3. BUSINESS FOCUS: Product teams 4. SCALE: Alignment & Communication
- 42. 4 levels waste 1. SPEED 1: We estimate bad, communicate bad, we have unfinished features 2. SPEED 2: We have bugs, we deliver slower then we could 3. BUSINESS FOCUS: We build what our customers donât want to pay for 4. SCALE: We lose all above, because of our scale
- 43. 4 levels of EMPOWERMENT 1. SPEED 1: Team create itâs own process (improve) 2. SPEED 2: Team aims for Technical excellence (Software craftsmanship) 3. BUSINESS FOCUS: Team improves business 4. SCALE: Teams can still do all of above while growing
- 44. 4 levels of lazy jobs 1. Scrum Master has little to do 2. Team Leader has little to do 3. PO has little to do 4. CEO has little to do