Downloaded 17 times
Uploaded bySteve Nunziata
Is Project Management Discipline Relevant in an Agile World?
The document discusses the relevance of project management discipline in an agile environment, emphasizing its critical role in successful agile project execution. It outlines agile principles and methods, how they relate to traditional project management processes, and the importance of lean principles in enhancing project outcomes. Ultimately, it concludes that applying project management creatively within agile frameworks can lead to greater success in project execution and enterprise adoption.
More Related Content
Similar to Is Project Management Discipline Relevant in an Agile World?
![Agile Project Management 1 17 2007[1]](https://cdn.slidesharecdn.com/ss_thumbnails/agileprojectmanagement11720071-13212136679535-phpapp01-111113134955-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Is Project Management Discipline Relevant in an Agile World?
- 1. Is Project ManagementDiscipline Relevant in an Agile World? STEVE NUNZIATA, PMP, ACP, CSM, CSP, SAFE SPC ENTERPRISE AGILE COACH APRIL 25TH, 2016
- 2. About Steve… 1990 -2005 2006 - 2016
- 3. Why are WeHere?
- 4. ‘Agile’ vs. ProjectManagement
- 5. Successful Agile ProjectManagement
- 6. Today’s Premise Project Management disciplineis a critical component in Agile project execution and Enterprise adoption.
- 7. Definition of Terms ProjectManagement discipline – the intent, or outcomes, behind PMI’s 10 knowledge areas, and the value that they provide.
- 8. Today’s Objective Empower youfor Success in Agile Projects: • By understanding WHAT Agile is, and WHY it works • By providing real examples of Project Management process & practice applied in an Agile context
- 9. Cornerstone of Agility– Lean Principles 1. Eliminate Waste 2. Amplify Learning 3. Decide as Late as Possible 4. Deliver as Fast as Possible 5. Empower the Team 6. Build Integrity in 7. See the Whole
- 10. Core Lean Principles- Defined Eliminate Waste Amplify Learning
- 11. Lean Principle –Eliminate Waste Incomplete Work Task Switching Defects
- 12. Lean Principle –Amplify Learning Idea Build Measure Learn
- 13. Small Batches toAmplify Learning Reduces Risk & Variability Shortens Cycle Time – Market & Feedback Problems are Instantly Localized Increased Quality – Less Defects
- 14. Large Batches –Infrequent Learning Months 1-3 Months 7-9 Months 4-6 Months 10-12
- 15. Agile Defined 1) ‘Agile’is a term that represents a family of Principle driven, Adaptive Frameworks (a.k.a. ‘Methods’).
- 16. Agile Defined Image: HenrikKniberg (http://blog.crisp.se/author/henrikkniberg) Agile Frameworks are Inherently Incomplete
- 17. Agile Methods inProject Execution Agile Methods (‘Factory’) Project Management Disciplines & Other Critical Processes Project
- 18. Recipe for Successwith Agile 1. Understand Context 2. Choose an Agile Method 3. Augment as Necessary 4. Test, Learn, Adjust
- 19. Agile Defined 1) ‘Agile’is a term that represents a family of Principle driven, Adaptive Frameworks (a.k.a. ‘Methods’). 2) Agile is characterized by Iterative and Incremental build and delivery, in adherence with Lean Principles.
- 20.
- 21. Agile – LeanPerspective • Scrum, Extreme Programming (XP), Kanban, and other Agile Methods can be considered as partial manifestations of Lean. • Each Agile method has constructs (ceremonies, roles, processes) aligned closely to Lean Principles.
- 22. The Scrum Cycle SmallBatch of Software Small Batch of Information• Minimize Waste • Amplify Learning
- 23. Agile Defined 1) ‘Agile’is a term that represents a family of Principle driven, Adaptive Frameworks (a.k.a. ‘Methods’). 2) Agile is characterized by Iterative and Incremental build and delivery, in adherence with Lean Principles. 3) Agile methods also ascribe to the values formalized in the Agile Manifesto.
- 24.
- 25. Quick Test -Quotes from ‘The Field’ “We have our Daily Standup every Friday.” “We demonstrate our work every two weeks, just without the primary customer.” “No, really, the project was 90% complete last week. Now we’re about 60% complete.” “Our first Sprint was Analysis, our second Sprint was Design... We hope to Code in our third.”
- 26.
- 27. Definition of Terms Plannedset of interrelated tasks, executed over a fixed time period, constrained by certain cost parameters. A temporary endeavor undertaken to create a unique product, service or result. proj·ect noun ˈpräjˌekt/
- 28. Observation Project Management processes, asdefined, inherently assume a Waterfall execution approach, as evidenced by the high degree of formality and prescriptiveness.
- 29. The Waterfall Biasin Project Management “The Project Manager must be able to develop a fully integrated information and control system to plan, instruct, monitor and control large amounts of data, quickly and accurately to facilitate the problem- solving and decision- making process.” -- Rory Burke
- 30. Agile Methods inProject Execution Small, Informal Batches Large, Formal Batches Project
- 31. Resolving the WaterfallBias in Agile In Agile… What can a Project Manager bring to the table?
- 32. PMBOK Knowledge Areas Knowledge Areas Stakeholder Procurement Communications Risk Human Resources Quality Integration Scope Time Cost 1)Cost 2) Time 3) Scope 4) Integration 5) Quality 6) Human Resources 7) Communications 8) Risk 9) Procurement 10)Stakeholder
- 33.
- 34. Communications Discipline Traditional WaterfallCommunications Plan
- 35. Communications in Agile •Agile methods support small Teams of 5 to 9 individuals • Agile methods prefer generalists over specialists • Agile ceremonies facilitate knowledge transfer – in small batches
- 36. Transparency – CoreAgile Tenet
- 37. Agile Communication Methods •Daily Standup (15 min) • Sprint Planning (Day 1 Sprint) • Demonstration (Day X Sprint) • Retrospective (Day X Sprint) • Pair Programming (XP)
- 38. Conclusion – AgileCommunications Agile methods provide a solid framework for knowledge transfer. Augment only if necessary!
- 39. Risk Management Discipline IdentifyAssess Respond Review
- 40. Risk Management Discipline TraditionalWaterfall Project Management Risk Register
- 41. Agile Risk Register 36 9 2 4 6 1 2 3 Vendor may not deliver critical component in timeM Impact Probability
- 42. Scrum Ceremonies &Risk Management Graphic: www.agilelearninglabs.com
- 43. Conclusion – AgileRisk Management Lightweight Risk Management methods can effectively manage risk by minimizing waste and amplifying learning.
- 44. Today’s Premise Project Management disciplineis a critical component in Agile project execution and Enterprise adoption.
- 45. Conclusion Project Management discipline, applied creativelyin adherence with Lean principles, can amplify success in Agile project execution and Enterprise adoption.
- 46.
- 47.