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.

Agile101 - What Agile Is and What Agile Is Not


Published on

Presented on September 28, 2012 at the PM Symposium in Washington DC.
Presented on November 9, 2012 at the PMI Puerto Rico Simposio Anual.

Published in: Business

Agile101 - What Agile Is and What Agile Is Not

  1. 1. Agile 101 What Agile Is andWhat Agile Is Not
  2. 2. Derek Huether Enterprise Agile Coach
  4. 4. What Agile is Not•New ≠
  5. 5. Not New DSDN Consortium Hirotaka Takeuchi Dynamic System & Ikujiro Nonaka Development Method Robert Charette The New New Product Lean DevelopmentTaiichi Ohno Development Game Jeff de LucaToyota Production System Feature DrivenKanban Development 1943 1985 1995 1997 2000 Hardware Software 1950- 1990 1996 1998 2001 1960s USAF & NASA X-15 hypersonic jet Iterative Incremental 1990 - Sutherland & Alistair Cockburn Delivery Schwaber Crystal Methodologies Scrum Framework 1996 - Beck, Cunningham, Jeffries Extreme Programming Agile Manifesto
  6. 6. Not New Agile Methods in 2011 Source: VersionOne - State of Agile Survey 2011
  7. 7. What Agile is Not•New•Without planning ≠
  8. 8. Not Without PlanningProduct / Project IterationWhat business objectives will this fulfill? What specifically will we build? Vision/Mission How will this iteration move us toward release objectives? Goals Iteration Plan Charter Development Tasks Release How can we release value incrementally? User Story What subset of business (Backlog Item) objectives will each release achieve? What user or stakeholder need will the story serve? Which user(s) will the release serve? How will I know if it is done? What general capabilities Story Details will the release offer? Acceptance Tests Release Roadmap Release Plan
  9. 9. What Agile is Not•New•Without planning ≠•An excuse for poor quality
  10. 10. Not an Excuse for Poor Quality Write a Passing Test Write code to make it pass Refactor Write code to make it pass Write a Failing Test
  11. 11. What Agile is Not•New•Without planning ≠•An excuse for poor quality•Undisciplined
  12. 12. Not Undisciplined Complete Subset of Backlog Portfolio/Project Team works on highest-value functionality until it Or Iteration meets jointly defined Acceptance Criteria. Planning Elaboration, estimation and Daily Meeting (or Standup)prioritization of highest-value 15-minute status and risk management meeting for deliverables. Team & Business/Product Owner. Execution Backlog Review Team demonstrates completed functionality to interested stakeholders, gathering feedback. As a [role] I want [value] Production Release (Optional) As a [role] I want [value] Generally occurs when a useful group of related functionality has been completed. As a [role] I want [value] Retrospective Team reflects on project & process and takes action as appropriate.
  13. 13. What Agile is Not•New•Without planning ≠•Without documentation•An excuse for poor quality•Undisciplined•Unproven
  14. 14. Not Unproven Source: VersionOne - Benefits of Agile - State of Agile Survey 2011
  15. 15. What Agile is Not•A hippie cult•A quick fix ≠•A silver bullet
  16. 16. =WHAT AGILE IS
  17. 17. What Agile Is•Upheld by values =•Guided by principles
  18. 18. Agile Manifesto ValuesWe are uncovering better ways of developing software bydoing it and helping others do it. Through this work we havecome to value: Individuals & interactions over Processes & tools Comprehensive Working software over documentation Customer collaboration over Contract negotiation Responding to change over Following a plan That is, while there is value in the items on the right, we value the items on the left more. Source:
  19. 19. Agile Manifesto Principles Satisfy the Welcome Deliver Collaborate Customer Change Frequently DailySupport & Trust Promote Promote Deliver Working Motivated Face-to-Face Sustainable Software Teams Conversations Pace Promote Maximize Have Reflect & Adjust Technical Through Self-Organized Regularly Excellence Simplicity Teams Source:
  20. 20. What Agile is•Upheld by values•Guided by principles =•People centric
  21. 21. People Centric Emotional IntelligencePersonal Competencies Social CompetenciesSELF-AWARENESS EMPATHYKnowing ones internal states, Awareness of others feelings, needs,preferences, resources, and intuitions and concerns.MANAGING EMOTIONS SOCIAL SKILLSManaging ones internal states, impulses, Adeptness at inducing desirableand resources. responses in others.MOTIVATIONEmotional tendencies that guide orfacilitate reaching goals.
  22. 22. What Agile is•Inspired by values•Guided by principles =•People centric•Value Driven
  23. 23. Value Driven
  24. 24. What Agile is•Upheld by values•Guided by principles =•People centric•Value Driven•Collaborative
  25. 25. Collaborative ! ? ?We don’t need an accuratedocument, we need ashared understanding - Jeff Patton / Agile 2012
  26. 26. What Agile is•Upheld by values•Guided by principles =•People centric•Value Driven•Collaborative•Self-Organizing
  27. 27. Self-Organizinginfo infoguide guide infoinfo guideguide
  28. 28. ConclusionAgile is an organizational approach. It is about teams and culture. Agile methods like Scrum are an Agile life-cycle. It is a life-cycle based on Agile teams. They happen to be Incremental-Iterative that support adaptive scope. You cant do Agile life-cycle without Agile teams but you can do Agile teams in other life-cycles.
  29. 29. Thank YouFor additional questions or information, just contact me at