Overview
Agile Introduction is the first of the nine learning-objective areas CertiProf lists for the SMPC, and it explains why Scrum exists before the exam asks how Scrum works. The core material is the Manifesto for Agile Software Development from 2001: four value statements that prefer individuals and interactions, working software, customer collaboration and responding to change, plus the twelve supporting principles. CertiProf partner courses add the idea of agility as an organizational capability, business agility, the Cynefin sense-making framework and a contrast with traditional predictive project management.
The Scrum Master Professional Certificate is an active CertiProf credential based on the 2020 Scrum Guide. It is a closed-book, 40-question multiple-choice exam lasting 60 minutes, and a candidate needs 32 correct answers (80%) to pass. Expect Agile Introduction questions to test whether you can apply the values and principles to a short situation rather than recite them.
How it's tested
Questions in this area usually describe a team behaviour and ask which agile value or principle it supports or violates. Others ask you to place a problem in a Cynefin domain or to say when an agile approach is a better fit than a predictive one. Direct recall of the Manifesto wording also appears.
-
Value on the left
A choice between two activities is described, and you pick the one the Manifesto values more, while remembering the items on the right still have value.
-
Which principle applies
A short story about delivery cadence, technical quality, motivated people or reflection asks you to name the matching principle.
-
Fit the approach to the problem
You decide whether a problem is clear, complicated, complex or chaotic and whether an empirical, adaptive approach suits it.
A sponsor asks the team to finish a 200-page requirements document before writing any code, because changes later would be costly. The tempting answer is to agree, since documentation is useful. The Manifesto values working software over comprehensive documentation and welcomes changing requirements, even late. The better response is to deliver a small working increment early and refine requirements through collaboration, keeping only the documentation that adds value.
Topics 4
Official topics from the CertiProf outline, in outline order.
1.1 The Agile Manifesto valuesThe four value statements published in 2001.
- What it means
- The Manifesto for Agile Software Development was written in 2001 by seventeen practitioners. It states four preferences: 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.
- What to understand
- Each statement compares two things that both have value; the Manifesto says the items on the left are valued more, not that the items on the right are discarded. Processes, documents, contracts and plans still exist in agile work. The values explain why Scrum favours face-to-face collaboration, frequent working Increments and inspection that leads to adaptation.
- How it shows up
- Expect a scenario where you choose the response that matches a value, or a recall question about which item sits on the left side.
- Common confusion
- Reading the values as a rejection of documentation, contracts or planning altogether.
1.2 The twelve agile principlesPrinciples that put the four values into practice.
- What it means
- Twelve principles support the values. They cover early and continuous delivery of valuable software, welcoming changing requirements, frequent delivery in short timescales, daily collaboration between business people and developers, motivated individuals, face-to-face conversation, working software as the primary measure of progress, sustainable pace, technical excellence, simplicity, self-organizing teams and regular reflection.
- What to understand
- Learn the principles in themes rather than as a numbered list. Delivery themes: early, frequent, working software. Collaboration themes: business and developers together, conversation, trust in motivated people. Quality themes: technical excellence, good design, simplicity as maximizing the amount of work not done. Team themes: sustainable pace, self-organizing teams and regular reflection, which maps directly to the Sprint Retrospective.
- How it shows up
- A behaviour such as overtime every Sprint or measuring progress by hours spent is described, and you identify the principle it breaks.
- Common confusion
- Confusing simplicity, the art of maximizing work not done, with cutting quality or skipping testing.
1.3 Agility, business agility and complexityWhat agility means and how the Cynefin framework classifies problems.
- What it means
- Agility is the ability to sense change and respond to it quickly while still delivering value. Business agility extends that capability beyond software teams to the whole organization. The Cynefin framework, created by Dave Snowden, helps leaders judge what kind of situation they face before choosing how to act.
- What to understand
- Cynefin describes clear situations with obvious cause and effect, complicated ones that experts can analyse, complex ones where cause and effect are only visible in hindsight, chaotic ones that need immediate action, and confusion when the domain is unknown. Scrum is designed for complex work, where probing with short experiments, sensing results and responding is more reliable than detailed upfront analysis.
- How it shows up
- You may be asked which Cynefin domain fits product development with uncertain requirements, or why empirical methods suit it.
- Common confusion
- Placing new product development in the complicated domain, which implies expert analysis alone can solve it.
1.4 Traditional and agile project managementHow predictive, plan-driven delivery differs from adaptive delivery.
- What it means
- Traditional or predictive project management fixes scope early, plans the whole project upfront and controls change through formal requests. Agile delivery fixes time and team capacity in short iterations and lets scope evolve as the team learns from feedback.
- What to understand
- Predictive approaches work well when requirements are stable and the work is repeatable. Agile approaches reduce risk on uncertain work by delivering usable Increments often, so value and feedback arrive early rather than at the end. In agile, a plan is a forecast that is revised. Neither approach removes the need for discipline; agile replaces upfront certainty with frequent inspection and adaptation.
- How it shows up
- Questions contrast the iron triangle, with fixed scope in predictive work and fixed time and cost in agile work, or ask when each approach is the better fit.
- Common confusion
- Believing agile means no planning; agile teams plan continually, at a shorter horizon.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Agile Manifesto
A 2001 statement of four values for developing software.
- Remember
- Items on the right still have value; the left side is valued more.
- Tested as
- Direct recall and scenario items rely on the exact pairs.
- Trap
- Swapping a pair, such as placing processes over individuals.
-
Working software as progress
The seventh principle measures progress by working product, not activity.
- Remember
- Percent complete and hours spent are weak measures.
- Tested as
- Appears in questions about status reporting.
- Trap
- Choosing a detailed task-completion report as the best progress measure.
-
Welcome changing requirements
Agile processes harness change for the customer's competitive advantage.
- Remember
- Change is welcomed even late in development.
- Tested as
- Tests whether you resist or embrace change.
- Trap
- Picking a change-freeze answer because it seems controlled.
-
Sustainable pace
Sponsors, developers and users should be able to keep a constant pace indefinitely.
- Remember
- Repeated overtime signals a problem to inspect.
- Tested as
- Linked to team health scenarios.
- Trap
- Treating heroic overtime as commitment.
-
Simplicity
The art of maximizing the amount of work not done.
- Remember
- It means avoiding unnecessary work, not lowering quality.
- Tested as
- Shows up with gold-plating and extra features.
- Trap
- Equating simplicity with skipping tests or design.
-
Self-organizing teams
The best architectures, requirements and designs emerge from them.
- Remember
- The 2020 Scrum Guide uses the stronger term self-managing.
- Tested as
- Bridges this area to the Scrum Team area.
- Trap
- Assuming a manager should assign every task.
-
Business agility
An organization's ability to adapt quickly to market change and deliver value.
- Remember
- It extends agility beyond IT teams.
- Tested as
- Appears in introductory definition questions.
- Trap
- Limiting agility to software development only.
-
Cynefin complex domain
Cause and effect are understood only in retrospect.
- Remember
- Probe, sense, respond suits it, which is why empiricism fits.
- Tested as
- Used to justify Scrum for product work.
- Trap
- Choosing the complicated domain because experts are involved.
-
Predictive approach
Plan-driven delivery with scope defined upfront.
- Remember
- Fits stable, well-understood work.
- Tested as
- Contrast questions with adaptive delivery.
- Trap
- Calling it wrong in every context.
-
Face-to-face conversation
The most efficient way to convey information within a development team.
- Remember
- Modern guidance accepts rich remote conversation as the spirit of it.
- Tested as
- Communication scenario questions.
- Trap
- Choosing email chains or long documents to share understanding.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Predictive vs. agile delivery
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Predictive | Plan the whole project, then execute and control change | Scope fixed early; time and cost flex | Assuming it suits uncertain product discovery |
| Agile | Deliver in short iterations and adapt from feedback | Time and capacity fixed per iteration; scope flexes | Assuming no plan exists |
| Hybrid | Mixes predictive governance with agile delivery | Common in practice but not part of Scrum | Treating it as a Scrum Guide concept |
Cynefin domains
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Clear | Cause and effect obvious to anyone | Sense, categorize, respond with best practice | Using experiments where a checklist works |
| Complicated | Cause and effect discoverable by experts | Sense, analyse, respond with good practice | Placing new product work here |
| Complex | Cause and effect clear only in hindsight | Probe, sense, respond with emergent practice | Expecting a full upfront plan to hold |
| Chaotic | No visible cause and effect; crisis | Act first, then sense and respond | Running a long analysis during an outage |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Documentation is bad
- What candidates pick
- An answer that drops all documentation.
- Why it looks right
- The Manifesto mentions working software over documentation.
- Why it's wrong
- The Manifesto keeps documentation; it only values working software more, so useful documents are still produced.
Clue to watch for Look for 'over' rather than 'instead of'.
-
Change freeze
- What candidates pick
- Locking scope to protect the delivery date.
- Why it looks right
- It sounds disciplined and lowers short-term risk.
- Why it's wrong
- Agile principles welcome changing requirements, even late, to give the customer an advantage.
Clue to watch for A customer learns something new partway through.
-
Overtime as commitment
- What candidates pick
- Praising a team that works weekends every Sprint.
- Why it looks right
- Effort looks like dedication.
- Why it's wrong
- Sustainable pace is a principle; constant overtime hides planning or capacity problems.
Clue to watch for Words like every Sprint or ongoing extra hours.
-
Progress by activity
- What candidates pick
- Tracking hours burned or tasks closed as the main progress measure.
- Why it looks right
- Activity metrics are easy to report.
- Why it's wrong
- Working software is the primary measure of progress in the principles.
Clue to watch for A sponsor asks how far along the product is.
-
Experts can plan it
- What candidates pick
- Choosing a detailed upfront analysis for a novel product.
- Why it looks right
- Analysis feels thorough.
- Why it's wrong
- Novel product work is complex; outcomes emerge through experimentation and feedback.
Clue to watch for Phrases like unknown customer needs or new market.
Answer framework
Use these steps when a question asks which agile value, principle or approach fits a situation.
- Name the tension in the scenario, such as plan versus change, documents versus product, or contract versus collaboration, before reading the answer options closely.
- Match it to the Manifesto pair that covers it and prefer the left-hand item, without discarding the right-hand item, which still has value.
- If no value pair fits, look for the principle theme involved: early delivery, collaboration, technical quality, sustainable pace or regular reflection and tuning.
- Judge the problem type with Cynefin; complex work with unknown customer needs points toward short experiments, working Increments and frequent feedback.
- Reject answers that remove planning, quality or documentation entirely, because agile adjusts these rather than abandoning them.
Practice question
Want more like this? The SMPC practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Start with the primary source. Read the Agile Manifesto and its twelve principles on agilemanifesto.org twice, then close the page and write the four value pairs from memory. Repeat until the left and right sides never swap. Next, sort the principles into four or five themes on a single card so you can recall them by idea rather than by number.
Then practise application. For each principle, write one short workplace example that follows it and one that breaks it; this mirrors how SMPC questions are phrased. Add a short note on Cynefin with one example per domain, making sure new product development sits in the complex domain.
Finish by comparing predictive and agile delivery in a small table covering scope, planning horizon, change handling and progress measurement. Because this area feeds every other SMPC area, return to the card when you study Scrum Theory and Act as Scrum Master and connect each Scrum rule back to a value or principle.
FAQ
How much of the SMPC exam does Agile Introduction cover?
CertiProf does not publish weights for its nine SMPC learning-objective areas, so the share of Agile Introduction is unknown. Expect a few questions on the Manifesto, its principles and agility concepts, roughly four on a 40-question exam as a planning guess.
Do I need to memorize all twelve principles word for word?
Exact wording is less important than recognising each principle in a scenario. Know the key phrases, such as working software as the primary measure of progress and maximizing the amount of work not done.
Is the Agile Manifesto part of the Scrum Guide?
No. The Manifesto is a separate 2001 document, but CertiProf includes it in the SMPC syllabus because Scrum shares its values and many of its authors.
What is the Cynefin framework doing in a Scrum exam?
It explains why Scrum suits complex problems. Partner courses for the SMPC use it to show that complex work needs probing and feedback rather than a fixed upfront plan.
Does agile mean no documentation?
No. Agile teams produce documentation that adds value. The Manifesto only places working software above comprehensive documentation.
Is the SMPC exam open book?
CertiProf and its partners describe the exam as closed book: 40 multiple-choice questions in 60 minutes, with 32 correct answers needed to pass.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 1 knowledge
Try a short set of SMPC questions on Manifesto values, principles and agility concepts before moving to the Scrum framework itself.