Agile Manifesto
The foundational statement that officially outlines agile's core values and guiding principles.
Key Points
- People and their collaboration matter more than strict tools or procedures.
- Delivering a working product outweighs producing extensive documentation.
- Close customer partnership is preferred over relying on contract terms alone.
- Adjusting to change is prioritized over rigidly following a fixed plan.
Example
A product team runs two-week iterations. After a customer demo reveals a new need, the product owner and team re-order the backlog, implement the most valuable change next, ship a usable increment, and capture only lightweight notes instead of heavy documents.
PMP Example Question
Midway through a release, a key stakeholder requests a shift in priorities based on new market insights. To align with the Agile Manifesto, what should the project manager do?
- Freeze scope to protect the baseline plan.
- Delay action until legal updates the contract.
- Reprioritize the backlog with the stakeholder and team, adapting the plan.
- Pause development to create comprehensive documentation first.
Correct Answer: C - Reprioritize collaboratively and adapt to change
Explanation: The Agile Manifesto favors customer collaboration and responding to change over contract negotiations, heavy documentation, or rigid adherence to a fixed plan.