1 / 36

Agile: Truths and Misconceptions

Agile: Truths and Misconceptions. Agile Center of Excellence. Richard K Cheng . Agile Center of Excellence. Richard K Cheng. Truth. Or. Misconception. Agile is just a high level concept. Truth Or Misconception. Core Agile Values.

barney
Download Presentation

Agile: Truths and Misconceptions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile: Truths and Misconceptions Agile Center of Excellence

  2. Richard K Cheng Agile Center of Excellence Richard K Cheng

  3. Truth Or Misconception

  4. Agile is just a high level concept Truth Or Misconception

  5. Core Agile Values We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: That is, while there is value in the items on the right, we value the items on the left more. www.agilemanifesto.org

  6. Satisfy the customer through early and continuous delivery Welcome changing requirements Deliver frequently, preferring a shorter timescale Business & Technical work together daily Pick the right team & trust them Face-to-Face Communication Core Agile Principles • Working software is the primary measure of progress • Sustainable pace • Technical excellence and good design enhances agility • Simplicity, maximizing the amount of work not done • Best results emerge from self-organizing teams • The team regularly reflects to become more effective

  7. Identifying and delivering value…… • Identify value and eliminate waste • Prioritize features • Deliver early and often • Constant inspection • Empower team

  8. Scrum and Agile are the same thing Truth Or Misconception

  9. Agile Methodologies

  10. Scrum Overview Project development is performed in 2 to 4 week iterations. Product Owner creates a prioritized backlog of features Highest priority features delivered first At the end of the iteration, the deliverables are reviewed by the business customers The team reflects on the process This is repeated until the project is completed

  11. Deployed At any given point, the product is “deployable”

  12. Agile ignores risk Truth Or Misconception

  13. Advantages of Scrum • Manages risk by delivering high value, high risk items early • Identify and resolve problems faster • Showing tangible results throughout the project • High assurance of product vision due to continual inspection by business representatives • Adaptability (Scrum) versus Predictability (Waterfall) • Waterfall makes it expensive to make changes to the project • Scrum development minimizes the cost of change • Quality is built in • Continuous improvement

  14. Software Development From http://www.defendmusic.com/thebiglie.php CHANGE IS EXPENSIVE

  15. Agile and the PMBOK are not compatibleAgile and EVM are not compatibleAgile and CMMI are not compatible Truth Or Misconception

  16. PMBOK 3rd Edition Chapter 1 – Section 1.1 “Good practice does not mean that the knowledge described should always be applied uniformly on all projects; the project management team is responsible for determining what is appropriate for any given project.” PMBOK vs Agile

  17. …from Sliger, PMI Global Congress 2008 North America PMBOK vs Agile

  18. PMBOK vs Agile

  19. PMBOK vs Agile

  20. PMBOK vs Agile

  21. PMBOK vs Agile

  22. Development • EVM is not inherently anti-Agile, issues are with implementations of EVM • Phase based on a waterfall SDLC • Not being able to change line items • Measurement of value Req From this to this… Design Requirements Dev Development QA Release EVM Timeline EVM Timeline To this…. Requirements Development EVM Timeline Agile and EVM

  23. CMMI Level 2 CMMI Level 3 Agile and EVM

  24. Agile does not believe in metricAgile does not believe in documentation Truth Or Misconception

  25. Agile Metrics

  26. Metrics for the Project

  27. Metrics for the Iteration

  28. Metrics for the Team

  29. Metrics for business initiatives First Quarter Initiatives Metrics for Business Initiatives

  30. Metrics for business value • Metrics for Business Value

  31. Identifying and delivering value…… • Identify value and eliminate waste • Prioritize features • Deliver early and often • Constant inspection • Empower team • Documentation

  32. Agile requires pair programming • Agile does not scale across the enterprise or large applications • Agile does not work in the Federal government • ………

  33. Richard K Cheng richard.cheng@excella.com 703-967-8620 http://www.excella.com http://www.Excella.com/blogs/richardcheng http://www.OneMoreAgileBlog.com My contact information

More Related