Agile applied to project management
Download as PPTX, PDF0 likes83 views
The document introduces agile project management, contrasting it with the traditional waterfall approach and emphasizing its principles, such as customer satisfaction, adaptability, and frequent delivery of valuable software. It outlines key concepts, methodologies like Scrum and Lean, and the importance of a collaborative mindset and effective communication. Additionally, it explains the agile manifesto and the three pillars of empiricism: transparency, inspection, and adaptation.
Agile applied to project management
- 1. Agile Project Management An introduction by Simon Carter
- 2. Contents ● Agile applied to Project Management ○ What is it? ○ Waterfall and Agile ○ The Agile Manifesto ○ Three pillars of empiricism ○ Applying these in principle
- 3. Agile applied to Project Management
- 4. Agile does not mean deliver projects faster!
- 5. Agile does deliver value faster
- 6. Agile does not mean no governance or documentation
- 7. Agile means only generating the needed, and relevant, meetings and documents
- 8. What is it? ● Set of methods and methodologies ○ Scrum, XP, Lean ○ Fast feedback ○ Information radiators ○ Timeboxes ○ Retrospectives ● Mindset ○ Fast feedback of all types - to reduce risk, respond to change quickly, catch problems early, improve quality ○ Collaboration ○ Cross functional ○ Adaptable ○ Team decide how best to develop the solution ○ Servant-leader approach, trust the team to deliver
- 9. Side by side comparison ● Waterfall ○ Plan driven ○ Deterministic ○ Linear ○ Feedback at set points ○ Benefits at the end (‘big bang’) ○ Fail – not until the end? (big splat?) ○ Command & control ○ Controller, director ○ Control/avoid change ● Agile ○ Value driven ○ Evolutionary ○ Iterative & incremental ○ Fast feedback ○ Early benefits ○ Fail fast (good thing!) ○ Self organising, collaborative ○ Enabler, facilitator ○ Embrace change (it’s a good thing!)
- 10. The Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan
- 11. Agile Principles 1. Satisfy the customer through continuous delivery of valuable software 2. Welcome changing requirements, harness change for the customer's competitive advantage 3. Deliver working software frequently, from a couple of weeks to a couple of months 4. Business people and developers must work together 5. Motivate individuals. Give them the environment and support they need 6. The most effective method of conveying information is face-to-face conversation 7. Working software is the primary measure of progress 8. Agile processes promote sustainable development 9. Continuous attention to technical excellence and good design enhances agility 10. Simplicity--the art of maximizing the amount of work not done--is essential 11. The best architectures, requirements, and designs emerge from self-organising teams 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly
- 12. Three pillars of empiricism: ● Transparency ● Inspection ● Adaptation
- 13. Applying these in principle ● Shorten feedback loops ● More customer involvement ● Framework agnostic ○ XP ○ Scrum ○ Lean ○ Agile PF/DSDM ○ PRINCE2 ● Ask the team which tools work
- 14. Planning Horizons Iteration Plan Daily Plan Product Plan Release Plan Portfolio Plan Every day during daily stand-up Every sprint by the development team and the product owner Every release by the development team and the product owner Bi-yearly by the product owner Yearly by the product owner
- 15. Recap ● Agile applied to Project Management ○ What is it? ○ Side by side comparison ○ The Agile Manifesto ○ Agile Principles ○ Three pillars of empiricism ○ Applying these in principle ○ Boards and burndowns ○ Planning Horizons
- 16. Questions?