Heart of Agile
•
1 like•386 views
Agile has become mainstream in the IT industry, since that the multiplication of Agile practices which makes Agile implementation complex and uncertain, we have started to see failure in Agile implementations. During this presentation we will start a simplification process by going back to the source of Agile, understand what Agile is and what it is not. We will discover what is the Heart of Agile, its essence, and how it embraces management
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Heart of Agile
Similar to Heart of Agile (20)
More from Pierre Hervouet
More from Pierre Hervouet (12)
Recently uploaded
Recently uploaded (20)
Heart of Agile
- 1. HEART OF AGILE What is Agile?
- 2. THANK YOU TO OUR
- 3. THANK YOU TO OUR PARTNERS
- 9. AGILE MANIFESTO Heart Of Agile PM BEFORE MANIFESTO AFTER MANIFESTO 2001
- 10. PM
- 12. 1 2 # 1 X X X X # 2 X X
- 13. Scrum Stakeholder Product Owner Developers Product Owner Vision Scrum Master Product Backlog Potentially shippable Product Daily Stand-Up Sprint Sprint Review Burndown Charts
- 14. CRYSTAL
- 15. Dynamic Systems Development Method (DSDM)
- 18. FDD
- 19. ASD Project Initiation Adaptive Cycle Planning Concurrent Component engineering Quality Review Final QA & Release Speculate Collaborate Learn
- 22. AGILE MANISFESTO
- 24. Agile Manifesto Values Working software over comprehensive documentation
- 25. What is the most important Word?
- 26. Agile Manifesto Values Working software over comprehensive documentation
- 27. Agile Manifesto Values Working software over comprehensive documentation
- 28. What’s Matter?
- 29. anecdote • CCMI • PMI • RUP
- 30. anecdote • CCMI • PMI • RUP PMP CMMI RUP
- 31. 12 principles ‣ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. . ‣ Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ‣ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ‣ Business people and developers must work together daily throughout the project. ‣ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ‣ The most efficient and effective method of conveying information to and within a development team is face- to-face conversation. ‣ Working software is the primary measure of progress. ‣ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ‣ Continuous attention to technical excellence and good design enhances agility. ‣ Simplicity--the art of maximizing the amount of work not done--is essential. ‣ The best architectures, requirements, and designs emerge from self-organizing teams. ‣ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 35. Failed, 29% Challenged , 60% Successful , 11% Waterfall Failed, 9% Challenged , 52% Successful , 39% Agile
- 38. PRACTICES • Daily Stand up meeting • Retrospective • Backlog • Sprint • TDD • Pair programming • Road map • Definition of done • Backlog Grooming • Sprint Planning • Limit the WIP • Relative sizing • Planning Poker • Dot Voting • User stories • Acceptance criteria • Celebration • A3 • Flow visualization • Burn down Chart • Cumulative Flow Diagram • Impediments Backlog • Cost Of Delay • Kudo Card • Real Option • No estimations • Story Points • Persona • Velocity • Client Proxy • Self-organized team • Definition of Ready • Gemba • Time Boxes • Prune the Product Tree • Product roadmap • Prototyping • …
- 39. CERTIFICATIONS
- 43. Beware the dark side of the force THE DARK SIDE OF agile THE NEW MANIFESTO
- 44. AGILE VALUES Individuals & Interactions OVER processes & Tools Working software OVER comprehensive documentation Customer Collaboration OVER Contract negotiation Responding to change OVER Planing
- 45. AGILE VALUES UNDERSTANDING Individuals & Interactions _NO_ processes & Tools Working software _NO_ comprehensive documentation Customer Collaboration NO_ Contract negotiation Responding to change _NO_ Planing
- 47. DARK SIDE OF AGILE PRINCIPLES Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. . Our highest priority is to satisfy the customer through early and continuous delivery of valuable software…”we don’t care of the quality”
- 48. DARK SIDE OF AGILE PRINCIPLES Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage
- 49. DARK SIDE OF AGILE PRINCIPLES Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- 50. DARK SIDE OF AGILE PRINCIPLES Business people and developers must work together daily throughout the project. Business people and developers must be busy together daily throughout the project.
- 51. DARK SIDE OF AGILE PRINCIPLES Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
- 52. DARK SIDE OF AGILE PRINCIPLES The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation (ALWAYS !) The most efficient and effective method of conveying information to and within a development team is face-to-face conversation (and we have to do systematically detailled minutes)
- 53. DARK SIDE OF AGILE PRINCIPLES Working software is the primary measure of progress. Working software is the ONLY measure of SUCCESS.
- 54. DARK SIDE OF AGILE PRINCIPLES “Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.” “Agile processes promote sustainable development (at minima). The sponsors, developers, and users should be able to maintain a constant pace (not to fast) indefinitely.”
- 55. DARK SIDE OF AGILE PRINCIPLES “Continuous attention to technical excellence and good design enhances agility.” “Continuous attention to technical excellence and good design enhances agility.” We deliver “Continuous attention to technical perfection and perfect design enhances agility.”
- 56. DARK SIDE OF AGILE PRINCIPLES “Simplicity--the art of maximizing the amount of work not done--is essential.” “Simplistically-the art of maximizing the amount of work not done--is essential.”
- 57. DARK SIDE OF AGILE PRINCIPLES “The best architectures, requirements, and designs emerge from self- organizing teams.” “The best architectures, requirements, and designs emerge from self- managing teams.” “The best architectures, requirements, and designs emerge from self- organized teams.”
- 58. DARK SIDE OF AGILE PRINCIPLES “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
- 59. Beware the dark side of the force THE DARK SIDE OF agile THE NEW MANIFESTO
- 60. DARK SIDE OF AGILE PRINCIPLES 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage 3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4. Business people and developers must be busy together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation (and we have to report in detail) 7. Working software is the ONLY measure of SUCCESS. 8. “Agile processes promote sustainable development (at minima). The sponsors, developers, and users should be able to maintain a constant pace (not to fast) indefinitely (like the project).” 9. “Continuous attention to technical perfection and perfect design enhances agility.” 10. “Simplistically-the art of maximizing the amount of work not done--is essential.” 11. “The best architectures, requirements, and designs emerge from self-organized teams.” 12. “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
- 62. “WHAT IS AGILE?”
- 63. SHU - HA – RI FOLLOW THE RULES BREAK THE RULES BE THE RULES
- 64. SHU - HA – RI - KOKORO FOLLOW THE RULES BREAK THE RULES BE THE RULES The Heart
- 67. 400 WORDS
- 68. 400 WORDS
- 69. 4 WORDS
- 71. 4 VERBS
- 80. Fortune teller
- 83. Fortune Teller