Agile Principles (12 Principles)
The twelve Agile Principles are guiding statements behind the Agile Manifesto that describe how agile teams should operate, emphasizing early and continuous delivery of value, welcoming change, and sustainable development.
Know it well enough for the exam? Questions on Agile Principles (12 Principles) are scenario-based, not definitional.
Practice it freeExplanation
The twelve principles expand on the four Agile Manifesto values and provide actionable guidance for teams. They address topics such as delivering working software frequently, maintaining a sustainable pace, harnessing change for competitive advantage, and promoting face-to-face communication. Together they form the behavioral backbone of every agile approach.
Key themes across the principles include customer satisfaction through early and continuous delivery, welcoming changing requirements even late in development, delivering working increments frequently, close daily cooperation between business people and developers, and building projects around motivated individuals. The principles also emphasize simplicity, self-organizing teams, and regular reflection on how to become more effective.
For exam purposes, you do not need to recite all twelve principles word-for-word, but you should understand their intent and be able to identify which principle applies in a given scenario. PMI often tests whether candidates can distinguish between agile values and principles and apply them to real project situations.
Key Points
- •Highest priority is satisfying the customer through early and continuous delivery of valuable software
- •Welcome changing requirements, even late in development
- •Deliver working software frequently, with a preference for shorter timescales
- •The best architectures, requirements, and designs emerge from self-organizing teams
Exam Tip
Focus on the intent behind each principle rather than rote memorization. Exam questions test application of principles to scenarios, not verbatim recall.
Frequently Asked Questions
Related Topics
Agile Manifesto
The Agile Manifesto is a foundational document published in 2001 that establishes four core values and twelve principles for agile software development, emphasizing individuals, working software, customer collaboration, and responding to change.
Self-Organizing Teams
Self-Organizing Teams (also called self-managing teams in the 2020 Scrum Guide) are teams that determine the best way to accomplish their work without being directed by people outside the team.
Servant Leadership
Servant Leadership is a leadership philosophy where the leader's primary role is to serve the team by removing obstacles, providing resources, and creating an environment where the team can do its best work.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice Agile Principles (12 Principles)
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.