Courseiva

CCNA Foundations OF Agile Questions

57 questions · Foundations OF Agile · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQeasy

Which of the following best describes the 'Disciplined Agile Mindset' regarding process?

A.Be pragmatic and choose your way of working (WoW)
B.Copy the processes of the most successful competitors
C.Follow the Scrum guide verbatim
D.Focus exclusively on speed of delivery
AnswerA

The Disciplined Agile Mindset holds that teams should be pragmatic, choosing and evolving their way of working to fit context rather than adopting one prescribed process. This satisfies the stem by describing the mindset's stance that process should be tailored, not mandated.

Why this answer

The Disciplined Agile Mindset is built on principles such as 'Be Pragmatic', 'Choose Your WoW', and 'Deliver Consumable Solutions'. Regarding process, the mindset explicitly states that teams should be pragmatic and choose their way of working (WoW) — tailoring practices to their context rather than adopting a one-size-fits-all method. This is the core of DA's philosophy.

Exam trap

DAF often tests the misconception that DA is just another prescriptive framework like Scrum — candidates pick 'follow the Scrum guide verbatim' or 'copy competitors', missing that DA's defining feature is pragmatic, context-driven tailoring of the WoW.

How to eliminate wrong answers

Option B is wrong because copying competitors' processes ignores context — what works for one organisation may fail in another due to different culture, scale, or constraints, and DA explicitly rejects cookie-cutter adoption. Option C is wrong because following the Scrum guide verbatim is prescriptive and contradicts DA's 'Choose Your WoW' principle — DA draws from Scrum, Kanban, SAFe, and others but expects teams to tailor. Option D is wrong because focusing exclusively on speed of delivery ignores DA's balanced focus on value, quality, and sustainability — speed at the expense of quality or team health is an anti-pattern.

Practice this question →
2
MCQeasy

A newly formed product team is deciding how to organize its work. The team lead suggests adopting a 'flow-based' strategy where work items are pulled continuously rather than committed to fixed-length iterations. Which Disciplined Agile principle best supports this choice?

A.Deliver value continuously by optimizing flow and eliminating waste.
B.Maximize utilization of all team members at all times.
C.Prefer predictive planning to reduce uncertainty.
D.Follow a single prescribed process for all teams.
AnswerA

This principle directly endorses continuous delivery and flow optimization, which aligns with pulling work as capacity allows. It is a core DA principle that guides teams to choose lifecycle approaches based on context, not dogma. The scenario's flow-based strategy is a valid DA way of working, so this principle is the best fit.

Why this answer

The team is choosing a flow-based strategy, which is one of several valid DA lifecycles. The principle of delivering value continuously and optimizing flow supports this choice, as it emphasizes pull systems, waste elimination, and adaptability. The other options reflect anti-patterns or misapplications of DA, such as over-planning, over-utilization, or rigid process adherence.

Exam trap

The trap here is assuming that DA mandates a specific lifecycle, when in fact it encourages teams to choose the approach that best fits their context.

Practice this question →
3
MCQeasy

What is the main benefit of having a 'cross-functional' team?

A.They work faster than specialized teams
B.They reduce dependencies on other teams
C.They can work on more projects at once
D.They don't need a team leader
AnswerB

Cross-functional teams hold all skills needed to deliver end-to-end, so they satisfy the stem by reducing dependencies on external teams. This cuts handoffs and waiting, letting the team complete work without queuing for specialist resources elsewhere.

Why this answer

A cross-functional team contains all the skills needed to deliver a working increment — analysis, development, testing, design, and often ops — so it does not have to wait on external specialists to complete its work. This directly reduces dependencies on other teams, which is the primary structural benefit in Disciplined Agile and other agile frameworks. Fewer handoffs means shorter feedback loops and less coordination overhead.

Exam trap

DAF often tests whether candidates confuse cross-functionality (skill coverage reducing dependencies) with speed or multi-tasking benefits — the exam wants the dependency-reduction rationale, not a productivity claim.

How to eliminate wrong answers

Option A is wrong because cross-functional teams are not inherently faster than specialized teams — specialization can be faster for narrow tasks; the benefit is autonomy and reduced handoffs, not raw speed. Option C is wrong because a cross-functional team is typically focused on one product or value stream, not juggling more projects; in fact, spreading a team across projects undermines the model. Option D is wrong because cross-functional teams still need leadership, coaching, and self-organization guidance — being cross-functional does not eliminate the need for a team leader or Scrum Master.

Practice this question →
4
MCQhard

During a release planning session, the stakeholders insist on a fixed-scope, fixed-date delivery. As a DA practitioner, how should you respond to this 'iron triangle' request?

A.Report the project as failing because it cannot be purely agile.
B.Accept the constraints and reduce the testing phase duration to meet the date.
C.Educate stakeholders on the tradeoffs by using a 'Range-Based' planning approach to show how scope can be flexed to hit the date.
D.Explain that agile methods do not allow for deadlines.
AnswerC

Range-based planning quantifies uncertainty by estimating scope in ranges rather than fixed points, exposing the schedule-scope tradeoff the stakeholders' fixed-date constraint creates. Educating them this way lets the team flex scope to protect the release date, satisfying the stem's fixed-date requirement while keeping delivery realistic.

Why this answer

As a DA practitioner, when stakeholders insist on fixed-scope, fixed-date delivery, the correct response is to educate them on the tradeoffs using a 'Range-Based' planning approach. This approach shows how scope can be flexed (e.g., using a minimum viable product or prioritised backlog) to meet the date, while maintaining quality and avoiding the pitfalls of the iron triangle.

Exam trap

DAF often tests the misconception that Agile cannot handle fixed dates or that the only response is to compromise quality — the trap is selecting an answer that either rejects the constraint outright or sacrifices testing/quality, rather than using range-based planning to flex scope.

How to eliminate wrong answers

Option A is wrong because reporting the project as failing is defeatist and incorrect — DA is pragmatic and can operate within constraints by adjusting other variables (scope, quality, or cost) rather than declaring failure. Option B is wrong because reducing testing duration to meet the date compromises quality and is a classic iron triangle mistake — DA would not sacrifice quality without explicit tradeoff discussions. Option D is wrong because Agile methods do allow for deadlines; they simply advocate for flexibility in scope or quality to meet them, and DA specifically provides guidance on how to handle fixed-date scenarios.

Practice this question →
5
MCQmedium

When a team is working on multiple projects, what is the impact on their productivity?

A.It allows for better utilization of team members
B.It is the standard way of working in DAD
C.It increases the risk of delay and quality issues due to context switching
D.It increases their total output
AnswerC

Context switching between projects imposes cognitive reload costs and fragments focus, directly reducing throughput. Because attention must repeatedly reorient to different goals, specifications and stakeholders, the likelihood of errors rises and schedules slip. This satisfies the stem's productivity constraint by identifying the mechanism through which multitasking degrades both delivery speed and output quality.

Why this answer

When a team works on multiple projects simultaneously, context switching between different domains, stakeholders, and technical stacks degrades productivity. DA explicitly warns against this and recommends limiting work in progress so teams can focus on one primary initiative at a time. The result of over-allocation is longer cycle times, more defects, and higher risk of delay.

Exam trap

DAF often tests the myth that multi-project allocation improves utilization, so candidates who think in terms of resource-utilization metrics pick the wrong answer instead of recognizing the context-switching penalty.

How to eliminate wrong answers

Option A is wrong because the appearance of better utilization ignores the cognitive and coordination overhead of context switching, which reduces effective throughput. Option B is wrong because multi-project allocation is not the standard DA way of working; DA favors dedicated, stable teams aligned to value streams. Option D is wrong because total output typically falls, not rises, when a team is spread across multiple projects, due to switching costs and reduced focus.

Practice this question →
6
Multi-Selectmedium

Which TWO of the following are core pillars of a 'Disciplined Agile' mindset?

Select 2 answers
A.Always use a Scrum-based lifecycle
B.Be pragmatic
C.Context counts
D.Prioritize speed over quality
E.Follow the process guide precisely
AnswersB, C

Being pragmatic means choosing practices that work for the team's actual situation rather than dogmatically following a framework. This pillar underpins Disciplined Agile's guidance to adapt methods to context, making it a genuine core mindset element.

Why this answer

Option B (Be pragmatic) is correct because Disciplined Agile's core mindset explicitly includes 'Be pragmatic' as one of its guiding principles, encouraging teams to choose the approach that works best in their situation rather than dogmatically following one method. Option C (Context counts) is also correct because Disciplined Agile emphasizes that every team, organization, and problem is unique, so the choice of lifecycle, practices, and roles must fit the specific context. Option A is wrong because Disciplined Agile supports multiple lifecycles (Agile, Lean, Continuous Delivery, etc.), not only Scrum.

Option D is wrong because Disciplined Agile values quality and sustainable delivery, not sacrificing quality for speed. Option E is wrong because DA is deliberately flexible and tailorable, not a rigid process guide to be followed precisely.

Exam trap

DAF often tests whether candidates recognize that DA is explicitly anti-dogmatic — options that prescribe a single framework (Scrum) or rigid adherence to a guide are traps, because DA's pillars emphasize pragmatism and context sensitivity.

Practice this question →
7
MCQmedium

A project is currently in the 'Construction' phase of the Disciplined Agile lifecycle. What is the main focus?

A.Building, testing, and verifying the solution
B.Establishing the initial team vision
C.Identifying stakeholders and their needs
D.Closing out the project and archiving documentation
AnswerA

Construction centres on incrementally building and testing a consumable solution, so this option matches the phase's purpose of producing verified, potentially shippable increments. It satisfies the stem's requirement by naming the actual work of the Construction phase rather than the Inception or Transition phases' concerns.

Why this answer

The Construction phase is where the team builds the solution in a series of iterations.

Practice this question →
8
Multi-Selecthard

A team is adopting Disciplined Agile and wants to ensure they are applying the DA mindset. Which TWO of the following are key aspects of the DA mindset? (Choose two.)

Select 2 answers
A.Avoiding any form of planning to stay flexible.
B.Focusing on value delivery and continuous improvement.
C.Following a fixed set of ceremonies regardless of team size.
D.Being pragmatic and context-driven.
E.Maximizing documentation for all decisions.
AnswersB, D

DA is centered on delivering value to stakeholders and continuously improving processes and products. This aspect drives teams to measure outcomes and adapt. It is a core element of the DA mindset, ensuring that agility serves business goals rather than being an end in itself.

Why this answer

The Disciplined Agile mindset is built on principles such as being pragmatic, context-driven, and focused on value delivery and continuous improvement. These aspects guide teams to tailor their way of working and to constantly seek better outcomes. The other options represent misconceptions: rigid ceremonies, excessive documentation, or no planning, none of which align with the DA mindset.

Exam trap

The trap here is equating agility with the absence of planning or with strict adherence to ceremonies, whereas DA promotes purposeful adaptation.

Practice this question →
9
MCQmedium

A delivery team at a financial services organization has been using a predictive approach for years. Leadership now wants to adopt Disciplined Agile to improve responsiveness. During the first retrospective, the team identifies that their biggest challenge is that they cannot get feedback from stakeholders until the very end of the project. Which Disciplined Agile principle should the team apply first to address this challenge?

A.Deliver value incrementally to obtain feedback early and often.
B.Optimize the whole by eliminating local efficiencies.
C.Make all decisions at the last responsible moment.
D.Choose the right level of detail for the context.
AnswerA

This principle directly addresses the challenge by breaking work into smaller increments that can be demonstrated to stakeholders, enabling early and frequent feedback. By delivering value incrementally, the team can validate assumptions and adjust direction before the project ends, reducing the risk of building the wrong thing. It is a core Disciplined Agile principle that promotes empirical process control and stakeholder collaboration.

Why this answer

Delivering value incrementally is the foundational Disciplined Agile principle that enables early and frequent feedback. By shortening the cycle time between building and showing working software, the team can engage stakeholders throughout the project rather than only at the end. This directly solves the identified problem and sets the stage for other principles such as optimizing the whole.

Exam trap

The trap here is assuming that any Disciplined Agile principle will fix the feedback gap, when only incremental delivery directly creates the opportunity for early stakeholder input.

Practice this question →
10
Multi-Selecthard

Which THREE of the following activities are considered essential for 'Continuous Improvement' in a DA team?

Select 3 answers
A.Implementing automated testing.
B.Conducting regular retrospectives.
C.Waiting for the annual performance review.
D.Monitoring and acting on team metrics.
E.Increasing the number of meetings.
AnswersA, B, D

Automated testing provides fast, repeatable feedback on every change, which is the empirical data continuous improvement depends on. Without it, teams cannot detect regressions quickly enough to inspect and adapt their Way of Working meaningfully.

Why this answer

Option A (Implementing automated testing) is correct because automated tests provide fast, repeatable feedback on code quality and regression risk, which is the empirical data Continuous Improvement depends on to shorten feedback loops and raise deployment confidence. Option B (Conducting regular retrospectives) is correct because retrospectives are the structured inspect-and-adapt ceremony in which the team identifies what worked, what did not, and commits to concrete improvement actions each iteration. Option D (Monitoring and acting on team metrics) is correct because Continuous Improvement requires measuring delivery and quality signals (e.g., lead time, deployment frequency, change failure rate, MTTR) and then acting on those metrics rather than guessing.

Option C (Waiting for the annual performance review) is not correct because yearly feedback is far too infrequent to drive iterative improvement and is not a team-level continuous mechanism. Option E (Increasing the number of meetings) is not correct because more meetings add overhead without guaranteeing measurable improvement; improvement comes from feedback and action, not meeting volume.

Exam trap

DAF often tests the confusion between continuous improvement and periodic events like annual reviews — candidates may pick 'annual performance review' because it sounds like evaluation, but continuous improvement requires frequent, team-based reflection and action.

Practice this question →
11
MCQhard

A team is using a 'Lean' approach. What is their primary goal?

A.To eliminate waste and optimize the flow of value
B.To force team members to work faster
C.To replace all agile practices with kanban
D.To increase the number of team meetings
AnswerA

Lean's primary goal is eliminating waste while optimising value flow, directly satisfying the stem's question. Every Lean practise, from value stream mapping to pull systems, serves this aim of removing non-value-adding activity and smoothing delivery.

Why this answer

Lean's primary goal is to maximize customer value by eliminating waste and optimizing the flow of value through the system. In software development, this means removing activities that do not add value, reducing cycle time, and delivering value smoothly. Lean is not about working faster or replacing Agile practices; it is a mindset and set of principles that complement Agile.

Exam trap

DAF often tests the misconception that Lean means working harder or faster, or that it is synonymous with Kanban — candidates may pick 'replace all agile practices with kanban' or 'work faster' instead of the waste-elimination goal.

How to eliminate wrong answers

Option B is wrong because Lean is not about forcing people to work faster — it is about removing waste so that work flows efficiently; pushing people to work faster leads to burnout and defects, which are wastes. Option C is wrong because Lean does not require replacing all Agile practices with Kanban; Kanban is a Lean-inspired method, but Lean is broader and can coexist with Scrum, XP, and other Agile practices. Option D is wrong because increasing meetings adds overhead and is often a form of waste (waiting, over-processing), directly contradicting Lean's goal of eliminating waste.

Practice this question →
12
MCQmedium

What is meant by 'Self-Organization' in a team context?

A.The team does not have a leader or a coach
B.Team members work on whatever they want, whenever they want
C.The team refuses to communicate with management
D.The team determines how to best accomplish the work assigned to them
AnswerD

Self-organisation means the team, not a manager, decides how to divide and sequence the work it has been assigned. Authority over the 'how' sits with those doing the work, while the 'what' and 'why' come from outside. This satisfies the stem's requirement that the team determines its own approach.

Why this answer

Self-organization in an Agile team means the team has the authority and responsibility to determine how to best accomplish the work assigned to them — they decide on task breakdown, assignment, and approach. It does not mean the absence of leadership or structure; rather, it means the team self-manages its internal processes while remaining accountable to the organization. The team still operates within organizational boundaries and may have a coach or Scrum Master facilitating the process.

Exam trap

The trap here is equating self-organization with anarchy — candidates often pick the option suggesting no leader or no structure, when self-organization actually means autonomy within organizational constraints.

How to eliminate wrong answers

Option A is wrong because self-organizing teams can and often do have leaders and coaches — a Scrum Master or Agile coach facilitates the team's self-organization rather than directing it, so the absence of a leader is a misconception. Option B is wrong because self-organization does not mean team members work on whatever they want whenever they want; the team still commits to sprint goals and delivers against agreed priorities, just with autonomy over how they execute. Option C is wrong because self-organizing teams are expected to communicate transparently with management and stakeholders — refusing communication would undermine the transparency that Agile depends on.

Practice this question →
13
MCQmedium

A team is working on a project with high technical uncertainty. Which approach should they adopt?

A.Follow the original plan strictly to reduce risk
B.Adopt an iterative approach with frequent spikes to learn
C.Outsource the uncertain parts of the project
D.Delay the uncertain work until the end of the project
AnswerB

Iterative delivery with spikes lets the team probe unknowns early, converting technical uncertainty into evidence before committing to full build. Spikes are timeboxed investigations, so learning happens without derailing delivery cadence — directly addressing the high uncertainty constraint in the stem.

Why this answer

When a project faces high technical uncertainty, the most effective approach is to reduce that uncertainty through rapid, iterative learning. Option B advocates an iterative approach with frequent spikes—time-boxed investigations or prototypes—which directly addresses unknowns by testing assumptions early and often. This aligns with agile and lean principles, where uncertainty is managed by short feedback loops rather than rigid planning.

By learning quickly, the team can adapt the plan based on empirical evidence, thereby reducing risk and increasing the likelihood of delivering value.

Exam trap

DAF often tests the misconception that uncertainty can be eliminated by strict planning or outsourcing, when in fact it requires iterative learning and adaptation.

How to eliminate wrong answers

Option A is wrong because following the original plan strictly assumes the plan is correct despite high uncertainty; it ignores the need to adapt when new information emerges, which can lead to wasted effort and failure. Option C is wrong because outsourcing uncertain parts does not eliminate the uncertainty; it merely transfers the work to another party who may lack the necessary context or may also struggle with the same unknowns, and it can introduce coordination overhead. Option D is wrong because delaying uncertain work until the end increases risk; the team may discover too late that the approach is unworkable, leaving no time to pivot, and it defers learning when it is most needed.

Practice this question →
14
Multi-Selectmedium

Which TWO of the following are core components of the Disciplined Agile 'Mindset'?

Select 2 answers
A.Strictly adhere to Scrum ceremonies.
B.Follow the PMI PMBOK guide exclusively.
C.Optimize Flow.
D.Be Awesome.
E.Always choose the newest technology.
AnswersC, D

Optimize Flow is a core component of the Disciplined Agile Mindset, focusing on removing bottlenecks and smoothing value delivery across the system. It satisfies the stem by naming a principle that guides decisions toward continuous, unimpeded throughput.

Why this answer

The Disciplined Agile (DA) Mindset is built around a set of guiding principles and promises, and among its core principles are 'Optimize Flow' (option C) and 'Be Awesome' (option D). 'Optimize Flow' reflects DA's lean-influenced focus on improving the smooth, continuous delivery of value through the value stream rather than optimizing individual silos or resources. 'Be Awesome' captures DA's emphasis on delivering delightful, high-quality solutions and continuously improving both the product and the team's way of working. Options A and B are incorrect because DA explicitly avoids prescribing a single framework or body of knowledge — it is a pragmatic, choice-driven hybrid that tailors practices from Scrum, Kanban, SAFe, PMBOK, and others rather than strictly adhering to Scrum ceremonies or following the PMBOK guide exclusively. Option E is incorrect because DA does not mandate always choosing the newest technology; instead it advises choosing the simplest technology that fits the context and delivers value.

Exam trap

DAF often tests whether candidates can identify DA's actual mindset principles (Optimize Flow, Be Awesome, Context Counts, Choice is Good) versus framework-specific rules or generic agile slogans that are not part of the DA mindset.

Practice this question →
15
MCQmedium

A team has a very large backlog of items. How should they manage it?

A.Regularly prioritize and refine the backlog
B.Have the project manager manage the backlog in secret
C.Delete half of the backlog to reduce the workload
D.Keep everything in the backlog and work on it sequentially
AnswerA

Regular prioritisation and refinement keeps a large backlog ordered by value and keeps top items estimated and ready for delivery. This satisfies the stem's constraint of an oversized backlog by preventing stale, low-value items from accumulating and obscuring what matters.

Why this answer

A large backlog should be managed through regular prioritization and refinement so that the most valuable items rise to the top and are ready for the team to pull. DA treats the backlog as a living artifact that is continuously groomed rather than a static list. This keeps the team focused on the highest-value work and prevents the backlog from becoming an unusable wish list.

Exam trap

DAF often tests whether candidates recognize that backlog management is a continuous, transparent, prioritization-driven activity, so options that propose secrecy, arbitrary deletion, or sequential processing are planted as plausible but wrong.

How to eliminate wrong answers

Option B is wrong because having the project manager manage the backlog in secret contradicts DA's transparency principle and removes the team's ability to make informed trade-offs. Option C is wrong because deleting half the backlog arbitrarily discards potentially valuable work without prioritization or stakeholder input, which is not a disciplined approach. Option D is wrong because keeping everything and working sequentially ignores prioritization, delays value delivery, and treats the backlog as a queue rather than a prioritized set of options.

Practice this question →
16
MCQhard

Your organization is struggling with 'Shadow IT'—teams buying their own software without oversight. What is the Disciplined Agile view on this?

A.Fully decentralize all IT procurement decisions
B.Force all teams to use legacy software only
C.Ban all software purchases by individual teams
D.Provide organizational guidance on standards while allowing for innovation
AnswerD

Disciplined Agile treats Shadow IT as a governance gap, not a crime: publish lightweight standards and guardrails covering security, data and support, then let teams innovate within them. This satisfies the stem by channelling autonomous purchasing into guided choice rather than blanket prohibition.

Why this answer

Disciplined Agile advocates for a balanced approach to Shadow IT, where the organization provides guidance on standards and governance while still allowing teams the flexibility to innovate. This means establishing clear guidelines for software procurement and usage, but not imposing rigid bans that stifle innovation. The goal is to enable teams to make informed decisions that align with enterprise objectives.

Exam trap

DAF often tests the misconception that DA either fully endorses or completely bans Shadow IT, when the correct answer is a balanced approach with guidance.

How to eliminate wrong answers

Option A is wrong because fully decentralizing procurement can lead to chaos and security risks, which DA does not endorse. Option B is wrong because forcing legacy software hinders innovation and agility. Option C is wrong because banning all purchases is overly restrictive and ignores the potential benefits of team-level innovation.

Practice this question →
17
Multi-Selecthard

Which TWO of the following are examples of 'Active Stakeholder Participation'?

Select 2 answers
A.Stakeholders only reading the final report
B.Stakeholders collaborating on feature prioritization
C.Stakeholders dictating the team's internal coding style
D.Stakeholders providing feedback on iterations
E.Stakeholders attending daily stand-up meetings
AnswersB, D

Collaborative feature prioritisation requires stakeholders to actively shape the product backlog rather than merely receive updates, satisfying the stem's demand for participation that is active. This contrasts with passive consultation or one-way communication, where stakeholders supply input but hold no shared decision-making authority over what gets built.

Why this answer

Option B is correct because active stakeholder participation means stakeholders engage directly in shaping what the team builds, and collaborating on feature prioritization is exactly that kind of ongoing, hands-on involvement in product decisions. Option D is correct because providing feedback on iterations keeps stakeholders continuously engaged throughout development, which is the essence of active participation rather than passive, end-of-project review. Option A is not correct because merely reading a final report is passive, after-the-fact involvement with no influence on the work.

Option C is not correct because dictating the team's internal coding style is inappropriate overreach into technical implementation, not legitimate stakeholder participation. Option E is not correct because daily stand-ups are internal team coordination events, and routine attendance is not the defining example of active stakeholder participation.

Exam trap

DAF often tests the boundary between active and passive stakeholder involvement — candidates pick 'attending daily stand-ups' as active participation, missing that stand-ups are a team-internal ceremony and that active participation means contributing to priorities and feedback, not intruding on team mechanics.

Practice this question →
18
MCQhard

What is the primary role of an 'Agile Coach' in a DA team?

A.To help the team learn and improve their WoW
B.To enforce the rules of the company
C.To act as the project manager
D.To perform the technical coding tasks
AnswerA

An Agile Coach guides the team in refining its way of working, fostering continuous improvement through mentoring and feedback rather than directing delivery. This satisfies the stem's focus on helping the team learn and improve their WoW.

Why this answer

An Agile Coach helps the team improve their way of working, not just manage the work.

Practice this question →
19
Multi-Selecteasy

Which TWO of the following are benefits of an 'Iterative' development approach compared to a waterfall approach?

Select 2 answers
A.Elimination of all documentation.
B.Guaranteed delivery of all original requirements on day one.
C.Reduced focus on software quality.
D.Ability to adapt to changing business needs.
E.Reduced risk through regular stakeholder feedback.
AnswersD, E

Iterative delivery produces working increments each cycle, so feedback arrives while requirements can still be changed cheaply. This satisfies the stem's benefit: unlike waterfall's single late delivery, iterations let the team adapt to changing business needs before significant investment is locked in.

Why this answer

Option D is correct because iterative development delivers software in short, repeated cycles, so newly discovered or changed business requirements can be incorporated in later iterations rather than being frozen at project start as in waterfall. Option E is correct because each iteration typically ends with a review or demo, giving stakeholders regular opportunities to inspect working software and provide feedback, which surfaces defects and misalignments early and thereby reduces overall project risk. The unmarked options do not belong: A is false because iterative approaches still require documentation (though often lighter and evolving), B is false because iterative delivery explicitly accepts that requirements will change and does not guarantee all original requirements on day one, and C is false because iterative methods such as continuous integration and testing generally increase, not reduce, focus on software quality.

Exam trap

DAF often tests the false dichotomy that iterative means 'no documentation' or 'no planning' — candidates must distinguish reduced ceremony from eliminated discipline.

Practice this question →
20
MCQhard

A team has been asked to implement a new feature. They don't know the technology stack well. What is the most 'disciplined' approach?

A.Commit to the feature immediately and learn as they build
B.Reject the feature request until they are experts
C.Ask management to assign an expert to do the work for them
D.Perform a 'Spike' to explore the technology
AnswerD

A spike is a time-boxed investigation that produces knowledge rather than shippable code, directly addressing the team's unfamiliarity with the stack. It satisfies the constraint of unknown technology by reducing uncertainty before commitment, keeping exploration disciplined and bounded instead of allowing unbounded learning during feature delivery.

Why this answer

Conducting a 'Spike' allows the team to research the technology before committing to a delivery plan.

Practice this question →
21
Multi-Selectmedium

Which TWO of the following are common signs of 'Technical Debt'?

Select 2 answers
A.High defect rates in the code base
B.The code is fully documented
C.Increased difficulty in adding new features
D.The team delivers features faster than ever before
E.The team uses a new IDE for coding
AnswersA, C

Accumulated shortcuts and poor code quality raise the volume of bugs, so high defect rates signal that rework is being deferred rather than addressed. This satisfies the stem by evidencing technical debt through measurable quality erosion in the code base.

Why this answer

Technical debt manifests as code quality problems that slow future work, so option A (High defect rates in the code base) is correct because accumulated shortcuts, poor design, and insufficient testing typically produce more bugs and regressions. Option C (Increased difficulty in adding new features) is also correct because technical debt makes the codebase rigid and coupled, so even small changes require disproportionate effort, workarounds, or risk. Option B is not a sign of debt since thorough documentation generally reduces maintenance friction and knowledge loss.

Option D is the opposite indicator: faster delivery often reflects low debt or effective practices, not accumulating debt. Option E is irrelevant because merely adopting a new IDE has no direct relationship to technical debt.

Practice this question →
22
MCQeasy

In Agile, what is a 'User Story'?

A.A detailed 50-page requirement document
B.A technical specification of the database schema
C.A description of a feature from the perspective of the user
D.A formal contract signed by the customer
AnswerC

A user story captures a requirement as a short, plain-language statement of a feature expressed from the end user's perspective, typically naming the role, the need and the benefit. This satisfies the stem's demand for a user-centred description rather than a technical specification.

Why this answer

A user story is a small, concise statement of a requirement from the user's perspective.

Practice this question →
23
MCQhard

A team is struggling with 'technical debt'. According to Disciplined Agile, which action is most appropriate to address this during the iteration?

A.Outsource the technical debt resolution to a different team
B.Include 'refactoring' and 'testing' tasks within each iteration
C.Ignore the debt until the project is near completion
D.Create a separate 'technical debt sprint' once a year
AnswerB

Embedding refactoring and testing tasks within each iteration directly satisfies the stem's constraint of addressing technical debt during the iteration, rather than deferring it. Disciplined Agile treats debt as a continuous concern, so incremental improvement is folded into daily work, preventing accumulation and keeping the codebase maintainable.

Why this answer

Disciplined Agile advocates addressing technical debt continuously rather than deferring it. The most appropriate action is to include refactoring and testing tasks within each iteration, so that debt is paid down incrementally as part of normal delivery. This aligns with DA's principle of delivering consumable solutions and its guidance that quality is built in, not bolted on.

Exam trap

DAF often tests the misconception that technical debt should be handled in a dedicated sprint or deferred — candidates pick the 'technical debt sprint' option because it sounds organised, missing DA's guidance that debt is addressed continuously within each iteration.

How to eliminate wrong answers

Option A is wrong because outsourcing technical debt resolution to a different team breaks the ownership and context that the delivering team has, and DA favours keeping work with the team that owns the code. Option C is wrong because ignoring debt until near completion is the classic anti-pattern that DA explicitly warns against — debt compounds and eventually cripples delivery. Option D is wrong because a separate annual 'technical debt sprint' is a batch approach that contradicts DA's continuous, incremental philosophy and allows debt to accumulate between sprints.

Practice this question →
24
MCQeasy

Which of the following is an example of an 'Agile' practice?

A.Creating a detailed project plan for the next 2 years
B.Holding a Daily Stand-up meeting
C.Requiring all changes to go through a formal committee
D.Assigning tasks to individuals by the manager
AnswerB

The Daily Stand-up is a defined Scrum ceremony where the team synchronises progress, surfaces impediments and re-plans the day's work. This satisfies the stem's requirement for an Agile practice, as it embodies inspect-and-adapt through frequent, short feedback cycles rather than phase-gated reporting.

Why this answer

A Daily Stand-up is a canonical Agile practice: a short, time-boxed ceremony where the team synchronizes, inspects progress, and adapts the plan. It embodies Agile principles like frequent communication, self-organization, and transparency. The other options describe predictive, command-and-control, or bureaucratic practices that are antithetical to Agile values.

Exam trap

The trap is equating any meeting or planning activity with Agile — candidates may pick 'detailed project plan' thinking planning is Agile, but Agile planning is iterative and adaptive, not a fixed 2-year plan.

How to eliminate wrong answers

Option A is wrong because creating a detailed 2-year project plan is a predictive/waterfall practice; Agile favors adaptive planning with rolling-wave or iterative planning over long-term detailed schedules. Option C is wrong because requiring all changes to go through a formal committee is a change-control bureaucracy that slows feedback and contradicts Agile's embrace of changing requirements. Option D is wrong because assigning tasks to individuals by the manager is a command-and-control practice; Agile teams are self-organizing and pull work collectively rather than having work pushed by a manager.

Practice this question →
25
MCQhard

Your organization is scaling Agile. What does Disciplined Agile suggest for scaling?

A.Increase the size of individual teams to 50+ members
B.Choose a lifecycle that fits the specific needs of the teams
C.Adopt a single framework like SAFe for all projects
D.Standardize all teams to use the exact same process
AnswerB

Disciplined Agile rejects a single prescribed scaling framework; instead it guides teams to select and tailor a lifecycle — such as Agile, Lean, or continuous delivery — matching their context, size, and constraints. This directly satisfies the stem's scaling need by fitting the lifecycle to the teams rather than forcing teams into one model.

Why this answer

Disciplined Agile (DA) suggests that scaling Agile is not about adopting a single framework for all teams, but rather about choosing a lifecycle — such as Agile, Lean, Continuous Delivery, Program, or Hybrid — that fits the specific needs and context of the teams involved. This reflects DA's 'Choice is Good' principle and its recognition that different teams require different approaches.

Exam trap

DAF often tests the misconception that scaling Agile requires adopting a single, prescriptive framework like SAFe — the trap is selecting an answer that promotes standardisation or a one-size-fits-all approach, when DA actually advocates for context-driven lifecycle selection.

How to eliminate wrong answers

Option A is wrong because increasing individual team size to 50+ members contradicts Agile principles of small, cross-functional teams (typically 5-9 members) and would create communication overhead and reduce agility. Option C is wrong because DA explicitly rejects the idea of adopting a single framework like SAFe for all projects — DA is framework-agnostic and promotes tailoring the approach to the context. Option D is wrong because standardising all teams to use the exact same process ignores the reality that different teams have different needs, skills, and contexts — DA advocates for context-driven choice, not uniformity.

Practice this question →
26
MCQeasy

A team is deciding which Disciplined Agile lifecycle to adopt. They have a stable, well-understood problem and a fixed deadline. Which lifecycle is most appropriate according to DA guidance?

A.Predictive
B.Continuous Delivery
C.Lean
D.Agile
AnswerA

The Predictive lifecycle is appropriate when the problem is well-understood and the scope is stable, allowing for detailed up-front planning. With a fixed deadline and stable requirements, this lifecycle provides the necessary structure and predictability. DA supports choosing the lifecycle that fits the context.

Why this answer

Disciplined Agile provides a range of lifecycles, and the choice depends on context. For a stable, well-understood problem with a fixed deadline, the Predictive lifecycle is most suitable because it allows for detailed planning and control. The other lifecycles are better suited for evolving requirements or continuous flow, which do not match the scenario's characteristics.

Exam trap

The trap here is assuming that agile approaches are always best, even when a predictive approach is more appropriate for a stable and well-defined project.

Practice this question →
27
MCQeasy

What is the primary benefit of the 'Iterative' approach over a 'Big Bang' delivery approach?

A.It allows for early detection and correction of errors
B.It eliminates the need for project managers
C.It requires less documentation than waterfall
D.It ensures that all team members are always busy
E.It guarantees that no changes will be made to requirements
AnswerA

Iterative delivery produces working increments each cycle, so defects and misaligned requirements surface during testing rather than after full build. This early feedback loop satisfies the stem's need to detect and correct errors before they compound across the whole delivery.

Why this answer

The iterative approach focuses on risk reduction and feedback through smaller, frequent releases.

Practice this question →
28
MCQeasy

What is the primary objective of 'Iterative' development in a project?

A.To avoid all documentation
B.To deliver working, tested functionality frequently
C.To ensure the project manager has total control
D.To allow the team to work on different projects simultaneously
AnswerB

Iterative development repeatedly produces working, tested functionality in short cycles, directly satisfying the stem's demand for the primary objective. Each iteration builds on validated output, enabling frequent delivery and early feedback rather than a single end-stage release. This continuous cadence distinguishes it from waterfall's sequential phases.

Why this answer

The primary objective is to deliver value in small, manageable increments.

Practice this question →
29
MCQmedium

Your team needs to balance the 'Adaptive' vs 'Predictive' lifecycle. Which criteria should you prioritize when making this choice?

A.The tenure of the team members
B.The total budget allocated to the project
C.The level of uncertainty and risk in the project
D.The seniority of the stakeholders
AnswerC

Uncertainty and risk drive the choice: high uncertainty favours adaptive, exploratory lifecycles, while low uncertainty and stable requirements suit predictive planning. This criterion directly addresses the stem's need to balance the two approaches against project conditions.

Why this answer

The choice between Adaptive (Agile) and Predictive (Waterfall) lifecycles hinges primarily on how well requirements and risks are understood upfront. High uncertainty and risk favor an Adaptive approach because iterative delivery allows course correction as new information emerges. Conversely, low uncertainty and well-understood requirements favor a Predictive approach where detailed upfront planning is safe.

Budget and team tenure are secondary considerations that do not fundamentally dictate lifecycle selection.

Exam trap

DAF often tests the misconception that budget size or team experience determines lifecycle choice, when the real driver is the level of uncertainty and risk in the project.

How to eliminate wrong answers

Option A is wrong because team member tenure (how long people have been on the team) is not a recognized criterion for lifecycle selection in the DAF framework — experience level may influence execution but not the fundamental Adaptive vs Predictive decision. Option B is wrong because total budget size does not determine lifecycle choice; both Adaptive and Predictive projects can operate at any budget scale, and a large budget with high uncertainty still favors Adaptive. Option D is wrong because stakeholder seniority is irrelevant to the uncertainty/risk assessment that drives lifecycle selection — senior stakeholders can exist on either type of project.

Practice this question →
30
MCQeasy

Which of the following best describes the 'Enterprise Awareness' principle in Disciplined Agile?

A.Teams should ignore company policies if they impede agility.
B.The team should delegate all integration tasks to a central architecture group.
C.Teams should work to improve the enterprise, not just their local team.
D.Teams should only focus on their own code quality to ensure speed.
AnswerC

Enterprise Awareness means teams optimise beyond their own boundaries, considering how decisions affect other teams, customers and the wider organisation. Local optimisation that harms the whole contradicts this principle, so the option correctly captures its enterprise-wide scope.

Why this answer

Enterprise Awareness in DA means teams consider the whole organisation and work to improve the enterprise, not just their local team. Option C captures this directly: teams should optimise for enterprise value rather than local metrics. This principle counteracts siloed behaviour and local optimisation.

Exam trap

The trap is confusing Enterprise Awareness with either blind obedience to policy or complete team autonomy — it is actually about teams voluntarily acting for the enterprise's broader benefit.

How to eliminate wrong answers

Option A is wrong because Enterprise Awareness does not license ignoring company policies — DA expects teams to work within governance guardrails and to help evolve them, not bypass them unilaterally. Option B is wrong because delegating integration to a central architecture group contradicts DA's preference for teams owning their own integration and for lightweight, collaborative architecture rather than centralised handoffs. Option D is wrong because focusing only on local code quality is the definition of local optimisation, which Enterprise Awareness explicitly warns against — enterprise value may require cross-team standards, shared components, and integration work.

Practice this question →
31
MCQhard

A team is experiencing 'analysis paralysis' during the initial phase of their project. Which Disciplined Agile strategy is best to move forward?

A.Extend the sprint duration to allow more time for analysis
B.Switch to a full Kanban system without any planning
C.Implement 'Just-in-Time' planning to reduce upfront analysis
D.Mandate a strict waterfall phase gate review
AnswerC

Just-in-time planning focuses on immediate work, reducing unnecessary analysis.

Why this answer

Disciplined Agile suggests 'Evolutionary' approaches, where the team performs just enough planning to start, then adapts.

Practice this question →
32
Multi-Selecthard

Which THREE of these activities are part of the 'Inception' phase in DA?

Select 3 answers
A.Developing the complete product
B.Identifying initial stakeholders
C.Aligning on the project vision
D.Forming the team
E.Closing out the final project budget
AnswersB, C, D

Identifying initial stakeholders belongs to Inception because that phase establishes the project's scope, vision and feasibility before any build work. Stakeholder identification directly satisfies the stem's requirement, as DA places it alongside defining the problem and forming the initial team, rather than in later elaboration or construction iterations.

Why this answer

In the Disciplined Agile (DA) lifecycle, the Inception phase is the startup stage where the team is stood up and the initiative is framed before construction begins. Option B (Identifying initial stakeholders) is correct because Inception includes recognizing who has an interest in or will be affected by the solution so their needs can shape the vision. Option C (Aligning on the project vision) is correct because a primary Inception goal is to reach a shared understanding of the problem, the desired outcome, and the high-level solution direction.

Option D (Forming the team) is correct because Inception covers organizing and chartering the team, including roles, initial staffing, and working agreements, so the team is ready to move into construction. Option A (Developing the complete product) belongs to the Construction/transition work, not Inception, and Option E (Closing out the final project budget) is a Transition/closeout activity, so neither is part of Inception.

Exam trap

DAF often tests the distinction between phase activities, so candidates may confuse Inception with Construction or Transition activities, picking options like 'developing the complete product' or 'closing out the final project budget'.

Practice this question →
33
MCQhard

A team is building a high-criticality system (e.g., medical software). What is the DA approach to documentation?

A.Tailor documentation to meet regulatory and quality needs
B.Rely solely on automated test cases as documentation
C.No documentation is required as per Agile principles
D.Document everything in detail before starting
AnswerA

High-criticality systems demand documented evidence of compliance, so documentation must be tailored to satisfy regulatory and quality standards rather than minimised. This directly addresses the medical-software constraint, where traceability and audit artefacts are mandatory, and aligns with Disciplined Agile's principle of tailoring practices to context.

Why this answer

DA's guidance is to tailor documentation to the actual regulatory, quality, and stakeholder needs of the system being built. For high-criticality systems like medical software, that means producing the traceability, design records, and verification evidence required by standards such as IEC 62304 or FDA design controls, but doing so incrementally rather than upfront. The principle is 'just enough documentation, just in time' scaled to risk.

Exam trap

DAF often tests the false dichotomy that Agile means 'no documentation' versus 'all documentation upfront', causing candidates to miss the correct middle answer of tailoring documentation to regulatory and quality needs.

How to eliminate wrong answers

Option B is wrong because automated test cases alone rarely satisfy regulators, who typically require design rationale, risk analysis, traceability matrices, and verification evidence that tests do not capture. Option C is wrong because the claim that Agile requires no documentation is a myth; DA explicitly rejects it and requires documentation proportional to risk and compliance obligations. Option D is wrong because documenting everything in detail before starting is a waterfall-style big-design-up-front approach that contradicts DA's incremental, risk-based documentation strategy.

Practice this question →
34
MCQmedium

What is the role of the 'Definition of Done' (DoD) in an agile project?

A.To replace the need for project manager oversight
B.To create a clear, shared understanding of what constitutes a completed work item
C.To tell the team how long a task should take
D.To act as a contract for external vendors
AnswerB

The Definition of Done supplies the shared quality criteria that every increment must meet, so the team and stakeholders agree on what "complete" actually means. This directly satisfies the stem's requirement for a common understanding of a finished work item, preventing items being declared done prematurely.

Why this answer

The DoD provides a shared understanding of quality and completeness for an increment.

Practice this question →
35
MCQhard

A team is using a 'Disciplined Agile' lifecycle but is struggling with high levels of 'technical debt' that prevent them from delivering new features. What should the team do next?

A.Create a separate, long-term project to fix the debt.
B.Ignore the debt until a 'system overhaul' phase is authorized.
C.Ask the product owner to prioritize only new features.
D.Incorporate 'Refactoring' and 'Debt Reduction' tasks into the regular iterative planning cycle.
AnswerD

Technical debt is repaid only when explicitly planned; adding refactoring and debt-reduction items to each iteration's backlog makes repayment continuous rather than deferred. This satisfies the stem's constraint that debt currently blocks feature delivery, restoring sustainable flow.

Why this answer

The DA approach to technical debt is to make it visible and address it continuously within the team's regular iterative planning cycle. By incorporating refactoring and debt reduction tasks into each iteration, the team pays down debt incrementally while still delivering new features. This avoids the trap of deferring debt to a separate project, which often never happens or becomes too costly.

Exam trap

The trap is thinking technical debt must be handled in a separate project or deferred, when DA explicitly recommends integrating debt reduction into the regular iterative planning cycle.

How to eliminate wrong answers

Option A is wrong because creating a separate long-term project to fix debt isolates the work from the team's regular flow and often leads to delays, loss of context, and the debt recurring. Option B is wrong because ignoring debt until a system overhaul is authorized is a recipe for escalating costs and declining delivery speed; DA advocates addressing debt continuously. Option C is wrong because prioritizing only new features accelerates debt accumulation and is contrary to DA's guidance to balance new work with debt reduction.

Practice this question →
36
MCQmedium

A stakeholder wants to change the scope mid-iteration. How should the team respond?

A.Discuss the impact and decide whether to incorporate it now or later
B.Accept the change and immediately stop current work
C.Refuse the change immediately
D.Ignore the stakeholder and finish the original work
AnswerA

Agile teams protect the iteration's goal by evaluating the request rather than accepting or rejecting it outright. Assessing value and impact against committed work lets the team decide whether to incorporate the change now or defer it to the backlog, preserving flow.

Why this answer

In agile/iterative delivery, scope changes mid-iteration are handled through collaborative impact assessment rather than unilateral action. The team should evaluate the change's effect on the iteration goal, capacity, and commitments, then decide with the product owner whether to incorporate it now (swapping equivalent work) or defer it to the backlog for a future iteration. This preserves the iteration's integrity while remaining responsive to stakeholder needs, which is the core of agile's 'welcome changing requirements' principle.

Exam trap

DAF often tests the misconception that agile means accepting all changes immediately, but the correct approach is always to assess impact and collaborate with the product owner before deciding.

How to eliminate wrong answers

Option B is wrong because immediately stopping current work to accept the change violates the iteration commitment and ignores impact analysis, risking unfinished work and broken sprint goals. Option C is wrong because refusing outright contradicts agile's embrace of changing requirements and damages stakeholder collaboration. Option D is wrong because ignoring the stakeholder is unprofessional and bypasses the product owner's role in backlog prioritization, leading to misalignment and lost trust.

Practice this question →
37
MCQeasy

When considering 'Continuous Feedback', what is the most effective approach?

A.Use automated dashboards as the only source of feedback
B.Solicit feedback throughout the lifecycle from users and stakeholders
C.Collect feedback only at the end of the project
D.Limit feedback to the internal team members only
AnswerB

Continuous feedback must be gathered iteratively across the whole lifecycle, not confined to a single review or release gate. Soliciting input from users and stakeholders throughout keeps direction aligned with real needs and enables early course correction.

Why this answer

Feedback is most effective when it is frequent, actionable, and involves the right stakeholders.

Practice this question →
38
Multi-Selectmedium

Which THREE of these are considered 'wastes' (muda) in a software development context?

Select 3 answers
A.Code reviews
B.Waiting for information
C.Team collaboration
D.Defect rework
E.Unnecessary features
AnswersB, D, E

Waiting for information is a classic muda, since idle time adds no value while the team is blocked. It directly matches the stem's software development context, where delayed decisions, reviews or dependencies stall flow and inflate cycle time without producing working software.

Why this answer

In Lean software development, muda (waste) refers to any activity that consumes resources without creating value for the customer. Option B (Waiting for information) is correct because idle time spent blocked on handoffs, approvals, or missing requirements adds delay and no customer value. Option D (Defect rework) is correct because reworking bugs or failed builds is pure waste—effort spent correcting work that should have been done right the first time, echoing the Lean principle of building quality in.

Option E (Unnecessary features) is correct because building functionality the customer did not request (overproduction/extra features) consumes effort and increases complexity without delivering value. By contrast, option A (Code reviews) is a value-adding quality practice that catches defects early, and option C (Team collaboration) is essential knowledge-sharing that reduces waste rather than creating it, so neither is classified as muda.

Exam trap

The trap is misidentifying value-adding practices (code reviews, collaboration) as waste — candidates may think any non-coding activity is waste, but Lean distinguishes value-adding from non-value-adding activities.

Practice this question →
39
Multi-Selecthard

Which THREE criteria are important to consider when selecting a delivery lifecycle in DA?

Select 3 answers
A.The preferred color of the workspace
B.The office location of the stakeholders
C.Project team size
D.The level of uncertainty
E.Technical complexity
AnswersC, D, E

Team size constrains coordination overhead and ceremony, so it directly shapes whether a lean or more structured lifecycle fits. DA lists it among the selection criteria alongside uncertainty and complexity, because larger teams need more explicit coordination mechanisms than small colocated ones.

Why this answer

In Disciplined Agile (DA), the delivery lifecycle is chosen based on context factors, and three of the options listed are genuine criteria: C (Project team size) matters because larger teams need more coordination and ceremony, favoring a more structured lifecycle such as a continuous delivery or lean lifecycle, while small teams can use lighter approaches; D (The level of uncertainty) is critical because high uncertainty favors an exploratory/agile lifecycle like Lean or Agile, whereas low uncertainty suits a more predictive or continuous delivery approach; and E (Technical complexity) is important because complex technical solutions may require more architecture, integration, and validation, influencing whether a continuous delivery, exploratory, or lean lifecycle fits best. Options A (The preferred color of the workspace) and B (The office location of the stakeholders) are not DA lifecycle selection criteria, as workspace color is irrelevant and stakeholder location is at most a minor environmental factor, not one of the core criteria for choosing a delivery lifecycle.

Practice this question →
40
MCQhard

A Disciplined Agile team is struggling with unpredictable delivery because they frequently receive urgent requests from different business units. The team lead suggests adopting a 'flow-based' approach. Which of the following best describes how a flow-based approach would help this team?

A.It limits work in progress and visualizes the value stream to manage demand and reduce multitasking.
B.It requires all work to be estimated in story points and planned in fixed-length iterations.
C.It mandates a single-piece flow where only one item is worked on at a time by the entire team.
D.It eliminates the need for a product backlog and replaces it with a continuous stream of unplanned work.
AnswerA

A flow-based approach, often implemented with Kanban, uses work-in-progress limits and visual management to expose bottlenecks and balance demand against capacity. By limiting WIP, the team reduces context switching and can better handle urgent requests without derailing all other work. Visualizing the value stream also helps stakeholders see the impact of new requests, enabling more disciplined prioritization.

Why this answer

A flow-based approach helps by making work visible and limiting WIP, which directly addresses the chaos of urgent requests. It allows the team to manage demand, expose capacity constraints, and have data-driven conversations with stakeholders about prioritization. This leads to more predictable delivery even when requests vary, because the team can control the amount of work in process and focus on completing items.

Exam trap

The trap here is confusing flow-based with iteration-based approaches, or assuming that flow means no planning or unlimited work intake.

Practice this question →
41
MCQmedium

When planning, what is the difference between 'Predictive' and 'Adaptive' planning?

A.Predictive planning is not allowed in Disciplined Agile
B.Predictive planning is better for high-uncertainty projects
C.Adaptive planning is always faster than predictive
D.Adaptive planning evolves as the project progresses based on feedback
AnswerD

Adaptive planning deliberately defers detailed scope decisions until feedback from working increments arrives, so the plan is revised each iteration. This contrasts with predictive planning, which fixes scope and schedule upfront. It satisfies the scenario's need for a plan that responds to emerging learning rather than assuming stable requirements.

Why this answer

Predictive planning is upfront and detailed, while adaptive is rolling-wave and iterative.

Practice this question →
42
MCQmedium

During a project, the team realizes the initial plan is no longer viable due to market changes. What should they do?

A.Wait for the end of the year to reassess
B.Ask the stakeholders to force the team to continue
C.Stick to the original plan to show commitment
D.Update the plan and pivot the strategy accordingly
AnswerD

Updating the plan and pivoting preserves alignment with current market reality instead of executing a plan whose assumptions have failed. This satisfies the stem's constraint that the initial plan is no longer viable, reflecting Agile's empirical approach of responding to change over following a fixed, outdated baseline.

Why this answer

Agile teams embrace change and pivot based on empirical evidence and feedback.

Practice this question →
43
Multi-Selecthard

Which THREE of the following strategies help in 'scaling' Agile across multiple teams?

Select 3 answers
A.Increase the number of project managers
B.Use shared communication tools
C.Ensure each team uses a different framework
D.Coordinate activities across teams
E.Establish a consistent 'Definition of Done'
AnswersB, D, E

Scaling requires coordination across team boundaries, and shared communication tools give distributed teams a common channel for status, dependencies and decisions. This directly addresses the scaling constraint of maintaining alignment when work spans multiple teams.

Why this answer

Option B is correct because shared communication tools (e.g., Jira, Confluence, Slack, or Azure DevOps) give distributed Agile teams a single source of truth for backlogs, sprint boards, and impediments, enabling transparency and synchronization at scale. Option D is correct because coordinating activities across teams — through Scrum of Scrums, PI Planning, or dependency-mapping ceremonies — manages cross-team dependencies and integration points that inevitably arise when many teams work on one product. Option E is correct because a consistent Definition of Done ensures every team applies the same quality bar (e.g., code reviewed, tests passed, CI green, documentation updated), so increments from different teams are genuinely integratable and releasable.

Option A is not correct because adding project managers increases overhead and central control rather than enabling the self-organizing, empirical flow that Agile scaling frameworks rely on. Option C is not correct because mixing frameworks per team (e.g., one Scrum, one Kanban, one SAFe) fragments terminology, cadence, and metrics, making cross-team coordination and shared planning far harder.

Exam trap

DAF often tests the misconception that scaling Agile means adding more managers or letting each team choose its own framework — candidates pick 'increase project managers' or 'different frameworks per team' because they sound like autonomy or oversight, but both undermine alignment and coordination.

Practice this question →
44
MCQeasy

What is the purpose of a 'Retrospective'?

A.To critique individual performance
B.To report progress to the stakeholders
C.To improve the team's way of working
D.To plan the next set of features
AnswerC

The Retrospective is the dedicated inspect-and-adapt ceremony held at iteration end, where the team examines its own processes and agrees concrete changes. This directly satisfies the stem's purpose of improving the team's way of working, rather than reviewing product scope or individual performance.

Why this answer

Retrospectives are for team reflection and process improvement.

Practice this question →
45
MCQhard

A team is transitioning to a 'Disciplined Agile' way of working. They need to handle 'Governance'. How is governance defined in DA?

A.A set of strict, compliance-driven checkpoints
B.Something that happens only during the final release
C.Lightweight and integrated into the workflow
D.The responsibility of a separate audit department
AnswerC

Disciplined Agile defines governance as lightweight and embedded within the team's workflow, rather than a heavyweight, separate control layer. This satisfies the transition constraint by letting the team self-organise while remaining accountable, with decision-making and compliance checks woven into daily ceremonies instead of imposed through external gate reviews.

Why this answer

In Disciplined Agile, governance is defined as lightweight and integrated into the team's workflow, not as a separate, heavyweight control layer. It is a continuous, collaborative activity that ensures the team is doing the right thing in the right way, and it is owned by the team and its stakeholders. This makes governance compatible with agile delivery rather than opposed to it.

Exam trap

DAF often tests the misconception that governance must be a strict, external, phase-gate activity, so candidates who equate governance with compliance checkpoints pick the wrong answer instead of recognizing DA's lightweight, integrated definition.

How to eliminate wrong answers

Option A is wrong because strict, compliance-driven checkpoints describe a traditional phase-gate governance model, which DA explicitly moves away from. Option B is wrong because governance in DA is continuous throughout the lifecycle, not a one-time event at final release. Option D is wrong because governance is not delegated to a separate audit department; in DA it is a shared responsibility of the team, stakeholders, and enterprise, integrated into daily work.

Practice this question →
46
MCQhard

A team is struggling with the 'Inception' phase. What is the goal of this phase in DAD?

A.Write all the code for the MVP
B.Complete 100% of the project design
C.Gain stakeholder alignment and establish a viable strategy
D.Finalize the budget and vendor contracts
AnswerC

The Inception phase in Disciplined Agile Delivery exists to align stakeholders around a shared vision and secure funding and initial scope before construction begins. Gaining stakeholder alignment and establishing a viable strategy directly satisfies the stem's requirement, since Inception's purpose is precisely to set direction and obtain consensus, not to build or release.

Why this answer

In Disciplined Agile Delivery (DAD), the Inception phase is a short, collaborative start-up effort whose primary goal is to gain stakeholder alignment and establish a viable strategy for the initiative. It is not about producing code or completing design, but about ensuring the team and stakeholders share a common vision and direction before committing to delivery.

Exam trap

DAF often tests the misconception that Inception equals full design or MVP development — candidates pick 'complete 100% of the project design' because it sounds like a thorough start, but DA explicitly rejects big up-front design in favor of alignment and a viable strategy.

How to eliminate wrong answers

Option A is wrong because writing all the code for the MVP is a Construction-phase activity — Inception produces a vision and strategy, not working software. Option B is wrong because completing 100% of the project design contradicts DA's embrace of 'just enough' up-front planning; DA is iterative and design evolves throughout the lifecycle. Option D is wrong because finalizing the budget and vendor contracts is a governance/procurement activity that may occur alongside Inception but is not its defining goal — Inception focuses on alignment and strategy, not contractual closure.

Practice this question →
47
MCQeasy

What is 'Velocity' in an agile project?

A.A measure of the volume of work a team completes per iteration
B.The total number of bugs found in the product
C.The number of hours worked by the team
D.The speed at which the project manager moves tasks
AnswerA

Velocity quantifies completed work per iteration, typically by summing story points or similar size estimates for items meeting the team's definition of done. It is a planning and forecasting input, not a productivity metric, and its value depends on consistent estimation across iterations.

Why this answer

Velocity is a measure of the amount of work a team completes in a given iteration.

Practice this question →
48
MCQmedium

Your team is struggling with scope creep due to unclear requirements from stakeholders. Using Disciplined Agile principles, what is the most appropriate action?

A.Increase the frequency of stakeholder feedback loops
B.Hire a dedicated business analyst to write detailed documentation
C.Lock down the scope for the next six months
D.Ignore the stakeholders until the product increment is finished
AnswerA

Increasing the frequency of stakeholder feedback loops shortens the gap between requirement clarification and delivery, surfacing ambiguity before it becomes scope creep. It satisfies the stem by tightening collaboration cadence, letting the team validate assumptions early and adjust scope continuously.

Why this answer

Scope creep from unclear requirements is best addressed by tightening and increasing feedback loops with stakeholders so requirements are clarified iteratively and misunderstandings surface early. DA favours frequent, lightweight stakeholder collaboration over documentation-heavy or scope-freezing approaches. This aligns with DA's principle of delighting customers through continuous engagement.

Exam trap

The trap is choosing a plan-driven fix (documentation, scope freeze) for an agile problem — DAF expects candidates to favour feedback loops and iterative clarification.

How to eliminate wrong answers

Option B is wrong because hiring a dedicated business analyst to write detailed documentation is a traditional, plan-driven response that adds handoff and delay rather than improving the feedback loop; DA prefers collaborative requirement elaboration. Option C is wrong because locking down scope for six months contradicts agile and DA principles of embracing change and delivering value incrementally — it treats the symptom by freezing requirements rather than resolving ambiguity. Option D is wrong because ignoring stakeholders until the increment is finished guarantees rework and misalignment, directly violating DA's emphasis on continuous stakeholder collaboration.

Practice this question →
49
Multi-Selecteasy

Which THREE are characteristics of a 'high-performing' Agile team?

Select 3 answers
A.Shared accountability for results
B.High trust among team members
C.Strict adherence to the initial plan
D.A leader who dictates every action
E.A focus on continuous improvement
AnswersA, B, E

High-performing teams hold collective ownership of outcomes rather than individuals owning isolated tasks. Shared accountability for results satisfies the stem's characteristic, since the team commits to delivering value together and absorbs setbacks as a group instead of assigning blame.

Why this answer

Option A (Shared accountability for results) is correct because high-performing Agile teams collectively own outcomes rather than siloing responsibility, which aligns with Agile principles of self-organizing teams. Option B (High trust among team members) is correct because trust enables open communication, psychological safety, and rapid collaboration, all essential for high performance. Option E (A focus on continuous improvement) is correct because Agile teams regularly inspect and adapt through retrospectives and iterative delivery to raise effectiveness.

Option C is incorrect because Agile values responding to change over strict adherence to an initial plan. Option D is incorrect because Agile teams are self-organizing, not led by a leader who dictates every action.

Exam trap

DAF often tests whether candidates can separate genuine high-performing team traits (trust, shared accountability, continuous improvement) from command-and-control or plan-worship behaviors that sound disciplined but are actually anti-agile.

Practice this question →
50
MCQeasy

A new project team is struggling to choose between a Scrum-based approach and a Lean-based approach. Which Disciplined Agile principle should the coach emphasize to help them decide?

A.Let the senior project manager decide the methodology.
B.Context counts.
C.Always choose Lean as it is inherently superior to Scrum.
D.Follow the Scrum Guide strictly to ensure consistency.
AnswerB

Context counts directs the team to fit their approach to their specific situation rather than defaulting to one method. This satisfies the stem by giving the coach a Disciplined Agile principle for choosing between Scrum and Lean based on actual circumstances.

Why this answer

'Context counts' is one of the foundational Disciplined Agile principles: the right way of working depends on the situation — team size, culture, regulatory environment, product complexity, and customer needs. Rather than dogmatically choosing Scrum or Lean, the coach should guide the team to fit the method to their context using DA's goal-driven, choice-based approach. This is the essence of DA's 'choice is good' philosophy.

Exam trap

DAF often tests the misconception that DA endorses one methodology (Scrum or Lean) as universally superior — candidates who pick a 'best framework' answer miss the core DA principle that context determines the right approach.

How to eliminate wrong answers

Option A is wrong because DA explicitly rejects top-down, command-and-control methodology selection by a single authority — the team owns its way of working (WoW) and evolves it collaboratively. Option C is wrong because DA does not declare any one method inherently superior; Lean and Scrum each fit different contexts, and DA's whole premise is that no single framework is universally best. Option D is wrong because strictly following the Scrum Guide contradicts DA's principle of tailoring and its recognition that Scrum is just one of many viable strategies — DA even documents how Scrum can be extended or hybridized.

Practice this question →
51
MCQeasy

Which of these is a key 'Agile' value?

A.Comprehensive documentation over working software
B.Following processes over individuals and interactions
C.Contract negotiation over customer collaboration
D.Responding to change over following a plan
AnswerD

The Agile Manifesto values responding to change over following a plan, prioritising adaptability when requirements shift. This is the specific value pairing, not a general preference for flexibility, and it directly matches the option as stated.

Why this answer

The Agile Manifesto explicitly states 'Responding to change over following a plan' as one of its four core values. This value acknowledges that in complex product development, requirements and understanding evolve, so the ability to adapt to changing circumstances is more valuable than rigid adherence to an upfront plan. The other three values in the Manifesto are: individuals and interactions over processes and tools, working software over comprehensive documentation, and customer collaboration over contract negotiation.

Exam trap

DAF often tests the Agile Manifesto values by presenting reversed versions — candidates who don't memorize the exact 'X over Y' ordering may select an inverted option that sounds plausible.

How to eliminate wrong answers

Option A is wrong because it reverses the Agile value — the Manifesto values working software over comprehensive documentation, not the other way around. Option B is wrong because it also reverses the value — the Manifesto values individuals and interactions over processes and tools, not the reverse. Option C is wrong because it reverses the third value — the Manifesto values customer collaboration over contract negotiation, not contract negotiation over collaboration.

All three wrong options are direct inversions of the actual Agile Manifesto values, making them easy to eliminate if you know the correct ordering.

Practice this question →
52
MCQmedium

A team finds that their current workflow is plagued by bottlenecks at the quality assurance stage, causing delays in delivery. According to Disciplined Agile, which action should the team prioritize to improve their process?

A.Focus on the process goal 'Coordinate Activities' to ensure all members are aligned.
B.Increase the batch size to allow QA to process more items at once.
C.Implement the 'Improve Team Productivity' process goal by identifying and removing the specific constraint causing the delay.
D.Switch to a purely predictive model to ensure quality gates are strictly followed.
AnswerC

The Improve Team Productivity process goal directs the team to find and eliminate the constraint limiting throughput. Applying it to the QA bottleneck removes the specific delay source, improving delivery flow rather than optimising non-constraint stages.

Why this answer

In Disciplined Agile, when a workflow has a bottleneck (like QA), the team should apply the 'Improve Team Productivity' process goal, which explicitly includes identifying and removing constraints using lean/Theory of Constraints thinking. The QA stage is the constraint; the correct action is to find and eliminate it (e.g., automate tests, cross-train, shift-left quality) rather than optimize elsewhere. This aligns with DA's guidance to address the system constraint, not symptoms.

Exam trap

DAF often tests whether candidates apply lean/ToC thinking (fix the constraint) versus generic coordination or scaling answers that sound plausible but do not address the bottleneck.

How to eliminate wrong answers

Option A is wrong because 'Coordinate Activities' addresses alignment and communication across teams, not the throughput constraint causing delivery delays. Option B is wrong because increasing batch size is the opposite of lean guidance — larger batches increase WIP, delay feedback, and worsen bottlenecks (Little's Law). Option D is wrong because switching to a purely predictive model does not remove the QA constraint; it just changes planning style and often adds rigidity that worsens flow.

Practice this question →
53
MCQeasy

Which of the following is an example of an 'Agile' feedback loop?

A.Having the team work independently on features
B.Creating a Gantt chart of the project timeline
C.Sending a weekly status email to the project sponsor
D.Conducting a product demo with stakeholders
AnswerD

A product demo gives stakeholders direct visibility of a working increment, letting them inspect it and return feedback that shapes the next iteration. That inspect-and-adapt cycle is the defining Agile feedback loop, satisfying the stem's requirement for a genuine example rather than an internal ceremony.

Why this answer

An Agile feedback loop is any mechanism that shortens the cycle between producing work and receiving validated input from stakeholders, enabling course correction. Conducting a product demo with stakeholders is a classic feedback loop because it puts working product in front of real users or sponsors and generates actionable input that feeds the next iteration.

Exam trap

DAF often tests whether candidates can distinguish genuine two-way feedback loops (demos, reviews, retrospectives) from one-way reporting artifacts (status emails, Gantt charts) that look like communication but do not close the loop.

How to eliminate wrong answers

Option A is wrong because having the team work independently on features is the opposite of a feedback loop — it isolates work and delays integration and validation. Option B is wrong because a Gantt chart is a predictive, plan-driven artifact that documents a fixed schedule rather than generating iterative feedback. Option C is wrong because a weekly status email is one-way reporting to a sponsor, not a two-way feedback mechanism that validates product increments; it reports progress, it does not solicit course-correcting input.

Practice this question →
54
Multi-Selectmedium

Which TWO of the following are 'Lean' concepts applied in DA?

Select 2 answers
A.Mandating a fixed-price contract
B.Forcing team members to work long hours
C.Elimination of waste
D.Maximizing the number of features in a release
E.Optimizing the flow of value
AnswersC, E

Eliminating waste removes activities that consume effort without adding customer value, such as waiting, rework and handoffs. This satisfies the stem's requirement for a Lean concept applied in DA, since waste elimination is the foundational Lean principle underpinning value-stream mapping and continuous improvement.

Why this answer

Option C, elimination of waste, is a core Lean concept: Lean defines value from the customer's perspective and systematically removes non-value-adding activities (muda) such as waiting, handoffs, rework, and partially done work, which in DA (Disciplined Agile) translates into streamlining ceremonies, artifacts, and governance. Option E, optimizing the flow of value, is likewise central to Lean thinking: it emphasizes making value flow smoothly through the delivery pipeline by limiting work in progress, reducing batch sizes, and pulling work rather than pushing it, which DA applies through its value stream and continuous improvement guidance. The unmarked options do not belong: A (mandating a fixed-price contract) is a contractual/commercial constraint, not a Lean principle, and Lean favors adaptive, value-driven agreements; B (forcing long hours) contradicts Lean's respect for people and sustainable pace, and overwork increases defects and waste; D (maximizing the number of features in a release) is output-focused rather than value-focused and conflicts with Lean's aim of delivering only what the customer values while minimizing waste.

Exam trap

DAF often tests whether candidates can distinguish genuine Lean concepts from generic management or productivity directives, so options like fixed-price contracts, long hours, and feature maximization are planted as plausible-sounding but anti-Lean distractors.

Practice this question →
55
Multi-Selecteasy

Which TWO are common 'Agile' ceremonies?

Select 2 answers
A.Retrospective
B.Budget approval meeting
C.Project planning meeting (held once at the start)
D.Weekly status report to executives
E.Sprint Planning
AnswersA, E

The retrospective is a recurring inspect-and-adapt ceremony where the team examines its process and agrees improvements. It is a standard Agile event, distinct from Disciplined Agile's broader process-goal guidance, and satisfies the stem by being one of the two commonly recognised ceremonies.

Why this answer

Retrospective (A) is a core Agile ceremony held at the end of each iteration/sprint, where the team inspects how it worked and identifies improvements to apply in the next sprint. Sprint Planning (E) is also a standard Scrum/Agile ceremony that occurs at the start of every sprint to define the sprint goal and select the backlog items the team will deliver. Both are recurring, team-level events that support iterative delivery and continuous improvement.

In contrast, budget approval (B) and weekly executive status reporting (D) are governance/reporting activities rather than Agile ceremonies, and a one-time project planning meeting at the start (C) reflects a traditional waterfall approach, not the recurring planning cadence of Agile.

Exam trap

DAF often tests whether candidates can distinguish recurring agile ceremonies (Sprint Planning, Retrospective, Daily Scrum, Sprint Review) from traditional project management meetings (budget approval, one-time planning, executive status reports).

Practice this question →
56
Multi-Selectmedium

Which TWO of the following are valid ways for an Agile team to improve their way of working (WoW)?

Select 2 answers
A.Copy the process of the highest-performing team in the company
B.Experiment with new practices in a controlled way
C.Wait for management to dictate new processes
D.Hold regular retrospectives to identify improvements
E.Use the exact same tools as other teams
AnswersB, D

Controlled experimentation lets a team trial a new practice within bounded scope, measure the effect and retain or discard it. This satisfies the stem's requirement for a valid improvement route, since it changes the way of working based on evidence rather than assumption.

Why this answer

Option B is correct because Agile teams improve their way of working through deliberate experimentation: trying a new practice on a small scale, measuring its effect, and inspecting and adapting based on the results, which is the essence of empiricism. Option D is correct because the retrospective is the dedicated Scrum/Agile event where the team regularly inspects how it works and identifies concrete improvements to apply in the next iteration, making it the primary mechanism for continuous WoW improvement. Option A is not valid because blindly copying another team's process ignores the team's own context, constraints, and empirical data, and best practices cannot simply be transplanted.

Option C is not valid because Agile teams are self-managing and own their process; waiting for management to dictate processes contradicts self-organization and continuous improvement. Option E is not valid because adopting identical tools does not improve a team's way of working and may not fit the team's needs, since tools are enablers rather than the source of process improvement.

Exam trap

DAF often tests the distinction between active, team-driven improvement (experimentation and retrospectives) and passive or imitative approaches (copying others, waiting for management) — the trap is selecting answers that sound plausible but violate DA's principles of empowerment and context-driven improvement.

Practice this question →
57
MCQeasy

A team is transitioning from a traditional project management approach to Disciplined Agile. Which mindset shift is most critical for the team to embrace during their first iteration?

A.Eliminating all documentation throughout the lifecycle
B.Strict adherence to the project charter
C.Reducing the team size to improve velocity
D.Focusing on delivering high-value, working software early and often
AnswerD

Traditional project management defers value to phase gates; Disciplined Agile instead demands incremental delivery of working software each iteration. This shift satisfies the stem's first-iteration constraint by replacing document-driven progress with demonstrable, high-value output that generates early feedback.

Why this answer

The core of Disciplined Agile is the pragmatic shift towards value delivery over rigid adherence to process, emphasizing a 'choose your way of working' approach.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Foundations OF Agile questions.

Start 20-question session