AgilePM Foundation · Domain 1 of 10

AgilePM Foundation Domain 1: Key agile concepts

The why behind every AgilePM question: business agility in a VUCA world, the four Agile Manifesto values and twelve principles, and why running a project is a bigger job than building a product.

Exam weight estimate
Not published
Official syllabus topics
3
Estimated questions estimate
~5
Suggested study time estimate
3–4 hrs

About 15 min read Reviewed October 2026

Overview

Key agile concepts is the starting point of the AgilePM v3 Foundation syllabus. It explains why organisations need business agility, the ability to sense and respond to change quickly, when their environment is volatile, uncertain, complex and ambiguous (VUCA). It then covers the Agile Manifesto: four value statements and twelve principles written in 2001 for software teams, which AgilePM reads in a project context covering business change as well as software.

The third idea sets the scope of the whole framework. Product development methods such as Scrum tell a team how to build and improve a product in short cycles, but a project also needs a business case, funding, governance, deployment into the business and a point at which benefits are judged. AgilePM exists to supply that project layer around agile delivery, and every later area (principles, roles, lifecycle, planning, governance) builds on the distinction made here.

How it's tested

Foundation questions here are short, closed-book recall and understanding items: identify the correct Manifesto value, recognise a statement that matches or contradicts an agile principle, or pick the reason a project needs more than a product delivery method. Distractors usually overstate agile (eliminate documentation, never plan) or misquote the Manifesto by a single word.

  • Which value or principle fits

    A short statement or behaviour is given and you match it to the Manifesto value or principle it expresses, or spot the one that contradicts it.

  • Overstated agile distractors

    Options claim agile removes plans, documents or contracts entirely; the correct option keeps them but values the left-hand items more.

  • Project vs product scope

    You choose what a project framework adds beyond a product delivery method, such as business justification, governance or deployment and benefits.

Reasoning it through

A question asks which statement reflects the Agile Manifesto's view of plans. One option says agile teams do not plan; another says plans are fixed once approved; a third says responding to change is valued more than following a plan. Read the Manifesto literally: both sides have value and the left side wins when they conflict. Only the third option keeps that balance, so it is correct, and the 'no planning' option is the classic overstatement.

Syllabus topics 3

Official syllabus topics from the APMG International outline, in outline order.

1.1 Business agility and why projects must respond to VUCAWhy volatile, uncertain, complex and ambiguous conditions push organisations toward agile projects.
What it means
VUCA stands for volatility, uncertainty, complexity and ambiguity: conditions in which requirements, markets and technology change during a project. Business agility is the organisation's ability to sense those changes and respond quickly and effectively, and agile projects are one of the main ways it does so.
What to understand
Under VUCA a fixed, fully specified plan is likely to be wrong before delivery ends, so the response is to deliver in small increments, get feedback early and keep the option to change direction. Agility is a business capability, not just a delivery-team habit.
How it shows up
A question describes a market or regulatory change mid-project and asks which approach or benefit agility offers; the answer centres on early, incremental value and the ability to adapt.
Common confusion
Treating business agility as a synonym for speed; it is about responsiveness to change, and moving fast in the wrong direction is not agility.
1.2 The Agile Manifesto and its principles in a project contextThe four values, the twelve principles, and how a project reads them.
What it means
The Manifesto values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan, while stating that the items on the right still have value. Twelve principles expand these, such as early and continuous delivery of valuable software, welcoming changing requirements, and working software as the primary measure of progress.
What to understand
In a project context 'working software' generalises to a working solution, which may include business processes and people changes. The word 'over' means preference when the two conflict, not elimination of the right-hand item.
How it shows up
You are shown a team behaviour or a statement and asked which value or principle it supports or violates, often with options that differ by one word.
Common confusion
Reading the Manifesto as 'no documentation, no plans, no contracts', when it explicitly keeps value in those items.
1.3 How agile project management differs from product development aloneWhy a project needs a management layer around an agile product delivery method.
What it means
Product development methods such as Scrum focus on a team building and improving a product in short cycles. A project is a temporary undertaking with a business case, defined scope of change, funding, governance, deployment into live use and benefits to assess, and it may involve several teams.
What to understand
AgilePM v3 positions Scrum as the product delivery engine and adds the project layer: business justification, lifecycle phases before and after development, project-level roles and governance. Neither replaces the other; they work at different levels.
How it shows up
A question asks what AgilePM provides that a team-level method does not, and the right answer names a project concern such as feasibility, governance, deployment or benefits.
Common confusion
Assuming AgilePM is an alternative to Scrum that competes with it, rather than a framework that wraps it.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

  • VUCA

    Volatility, uncertainty, complexity and ambiguity describe conditions in which the facts a plan relies on can change while the project is still running.

    Remember
    The four letters stand for volatility, uncertainty, complexity and ambiguity, and together they are the argument for incremental, feedback-driven delivery.
    Tested as
    Questions use VUCA as the reason a fixed up-front specification is risky and agility is valuable.
    Trap
    Expanding the acronym wrongly, for example as 'velocity' or 'urgency', which a distractor may offer.

  • Business agility

    Business agility is an organisation's ability to sense change in its environment and respond quickly and effectively, delivering value as conditions shift.

    Remember
    It is an organisational capability measured by responsiveness and value, not by how fast a single team codes.
    Tested as
    It frames why AgilePM exists and why projects should deliver value in increments rather than one big release.
    Trap
    Equating agility with speed alone, which ignores the sense-and-respond part.

  • The four Manifesto values

    Individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan.

    Remember
    Learn the exact pairs and their order, because distractors swap the sides or pair the wrong items.
    Tested as
    Direct recall items and behaviour-matching items both depend on knowing the pairs precisely.
    Trap
    Pairing 'working software' with 'contract negotiation' or putting a right-hand item on the left.

  • 'Over' means preference

    The Manifesto states that while there is value in the items on the right, the authors value the items on the left more.

    Remember
    The right-hand items are kept, just ranked lower when there is a conflict.
    Tested as
    Many distractors claim agile removes plans, documentation or contracts entirely.
    Trap
    Choosing an option that says agile teams 'do not' document or plan.

  • Working software as the primary measure of progress

    One of the twelve principles says progress is measured by working output, not by documents produced or tasks marked complete.

    Remember
    In AgilePM's project reading, demonstrable working parts of the solution are the evidence of progress.
    Tested as
    Linked to how progress is tracked later in planning and control questions.
    Trap
    Accepting percentage-complete reports on unfinished work as equivalent evidence.

  • Welcome changing requirements

    The principles say agile processes welcome changing requirements, even late in development, to give the customer a competitive advantage.

    Remember
    Change is expected and harnessed for value, which is why detail is deferred until it is needed.
    Tested as
    Appears when a scenario introduces a late change and asks for the agile response.
    Trap
    Treating any late change as scope creep that must be refused.

  • Frequent delivery, shorter timescale preferred

    The principles call for delivering working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.

    Remember
    Short delivery cycles give early feedback and earlier value.
    Tested as
    Supports timeboxing and incremental deployment questions in later areas.
    Trap
    Thinking the Manifesto sets a fixed iteration length; it states a preference, not a rule.

  • Project vs product

    A product method guides building and evolving a product, while a project is a temporary undertaking with a business case, governance, deployment and benefits.

    Remember
    AgilePM supplies the project layer and uses Scrum for product delivery inside it.
    Tested as
    Questions ask what AgilePM adds that Scrum alone does not provide.
    Trap
    Picking an option that describes a team-level practice, such as the Daily Scrum, as a project-level addition.

  • Simplicity

    The principle defines simplicity as the art of maximising the amount of work not done.

    Remember
    Avoiding unnecessary work is an explicit agile goal, which links to prioritising only what delivers value.
    Tested as
    Can appear as a principle-matching item or behind a gold-plating scenario.
    Trap
    Reading simplicity as 'minimal quality' rather than 'minimal unnecessary work'.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Manifesto left side vs. right side

ConceptMeaningKey differenceCommon trap
Individuals and interactions over processes and tools People talking directly solve problems faster than process alone Processes and tools still exist but serve the people Concluding that agile projects have no defined process
Working software over comprehensive documentation Demonstrable output is the best evidence of progress Documentation is kept where it adds value Choosing 'agile teams produce no documentation'
Customer collaboration over contract negotiation Ongoing joint work beats arguing over contract terms Contracts remain; collaboration governs the day to day Thinking agile cannot be used under a contract
Responding to change over following a plan Adapting to new information beats sticking to an outdated plan Plans exist and are revised as learning occurs Choosing 'agile projects do not plan'

Product delivery method vs. agile project framework

ConceptMeaningKey differenceCommon trap
Product delivery (for example Scrum) How a team builds and improves a product in short cycles Team-level, ongoing, no built-in business case or project closure Assuming it covers funding, governance and benefits on its own
Agile project framework (AgilePM) How a temporary change initiative is justified, governed, delivered and closed Adds lifecycle phases, project roles and governance around delivery Thinking it replaces Scrum rather than wrapping it

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

  1. Agile means no documentation

    What candidates pick
    An option stating that agile projects avoid documentation in favour of working software.
    Why it looks right
    It echoes the Manifesto wording and sounds suitably agile.
    Why it's wrong
    The Manifesto says there is value in comprehensive documentation; it only ranks working software higher when the two compete.

    Clue to watch for Absolute words such as 'no', 'never' or 'eliminate' attached to a right-hand item.

  2. Agile means no plan

    What candidates pick
    The statement that agile teams respond to change instead of planning.
    Why it looks right
    Responding to change is a core value, so rejecting plans feels consistent.
    Why it's wrong
    Planning still happens and plans are revised; AgilePM in particular plans at several levels across the lifecycle.

    Clue to watch for A distractor that removes planning rather than ranking it below adaptation.

  3. Swapped value pairs

    What candidates pick
    'Customer collaboration over comprehensive documentation' or a similar recombined pair.
    Why it looks right
    Every word in it comes from the Manifesto, so it looks familiar.
    Why it's wrong
    Each value is a specific pair; recombined pairs are not Manifesto values.

    Clue to watch for Familiar words in an unfamiliar pairing.

  4. Agility equals speed

    What candidates pick
    The option defining business agility as delivering projects faster.
    Why it looks right
    Agile delivery is often marketed as faster.
    Why it's wrong
    Business agility is the ability to sense and respond to change and keep delivering value; speed without responsiveness misses the point.

    Clue to watch for A definition question where one option mentions sensing or responding to change.

  5. Scrum alone runs the project

    What candidates pick
    The view that a Scrum team needs no project framework because Scrum covers everything.
    Why it looks right
    Scrum is complete for product development and widely used.
    Why it's wrong
    Scrum does not provide a business case, feasibility, governance or post-deployment benefits assessment; AgilePM adds that project layer.

    Clue to watch for The scenario mentions funding, a sponsor, deployment into the business or benefits.

Answer framework

Use these steps whenever a Foundation question tests an agile concept, value or principle.

  1. Identify whether the question is about the environment (VUCA and business agility), the Manifesto values and principles, or the project-versus-product distinction, because each has a different source of truth.
  2. For Manifesto items, recall the exact value pair or principle wording, and remember that the right-hand item keeps its value even when it ranks second.
  3. Eliminate any option that uses absolute language such as 'never' or 'no' to remove plans, documents, processes or contracts.
  4. For scope questions, ask whether the option is a project concern (business case, governance, deployment, benefits) or a team delivery practice.
  5. Choose the option that balances adaptability with control, since AgilePM consistently pairs agility with governance rather than abandoning it.

Practice question

A new project manager asks how the Agile Manifesto expects the team to treat processes and tools, comprehensive documentation, contract negotiation and following a plan?

Want more like this? The AgilePM Foundation practice test has questions for every domain.

Checklist

0 of 10

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start here before any other area, because the later syllabus assumes this vocabulary. Write out the four Manifesto values from memory until the pairs are automatic, then read the twelve principles and put each one in your own words with a project example, such as a late regulatory change being welcomed rather than rejected.

The high-priority idea is balance. Practise rewriting distractors: take a statement such as 'agile teams do not document' and correct it to the Manifesto's actual position. That habit removes most wrong answers in this area and in later areas where the same overstatements reappear.

The commonly underestimated topic is the project-versus-product distinction. Spend time listing what a project needs that a product team method does not supply, because this explains why AgilePM has pre-project and feasibility work, project-level roles and governance products, and why Scrum sits inside it rather than competing with it.

Afterwards, move to Scrum overview and AgilePM fundamentals, then take a short practice set mixing Manifesto items with principle questions so you learn to tell the Agile Manifesto principles apart from AgilePM's own principles.

FAQ

How many questions come from key agile concepts?

APMG does not publish per-area weights or counts. With ten syllabus areas and 50 questions, an even split suggests about five, but treat that as a planning estimate only.

Do I need to memorise all twelve Manifesto principles word for word?

You need to recognise each principle when it is paraphrased and to tell it apart from a distorted version. Knowing the four values exactly is more important, because options often differ by one word.

Does the Agile Manifesto say agile teams should not write documentation?

No. It values working software over comprehensive documentation while stating there is value in the documentation. Agile projects document what is useful, and AgilePM has defined products for governance.

What does VUCA mean and why does AgilePM care?

Volatility, uncertainty, complexity and ambiguity. In those conditions a fixed detailed plan goes out of date quickly, so AgilePM favours incremental delivery, early feedback and planning that is refined as the project learns.

Is AgilePM a replacement for Scrum?

No. AgilePM v3 uses Scrum as its product delivery engine and adds the project layer around it: business justification, lifecycle phases, project roles and governance.

Are the Agile Manifesto principles the same as the AgilePM principles?

No. The Manifesto principles are general agile principles; AgilePM has its own set of project principles covered in the AgilePM fundamentals area. Questions may test whether you can tell which set a statement belongs to.

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

Test your Domain 1 knowledge

You have covered VUCA, business agility, the Agile Manifesto and why a project needs more than a product method. Check that you can spot the one-word distortions the exam uses in these questions.

Take the AgilePM Foundation practice test Check your AgilePM Foundation readiness

Keep going