DAF Practice Test 3 — 30 Questions

Question 1

A team is using a basic Kanban approach and wants to improve their throughput. Which step is most aligned with the DA toolkit?

Accepted Answer

Review their current process goals and experiment with a practice that limits WIP.. The DA (Disciplined Agile) toolkit emphasizes empirical process improvement through inspecting current goals and experimenting with practices. Limiting WIP is a core Lean/Kanban practice that directly improves flow and throughput by reducing multitasking and bottlenecks. Reviewing process goals and experimenting aligns with DA's guided continuous improvement philosophy.

Answer

Increase team member hours.

Answer

Ignore the bottleneck and work faster.

Answer

Switch to a full Scrum implementation.

Question 2

A team has decided to use the 'Scrum' lifecycle. According to DA, what is the next step after selecting the lifecycle?

Accepted Answer

Identify and address the process goals within the lifecycle.. In Disciplined Agile (DA), after selecting a lifecycle (such as Scrum), the team must identify and address the process goals that are relevant to that lifecycle. Process goals are the foundational activities that guide how the team will work, and they must be tailored to the team's context. This step ensures that the team doesn't just adopt a superficial set of ceremonies but instead focuses on the underlying goals that drive success. Only after addressing these goals can the team effectively start executing the lifecycle.

Answer

Report the choice to the executive sponsor.

Answer

Start the first sprint immediately.

Answer

Hire a Scrum expert to manage the team.

Question 3

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

Accepted Answer

To create a clear, shared understanding of what constitutes a completed work item. The DoD provides a shared understanding of quality and completeness for an increment.

Answer

To replace the need for project manager oversight

Answer

To tell the team how long a task should take

Answer

To act as a contract for external vendors

Question 4

In the DA framework, what is the 'Transition' phase primarily focused on?

Accepted Answer

Deployment and release. In Disciplined Agile, the Transition phase focuses on deploying the solution to production and releasing it to stakeholders. It covers activities like release planning, deployment, and operational readiness, ensuring the solution is delivered and supported. This phase follows Construction and precedes ongoing operations and continuous improvement.

Answer

Continuous improvement

Answer

Requirement gathering

Answer

Team building

Question 5

Which THREE of the following represent ways to reduce handoffs?

Accepted Answer

Automating the delivery pipeline to minimize manual intervention.. Option A is correct because automating the delivery pipeline (e.g., CI/CD with automated build, test, and deploy stages) removes the manual handoffs between development, QA, and operations that occur when artifacts are passed between people or teams. Option B is correct because co-locating team members who need to collaborate frequently replaces formal, asynchronous handoffs with direct, high-bandwidth communication, reducing the transfer of work between separate locations or groups. Option C is correct because cross-functional teams that own features end-to-end keep the skills needed for the whole value stream (dev, test, ops) within one team, eliminating the sequential handoffs to external specialist teams. Option D does not belong because outsourcing to a vendor creates additional organizational boundaries and handoffs rather than reducing them. Option E does not belong because adding a management layer to monitor transfers adds coordination overhead and does not remove the handoffs themselves.

Answer

Outsourcing non-core tasks to a specialized vendor.

Answer

Adding an extra layer of management to monitor transfers.

Question 6

What is the primary benefit of the 'Process Goal' structure in the DA toolkit?

Accepted Answer

It provides a clear way to navigate and choose practices.. The 'Process Goal' structure in the DA toolkit provides a clear way to navigate and choose practices by organizing them around what the team wants to achieve rather than prescribing a fixed set of steps. Each process goal describes a desired outcome and offers a range of practices that can be selected based on context. This structure supports the 'Choose Your WoW' philosophy by making it easier to identify relevant practices.

Answer

It replaces the need for a Project Manager.

Answer

It ensures that teams only use Lean practices.

Answer

It forces teams to adopt a specific lifecycle.

Question 7

Which THREE of the following factors would influence your choice of lifecycle within the DA toolkit?

Accepted Answer

The regulatory compliance requirements.. Option A (regulatory compliance requirements) is correct because the DA (Disciplined Agile) toolkit requires lifecycle selection to account for governance and compliance obligations; highly regulated environments favor more predictive, phase-gated lifecycles with documented control points, while low-regulation contexts can safely use agile or lean approaches. Option C (the maturity of the team) is correct because team capability and experience directly shape which lifecycle is viable: a less experienced or newly formed team typically needs the structure and guidance of a predictive or hybrid lifecycle, whereas a mature, self-organizing team can operate effectively with a continuous delivery or lean lifecycle. Option E (the duration of the project) is correct because project length influences lifecycle fit: short, well-bounded efforts suit agile or lean continuous approaches, while long, complex initiatives with evolving scope often benefit from hybrid or predictive lifecycles with staged governance. Options B (office wall color) and D (team member salaries) are incorrect because they are irrelevant environmental or compensation details that have no bearing on the factors DA uses to guide lifecycle selection, such as compliance, team maturity, project duration, delivery cadence, and solution complexity.

Answer

The color of the team's office walls.

Answer

The salary of the team members.

Question 8

What is the role of 'Enterprise Awareness' in the DA toolkit?

Accepted Answer

To encourage team members to act in the best interest of the organization. Enterprise Awareness in DA is a guiding principle that encourages individuals and teams to consider the whole organisation when making decisions, rather than optimising only for their local team. It pushes teams to act in the best interest of the enterprise, even when that means accepting a locally suboptimal outcome. This is distinct from standardisation or reporting mandates.

Answer

To ensure everyone works the same way

Answer

To report all team activities to management

Answer

To limit the team to internal tasks

Question 9

If you have a 'bottleneck', how does increasing local efficiency at a non-bottleneck step affect the system?

Accepted Answer

It increases the pile-up at the bottleneck.. Increasing speed at a non-bottleneck simply pushes more work to the bottleneck, increasing the pile-up without increasing system throughput.

Answer

It reduces the cycle time of the entire system.

Answer

It has no effect on the system.

Answer

It improves the total throughput of the system.

Question 10

Which THREE of the following actions support the Lean principle 'Build Quality In'?

Accepted Answer

Using automated regression testing.. Option C (Using automated regression testing) is correct because it embeds quality checks into the delivery pipeline, catching defects immediately after each change rather than letting them accumulate, which directly supports building quality in at the source. Option D (Performing continuous integration) is correct because CI automatically builds and tests every commit, providing fast feedback and preventing integration defects from compounding, which is a core mechanism for building quality into the product. Option E (Implementing Test-Driven Development (TDD)) is correct because writing tests before code forces quality requirements into the design and implementation from the start, eliminating defects at the earliest possible point. Option A (Deferring testing until the end of the project) is not correct because late-stage testing allows defects to accumulate and violates the build-quality-in principle of early detection. Option B (Relying on manual testing by an external team) is not correct because outsourcing manual testing creates delayed, non-continuous feedback and does not embed quality into the development process itself.

Answer

Deferring testing until the end of the project.

Answer

Relying on manual testing by an external team.

Question 11

When applying the principle of 'Optimize the Whole', how should you view a 'specialized' sub-team?

Accepted Answer

As a potential silo that should be integrated into cross-functional flow.. Specialized teams often act as silos. The goal is to integrate them into a cross-functional unit to improve end-to-end flow.

Answer

As the most important part of the organization.

Answer

As a group that should work at their own pace.

Answer

As a highly efficient unit that should be kept separate.

Question 12

You are trying to improve flow in a cross-functional team. How does 'T-shaped' skill development support this?

Accepted Answer

It enables team members to help each other, preventing bottlenecks.. T-shaped skills allow team members to jump in and help others during bottlenecks, preventing work from stalling.

Answer

It reduces the need for salary increases.

Answer

It increases the number of people available for specialized tasks.

Answer

It makes documentation unnecessary.

Question 13

Which TWO of the following statements correctly describe how a team should evolve its Way of Working according to Disciplined Agile?

Accepted Answer

Improvement should be continuous and guided by the team's current context.. Option A is correct because Disciplined Agile (DA) treats the Way of Working (WoW) as something a team continuously evolves and tailors to its own context — the team's size, domain, culture, and constraints — rather than adopting a one-size-fits-all process. Option C is correct because DA's guided continuous improvement (GCI) approach relies on empirical data and regular retrospectives to inspect what is working, identify experiments, and verify that changes actually improve outcomes. Options B, D, and E are incorrect: DA deliberately keeps process ownership with the team rather than outsourcing it to external consultants, rejects the churn of swapping frameworks every quarter in favor of incremental, context-driven improvement, and depends on retrospectives as a core inspect-and-adapt mechanism, so skipping them would undermine the very feedback loop that drives WoW evolution.

Answer

Teams should rely on external consultants to define their process.

Answer

Teams should adopt a new framework every quarter to stay modern.

Answer

Teams should skip retrospectives to maximize delivery time.

Question 14

You are managing a program that spans multiple DA teams. Which process blade helps manage the dependency between these teams?

Accepted Answer

Coordinate Activities. In Disciplined Agile, the Coordinate Activities process blade exists specifically to manage dependencies, risks, and coordination across multiple teams, including across the enterprise. When a program spans multiple DA teams, Coordinate Activities provides the guidance for aligning their work, resolving cross-team dependencies, and coordinating releases — making it the correct blade for managing inter-team dependencies.

Answer

Team Development

Answer

Product Management

Answer

Governance

Question 15

Which THREE of the following are important aspects of DA Governance?

Accepted Answer

Lean. DA Governance (Data Analytics Governance) is important because it must be Lean (option A), meaning it should minimize bureaucracy and overhead so that governance enables rather than blocks analytics delivery. It should also be Automated (option C), using tooling, policy-as-code, and automated monitoring/enforcement to keep governance consistent and scalable across data pipelines and models. Finally, it must be Risk-based (option D), prioritizing controls and oversight according to the sensitivity, regulatory impact, and business criticality of the data and analytics use cases. Options B (Command and Control) and E (Manual and heavy) do not belong because DA Governance deliberately avoids rigid, top-down command-and-control structures and manual, heavyweight processes, which slow down analytics and reduce adoption.

Answer

Command and Control

Answer

Manual and heavy

Question 16

How should a team handle an 'emergency' request in a Kanban system that is already at its WIP limit?

Accepted Answer

Discuss the trade-off and decide if the emergency justifies exceeding the WIP limit.. In Kanban, WIP limits are policies, not absolute laws, and the correct response to an emergency is to make the trade-off explicit: discuss what will be delayed or stopped if the emergency is pulled in, and decide consciously whether the emergency justifies exceeding the limit. This preserves the team's ability to manage flow while acknowledging that some situations genuinely warrant an exception.

Answer

Refuse the request at all costs.

Answer

Ask the team to work late to finish it.

Answer

Automatically prioritize the emergency and break all WIP limits.

Question 17

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

Accepted Answer

They reduce dependencies on other teams. 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.

Answer

They work faster than specialized teams

Answer

They can work on more projects at once

Answer

They don't need a team leader

Question 18

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?

Accepted Answer

Educate stakeholders on the tradeoffs by using a 'Range-Based' planning approach to show how scope can be flexed to hit the date.. 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.

Answer

Report the project as failing because it cannot be purely agile.

Answer

Accept the constraints and reduce the testing phase duration to meet the date.

Answer

Explain that agile methods do not allow for deadlines.

Question 19

What is the primary purpose of 'Little's Law' in Lean?

Accepted Answer

To relate WIP, Throughput, and Cycle Time mathematically.. Little's Law states that the average number of items in a queuing system (WIP) equals the average arrival rate (Throughput) multiplied by the average time an item spends in the system (Cycle Time): WIP = Throughput × Cycle Time. In Lean and Kanban, this relationship is used to predict how reducing WIP or increasing throughput affects cycle time, making it a foundational flow metric.

Answer

To measure individual developer productivity.

Answer

To determine the number of staff members needed.

Answer

To calculate the total project budget.

Question 20

You are analyzing why a project failed to deliver value. Which DA concept should you apply for post-mortem?

Accepted Answer

Apply the 'Improve Process' goal. DA's 'Improve Process' goal is the framework's mechanism for retrospectives and process improvement, making it the right concept to apply when analyzing why a project failed to deliver value. It guides the team to inspect what happened, identify root causes, and adapt their way of working. This is a blameless, systems-thinking approach rather than a people-focused one.

Answer

Blame the developers

Answer

Change all team members

Answer

Restart the project with a new lead