1 / 12

Agile Training Game

Training Solutions. Agile Training Game. v. 7.3.1. Only 16% of projects finished on-time, on-budget with originally defined scope. Trouble With Traditional Project Approach. Some Interesting Findings:

shelby-hensley
Download Presentation

Agile Training Game

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. Training Solutions Agile Training Game v. 7.3.1

  2. Only 16% of projects finished on-time, on-budget with originally defined scope Trouble With Traditional Project Approach Some Interesting Findings: A study of 8,300+ projects completed by large American companies using traditional methodologies revealed: Only 42% of features originally proposed are implemented Most Common Reasons for Failure: • Incomplete or changing requirements • Lack of User Input FACT!66% of Product Features are rarely, if ever, used. FACT!80% of a Product’s Features are added after the first release

  3. Agile Software Development processes were first formulated in the early 1990’s The Agile core set of values was articulated in the Agile Manifesto in 2001We Value: Individuals and interactions over processes and tools Working software over comprehensive 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” Agile processes present light-weight methodologies that focus on incremental, iterative development Agile implementations focus on rapid value delivery, minimizing waste and continuous improvement What is Agile?

  4. Faster Release Cycles Reduced time to market Better Productivity Team focused on product development Increased Quality Quality controls embedded throughout lifecycle Focus on Delivering True Value Value can only be recognized in the form of completed product Responsive to Change No change control process required Goals of Agile

  5. Focus on Business Objectives Deliver maximum business value Measure Progress in the Form of Completed Product Tested, customer-accepted product Build a Culture of Continuous Improvement Continuous incremental gains Responsive to Feedback and Learning Facilitates changes that improve product Maximize Team Productivity Laser-focus on delivering product Why does it work?

  6. Deliver customer value early and often Frequent, iterative delivery of accepted product Embrace change Closely integrated team Minimize waste Strive for highest level of collaboration Success is built around motivated self-organizing teams Continuously seek ways to improve The Agile Principles

  7. Traditional/Waterfall Process Typical Waterfall/Traditional SDLC Deliverable: Requirements Document Analysis Deliverable: Design Specification Design Deliverable: Integrated Code Development Deliverable: Tested, Accepted Product QA

  8. Analysis Design Development QA Waterfall/Traditional Value Delivery Analysis Design Development QA

  9. In traditional projects: Maximum value is achieved at product launch Launch Analysis Design Development QA In traditional projects: Value is only delivered at the completion of the QA phase of the project. In traditional projects: Real value cannot be recognized during the majority of the process 2 4 6 8 10 12 14 16 Waterfall/Traditional Value Delivery Value/Quality Software Delivered Analysis Design Development QA Value Growth: Traditional Project 0 Week

  10. Reduce Risk Minimize Business Risk Minimize Product Risk Minimize Project Risk Launch Launch Launch 2 4 6 8 10 12 14 16 Agile Value Delivery In Agile projects: Frequent integration at the end of each iteration ensures product quality early in the product lifecycle In Agile projects: Customer realizes value as early as the completion of the first iteration Value/Quality Software Delivered In Agile projects: Each iteration delivers incremental functionality intended to continuously reflect the customer chosen direction for the product 0 Week

  11. Deliver customer value early and often Frequent, iterative delivery of accepted product Embrace change Closely integrated team Minimize waste Strive for highest level of collaboration Success is built around motivated self-organizing teams Continuously seek ways to improve The Agile Principles

  12. Agile Abandons all Rigor Agile is very rigorous in its principles Agile does not scale Agile has been scaled to hundreds of product developers Agile is not for Distributed Teams Agile supports the model of multiple distributed teams that adopt the same principals and practices Agile = ‘No Documentation’ Agile stresses product documentation Agile Focuses Cost Reduction Agile does not directly address project or resource costs Agile Ignores Architecture Agile stresses continuous architecture and design evolution Agile Means ‘No Planning’ Agile stresses the importance of short-term and long-term planning Common Agile Misconceptions

More Related