Getting Started with Agile Project Management Principles
•Download as PPTX, PDF•
1 like•149 views
An introduction to the philosophy behind Agile project management, and a few simple ways that you can start to implement Agile in your own projects.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Getting Started with Agile Project Management Principles
Similar to Getting Started with Agile Project Management Principles (20)
Recently uploaded
Recently uploaded (20)
Getting Started with Agile Project Management Principles
- 1. Getting ‘Agile’. The Principles of Agile Project Management
- 3. A philosophy not a methodology.
- 4. 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 Source: http://agilemanifesto.org/principles.html
- 5. What does that look like in practice? - Adaptive planning - Evolutionary development - Early (and frequent) delivery - Continuous improvement - Flexible response to change
- 6. Agile Products Where do we start? Prioritised Requirements List (PRL) Iterative development & deployment User Stories
- 7. User Story Cards As a (role) I need (requirement) So that (goal/business need) > Acceptance criteria
- 8. User Story Cards As a donor I need to make a quick decision about a single / regular gift So that I can complete my donation to the HF > Information and decision in under 30 seconds.
- 10. Core Agile Principle “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
- 11. Don't Agile overkill. :(
Editor's Notes
- Using Agile in projects isn't always appropriate, and not all businesses are ready to fully recognise an Agile philosophy. However there are ways in which we can slowly begin to introduce Agile Principles and Products into our current project environments. These are examples for those products and principles.
- User stories are a great way to keep your work focused on the needs of the end user. User Story Cards in this format (with more detail) can be used to keep track of multiple features and deliverables within a project increment. The cards outline the detail of the core user need for that feature, and the 'acceptance criteria’ or measure used to confirm completion.
- Traditional project management places emphasis primarily on the ‘features’ of a product or service - and often time and cost will be sacrificed to ensure delivery of those features. The Agile approach flips this on its head; features are prioritised (using MoSCoW for example) and can dropped during development if deemed by the team to be non-essential.