1.2.2: Agile Principles

Agile Project Management · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    1.2.2: Agile Principles

    The 12 Agile Principles

    The official Agile Manifesto site lists the 12 principles behind Agile, and Agile Alliance also presents them as the guiding practices for implementing Agile ways of working. I used those as the baseline and expanded them into the same textbook style. 

    The 12 Agile principles translate the Agile Manifesto from values into day-to-day behaviors.

    The Agile values tell us what matters. The Agile principles tell us how those values show up in real project work.

    The Agile Manifesto gives us four major value statements, but the 12 Agile principles explain how those values should influence the way teams actually work. These principles are especially important for the PMI-ACP exam because they help you choose the best response in scenario-based questions.

    The exam may not ask you to recite all 12 principles word for word. Instead, it may describe a team situation and expect you to recognize which Agile principle should guide the response. For example, if customers are not seeing progress until the end of the project, the relevant principle is early and continuous delivery. If the team is being forced to follow an outdated plan despite new market information, the relevant principle is welcoming change. If team members are burned out from constant overtime, the relevant principle is sustainable pace.

    Although the original principles refer to “software,” PMI-ACP applies the same thinking more broadly to products, services, deliverables, and business outcomes. In this book, you can read “working software” as “working product,” “usable increment,” or “valuable deliverable,” depending on the context.

    Principle 1: Satisfy the Customer Through Early and Continuous Delivery

    The first Agile principle says that the highest priority is customer satisfaction through early and continuous delivery of valuable work. This is the heart of Agile. The team should not disappear for months, build in isolation, and then surprise the customer at the end. Instead, the team should deliver useful increments frequently so the customer can see progress, provide feedback, and receive value sooner.

    Agile teams build trust by delivering value early, not by asking customers to wait until the end.

    Customers do not receive value from promises, plans, or status reports. They receive value when something useful is delivered.

    Early delivery reduces risk. If the team is building the wrong thing, it is better to discover that after two weeks than after two years. Continuous delivery also builds stakeholder confidence. Customers and sponsors are more likely to trust a team that demonstrates real progress regularly.For PMI-ACP, remember that customer value is more important than internal activity. A team may be busy, but if it is not delivering usable value, it is not truly succeeding.

    Principle 2: Welcome Changing Requirements

    Change is not automatically a disruption. Sometimes change is the signal that helps the team deliver the right thing.

    Traditional project management often treats change as a threat to the baseline. Agile treats change differently. Agile teams understand that customers, markets, technologies, and business priorities can change during the project. Rather than resisting all change, Agile teams evaluate change and use it to improve customer value.

    Agile teams treat change as useful information, even when it arrives late.

    This does not mean that every change is accepted immediately. The team still considers priority, effort, risk, dependencies, and timing. However, Agile teams do not reject change simply because it was not part of the original plan.

    This principle is especially important in competitive environments. If a competitor releases a new feature, customer expectations may change. If users test a prototype and dislike an assumption, the backlog may need to change. If new regulations appear, the product may need to adapt.

    When new information appears, do not blindly defend the old plan. Collaborate, inspect the impact, reprioritize, and adapt responsibly.

    Principle 3: Deliver Working Products Frequently

    The shorter the feedback loop, the faster the team learns whether it is building something valuable.

    Agile favors frequent delivery. Instead of waiting for one large final release, the team delivers smaller increments at regular intervals. These increments should be usable, testable, reviewable, or at least meaningful enough to generate feedback.

    Frequent delivery helps the team discover problems earlier. Technical issues, usability concerns, integration risks, and customer misunderstandings become visible sooner. This allows the team to correct course while there is still time.

    Agile teams reduce uncertainty by delivering small, usable increments on a regular rhythm.

    The principle also encourages smaller batches of work. Smaller batches are easier to plan, easier to review, easier to test, and easier to change. Large batches hide problems for too long.

    Principle 4: Business People and Developers Work Together Daily

    Agile fails when business and delivery teams throw work over the wall to each other.

    Agile teams need frequent collaboration between business stakeholders and development teams. The people who understand customer needs, business goals, compliance requirements, and market realities must stay connected with the people designing, building, testing, and delivering the solution.

    Agile requires close collaboration between those who understand the business need and those who build the solution.

    This principle prevents misunderstandings. If business stakeholders only define requirements at the beginning and return at the end, the team may build something technically correct but commercially useless. Daily or frequent collaboration helps clarify priorities, answer questions, resolve trade-offs, and keep the work aligned with value.

    In modern Agile environments, “business people” may include product owners, customers, sponsors, users, compliance experts, operations teams, marketing, sales, or other stakeholders.

    Principle 5: Build Around Motivated Individuals

    You cannot command creativity into existence. You create the conditions where motivated people can do their best work.

    Agile depends on motivated individuals. The team needs the right environment, tools, support, clarity, and trust. Leaders should not micromanage every task or decision. Instead, they should help the team understand the goal and then trust them to determine how best to accomplish the work.

    Agile teams perform best when people are trusted, supported, and given the environment they need to succeed.

    This principle connects directly to servant leadership. Agile leaders remove impediments, protect the team from unnecessary disruption, clarify priorities, and support team ownership.

    Trust is essential. A team that is constantly second-guessed will stop taking ownership. A team that is blamed for every problem will hide risks. A team that is trusted and supported is more likely to collaborate, innovate, and improve.

    Principle 6: Use Direct Communication Whenever Possible

    A five-minute conversation can prevent five days of confusion.

    The Agile principles emphasize direct conversation as one of the most effective ways to share information. In the original Manifesto, this was described as face-to-face conversation. In modern distributed teams, the same idea can include video calls, collaborative working sessions, whiteboarding tools, pairing, workshops, and real-time discussions.

    The point is not that documentation is bad. The point is that complex problems are often solved faster through conversation than through long chains of written clarification. Documents can support understanding, but they should not replace collaboration.

    Agile favors fast, clear, human communication over slow and indirect handoffs.

    This principle is particularly useful when requirements are unclear, conflict exists, or the team needs rapid feedback. Instead of sending messages back and forth for days, Agile encourages people to talk directly and resolve ambiguity quickly.

    Principle 7: Working Product Is the Primary Measure of Progress

    A project is not truly progressing just because documents are complete, meetings are held, or tasks are marked green.

    In Agile, the clearest measure of progress is a working product or usable increment. This does not mean planning, design, documentation, and analysis are unimportant. They are useful when they support delivery. But they are not the final proof of progress.

    Agile progress is measured by usable outcomes, not by how much activity has occurred.

    A team may say it is 80% done because many tasks are complete. But if nothing works yet, the customer has not received value. Agile prefers evidence that the product is actually functioning and moving toward the desired outcome.

    This principle helps prevent false progress. A project can look healthy on a status report while hiding integration problems, quality issues, or misunderstood requirements. A working increment exposes reality.

    Principle 8: Maintain a Sustainable Pace

    A team that burns out this month will not be faster next month.

    Agile promotes sustainable development. Sponsors, team members, and users should be able to maintain a steady pace over time. This principle rejects the idea that success requires constant overtime, weekend work, and emergency pressure.

    Agile delivery should be steady and sustainable, not dependent on constant overtime and heroics.

    Short bursts of extra effort may sometimes happen, but they should not become the operating model. If a team can only meet commitments through exhaustion, the system is broken. Burnout reduces quality, creativity, morale, and long-term predictability.

    Sustainable pace also supports better planning. A team that works at a realistic pace can understand its true capacity. A team that constantly relies on heroics cannot forecast reliably.

    Principle 9: Pursue Technical Excellence and Good Design

    The faster you want to adapt, the more important quality becomes.

    Agile is not just about moving quickly. It is about being able to change direction without collapsing under the weight of poor quality. Technical excellence and good design make future change easier.

    Agility depends on quality; weak design and poor engineering make change harder.

    If a product is poorly designed, every new feature becomes risky. If testing is weak, defects increase. If code, architecture, or process quality is ignored, the team accumulates technical debt. Eventually, the team slows down because every change breaks something else.

    This principle reminds us that Agile speed should not come from cutting quality. Agile speed comes from reducing waste, improving feedback, keeping work small, and maintaining a strong technical foundation.

    For non-software projects, technical excellence may mean professional standards, quality practices, sound design decisions, compliance discipline, operational readiness, or craftsmanship.

    Principle 10: Maximize Simplicity

    The most efficient feature is the one you discover you do not need to build.

    Simplicity is one of the most powerful Agile ideas. Agile teams should maximize the amount of work not done. This means avoiding unnecessary features, excessive documentation, over-engineered solutions, low-value approvals, and gold-plating.

    Agile teams focus on the simplest thing that delivers value and avoid unnecessary work.

    Customers may ask for many things, but not all requested features create equal value. Agile teams use prioritization, feedback, and experimentation to identify what truly matters. The goal is not to build everything. The goal is to build the right things.

    Simplicity also reduces risk. A smaller solution is easier to test, easier to change, easier to explain, and easier to maintain. Overly complex solutions often create hidden costs.

    Principle 11: Self-Organizing Teams Create the Best Solutions

    The people closest to the work often understand the work best.

    Agile principles emphasize self-organizing teams. This means the team has the authority and responsibility to decide how to deliver the work. Leaders and stakeholders clarify goals, priorities, and constraints, but they do not micromanage every task.

    Agile teams are trusted to decide how best to accomplish the work.

    Self-organization increases ownership. When teams participate in planning and decision-making, they are more committed to the outcome. They also adapt faster because they do not need approval for every small decision.

    This principle does not mean the team does whatever it wants. The team still works within organizational goals, product priorities, compliance constraints, and customer needs. Self-organization means autonomy with alignment.

    Principle 12: Reflect and Adjust Regularly

    A team becomes Agile not because it is perfect, but because it keeps improving.

    The final Agile principle focuses on continuous improvement. At regular intervals, the team reflects on how to become more effective and then adjusts its behavior. This is the foundation of retrospectives.

    Agile teams improve by pausing, learning, and changing their behavior.

    Reflection alone is not enough. The team must also act. A retrospective that produces no change becomes a ritual without value. Effective teams identify improvement opportunities, select a small number of actions, and follow through.

    This principle applies to process, collaboration, quality, tools, stakeholder engagement, estimation, planning, and team health. Agile teams do not assume their current way of working is perfect. They inspect and adapt not only the product, but also the process.Key Takeaways

    Grouping the 12 Principles for Easier Memory
    • The 12 principles become easier to remember when grouped into themes. Do not memorize the principles as isolated sentences. Understand the patterns behind them. The 12 Agile principles can be grouped into six major themes.
    • Customer value: Principles 1, 2, and 3 emphasize customer satisfaction, welcoming change, and frequent delivery.
    • Collaboration: Principles 4 and 6 emphasize close communication between business and technical people.
    • Team empowerment: Principles 5 and 11 emphasize motivated individuals, trust, support, and self-organization.
    • Evidence of progress: Principle 7 reminds us that working products are the primary measure of progress.
    • Sustainable quality:  Principles 8 and 9 emphasize sustainable pace, technical excellence, and good design.
    • Continuous improvement and simplicity:  Principles 10 and 12 emphasize reducing waste, keeping work simple, reflecting, and improving.

    On the exam, the wrong answer is often not ridiculous. It is usually a predictive answer dressed in professional language.

    Common Exam Traps

    Watch for these common traps.

    1. A question may suggest that the team should reject late changes because the plan has already been approved. This violates the principle of welcoming change.
    2. A question may suggest that progress should be measured mainly by completed documentation or percentage of tasks finished. This violates the principle that working product is the primary measure of progress.
    3. A question may suggest that the project manager should assign all tasks to team members. This violates the principle of self-organizing teams.
    4. A question may suggest that the team should work nights and weekends to meet an unrealistic commitment. This violates the principle of sustainable pace.
    5. A question may suggest that the team should build every requested feature because stakeholders asked for them. This violates the principle of simplicity and value-based prioritization.
    6. A question may suggest that business stakeholders should provide requirements upfront and then return only at the end. This violates the principle of continuous collaboration.
    7. A question may suggest that quality can be reduced to go faster. This violates the principle of technical excellence and good design.

    When you see these traps, return to the Agile principles. The best PMI-ACP answer usually supports early value, collaboration, empowered teams, sustainable delivery, quality, simplicity, and continuous improvement. For PMI-ACP, this principle often appears when the team repeatedly faces the same issue. The correct answer is usually not to blame individuals. It is to inspect the process, identify root causes, and improve the system.


    This page titled 1.2.2: Agile Principles was last modified on Sun, 07 Jun 2026 22:37:03 GMT and is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Guharaman Janakiraman.