Agile Philosophy and Principles Flashcards
What is the Agile Philosophy?
Best business value emerges when projects are
aligned to clear business goals, deliver frequently
and involve the collaboration of motivated and empowered people
What are the 5 principles of Agile Philosophy?
- Process
- People
- Products
- Practices
- Common sense and pragmatism
How is the philosophy of Agile achieved by all stakeholders?
When they:
- Understand and buy into the business vision and objectives
- Are empowered to make decisions within their area of expertise
- Collaborate to deliver a fit for purpose business solution and to deliver to agreed timescales in accordance with business priorities
- Accept that change is inevitable as an understanding of the solution grows over time
What are the 4 key variables for traditional and DSDM projects?
Feature/Scope
Quality
Time
Cost/Budget
Which variables are fixed in traditional vs DSDM projects?
Traditional - Features and partially quality
DSDM - Time, Quality & Cost
What project variable is variable in the DSDM approach?
Features
What are the 8 principles of DSDM Agile?
1) Focus on the Business Need
2) Deliver on Time
3) Collaborate
4) Never Compromise Quality
5) Build Incrementally from Firm Foundations
6) Develop Iteratively
7) Communicate Continuously and Clearly
8) Demonstrate Control
What does the Focus on the Business Need principle aim to ensure?
PM ensures Solution Development Team members:
• Understand and respect true business priorities
By ensuring correct application of MoSCoW prioritization
• Establish the valid business case
• Ensure continuous business sponsorship and commitment
• Guarantee delivery of Minimum Usable SubseT
What does the Deliver on Time principle aim to ensure?
PM ensures Solution Development Team members:
• Timebox the work
• Focus on business priorities
• Always hit deadlines
• Build confidence through predictable delivery
What does the Collaborate principle aim to ensure?
PM ensures Solution Development Team members:
• Involve the right stakeholders at the right time throughout the project
• Encourage proactive involvement from business representatives
• Ensure all team members are empowered to take decisions on behalf of those they represent
• Build a one-team culture
What does the Never Compromise Quality principle aim to ensure?
PM ensures Solution Development Team members:
• Agree the level of quality from outset, before development starts
• Ensure quality does not become a variable
• Test early, test continuously and test to appropriate level
• Design and document appropriately
What does the Build Incrementally from Firm Foundations principle aim to ensure?
PM ensures Solution Development Team members:
• Do appropriate analysis and enough design up front (EDUF) to create strong foundations for all subsequent work
• With each delivered Increment: Formally reassess priorities & Informally reassess ongoing project viability
What does the Develop Iteratively principle aim to ensure?
PM ensures Solution Development Team members:
• Build business feedback into each iteration
• Recognise that most detail should emerge later, rather than sooner
• Embrace change: The right solution will not evolve without it
What does the Communicate Continuously and Clearly principle aim to ensure?
PM ensures Solution Development Team members:
• Make full and proper use of DSDM practices e.g. Workshops, Modelling, Timeboxing with daily Stand-ups
• Provide opportunities for those interested to keep themselves informed
about project through visible activity and outputs
• Keep documentation lean and timely: Only create it where it adds genuine value to solution
• Manage stakeholder expectations at all levels: Ideally through involvement in DSDM process
• Always aim for honesty and transparency: Within team and external to project team
What does the Demonstrate Control principle aim to ensure?
PM ensures Solution Development Team members:
• Make plans and progress visible to all
• Measure progress through focus on delivery of products: Rather than completed activities
• Use appropriate level of formality for tracking and reporting: Allowing project-level roles to continually assess viability of project
