![Cause for
planning failure
in waterfall
Focus on completion of activity than delivery of feature.
On schedule review , focus is on forgotten activities than missed schedule
Activity based
Planning [not
feature based]
Multitasking cause delay
Features are not developed by priority.
Uncertainty is ignored and plan based on assumptions
The best way to deal with uncertainity is iterate.
Estimates becomes commitments. An estimate is a probability and
commitments cannot be a probability.](https://image.slidesharecdn.com/acpwhentouseagile-170517135020/75/When-to-use-agile-PMI-ACP-16-2048.jpg)
Uploaded byDavis Thomas
When to use agile (PMI ACP)
The document introduces Agile methodology, highlighting its core principles such as customer satisfaction, flexibility in scope, and collaborative team dynamics. It discusses the differences between Agile and traditional Waterfall approaches, emphasizing iterative planning and frequent re-evaluation of project goals. Additionally, it outlines the roles within Agile teams and the importance of communication and customer feedback throughout the development process.
More Related Content
Similar to When to use agile (PMI ACP)
When to use agile (PMI ACP)
- 1. Agile Methodology DAVISTHOMAS K PMP,ITIL ,CSP , CSM, CSPO Presentation on Intro to agile andAPM frame work
- 2.
- 3. What comes to yourmind when you think of Agile? Why should we go for agile ? Faster delivery Customer collaboration Stakeholder engagement NOT Stakeholder Management Scope is flexible, keeping time and cost fixed Collaborative self organized – Self managed team Less Documentation Face to Face interaction Design is Emergent in nature Internal Quality Shorter delivery cycle Fast Feedback from stakeholders Agile is based on progressive elaboration and rolling wave planning Incremental and Iterative development When the customer is unaware of requirements
- 4.
- 5.
- 6. Principles behind the AgileManifesto Source :agilemanifesto.org/principles.html
- 10. Agile Principles 1. Aim CustomerSatisfaction 2. Welcome the CR 3. Deploy work products frequently 4. Work as a team 5. Focus on motivated individuals 6. Promote F2F interaction 7. Measure progress based on working software 8. Maintain the pace 9. Follow good engineering practice 10. Generate desired value 11. Self organized team 12. Learn from Retrospective frequently
- 11.
- 12. Defined Process vs Empherical Process PredictableInput Defined Process Historical Predictable Output Unknown Input Empirical Process observation / experience Goal
- 13. Adaptive Life cycle When to useagile Measure the uncertainty in your project Iterative Life cycle Predictive Life cycle HIGHUNCERTAINONWHATTODO
- 14. TheAgile Paradigm Shift The definition of successis to keep all three things in perfect balance throughout the project. In waterfall Agile says that we'll fix the time and the cost for the effort. These are fixed, but the scope isn't. This is flexible
- 15.
- 16. Cause for planning failure inwaterfall Focus on completion of activity than delivery of feature. On schedule review , focus is on forgotten activities than missed schedule Activity based Planning [not feature based] Multitasking cause delay Features are not developed by priority. Uncertainty is ignored and plan based on assumptions The best way to deal with uncertainity is iterate. Estimates becomes commitments. An estimate is a probability and commitments cannot be a probability.
- 17. Agile Approach to project Works asa team, but roles filled by specific individuals Works in short time-boxed iterations Delivers valuable in each iterations and feedback is gathered Focus on business priorities Team inspects and adapts every iteration
- 18. Agile Approach to planning Agile teamuse three levels of planning Release Planning Iteration planning Daily planning Strategy Portfolio Product Release Iteration Day Team use daily standup meeting to coordinate work and synchronize daily efforts PO identifies high priority work, and dev team estimate for the iteration Release planning occurs at start of project Defines product vision and outlines road map for the product Defines overall product offering and how they integrate Defines the strategic business objective of organization
- 19. WhyAgile planning works Re-planning occursfrequently Estimate of Size and durations are separated Plans are made at different levels Plans are based on feature not task Project tracking is at team level Uncertainity is acknowledge and planned for
- 20. Do you buya car without test drive ?
- 21. Agile vs Waterfall Timelydelivery vs Delayed delivery Quality focused vs Lack of Quality Shorter delivery cycle vs Long time to market Customer collaboration vs Contract Negotiation Welcoming and inviting change vs Following a plan Aim to achieve customer goal vs Goal is to finish the project/Goal is to deliver agreed scope on time. Working software vs Comprehensive documentation Importance to Individual interaction vs following a defined process Visualization vs Reporting Scope is flexible vs fixed scope People helps and works as team vs Zylo environment
- 22. Agile vs Scrum Agile isa methodology whereas Scrum is an agile approach / Scrum is a framework of Agile.
- 23. SPECULATE EXPLOREADAPT ITERATION 0 CLOSE ENVISION OUTPUT RELEASE PLAN APMFramework FINAL PRODUCT COMPLETED FEATURES RELEASE PLANRELEASE PLANFEATURE LIST
- 24. What is Agile When to use agile Agile Framework Knowing and Using Kanban Scrum User Stories Estimation Value Based Prioritization Agile Planning Agile Monitoring Retrospective XP Lean Communication Risk Governance Soft Skills Agile and Project Management Doing Projects in Agile How Roles Changes in Agile PMI - Agile
- 25.