DAF Practice Test 5 — 25 Questions

Question 1

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?

Accepted Answer

Incorporate 'Refactoring' and 'Debt Reduction' tasks into the regular iterative planning cycle.. 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.

Answer

Create a separate, long-term project to fix the debt.

Answer

Ignore the debt until a 'system overhaul' phase is authorized.

Answer

Ask the product owner to prioritize only new features.

Question 2

What is the relationship between 'Flow' and 'Value' in Lean?

Accepted Answer

Flow is the mechanism that enables value delivery.. In Lean, value is defined from the customer's perspective as what they are willing to pay for, and flow is the uninterrupted movement of work or materials through the value stream that delivers that value. Flow is the mechanism — the smooth, continuous progression of work — that enables value to reach the customer without delays, rework, or waste. Thus flow enables value delivery.

Answer

Value is achieved by stopping all flow.

Answer

Flow is only for manufacturing, not software.

Answer

Flow and value are completely unrelated.

Question 3

What is the primary role of the 'DA Flex' (or DA toolkit application) in an organization?

Accepted Answer

To enable teams to pick the best practices for their specific context.. The DA Flex (or DA toolkit application) is designed to enable teams to select and tailor the best practices that fit their specific context. It provides a structured but flexible approach, allowing teams to choose from a range of practices rather than imposing a rigid process. This aligns with the Disciplined Agile principle of context-sensitive agility.

Answer

To monitor team performance against a standard.

Answer

To provide a rigid process that must be followed by all.

Answer

To standardize all team tools.

Question 4

You are a team lead in a DA environment. How do you resolve a conflict regarding technical direction?

Accepted Answer

Consult the Architecture Owner. In Disciplined Agile, the Architecture Owner is the role responsible for guiding technical decisions, ensuring architectural integrity, and facilitating technical discussions. When a conflict arises regarding technical direction, the team lead should consult the Architecture Owner, who has the expertise and authority to guide the decision. This aligns with DA's principle of organizing around products/services with clear ownership.

Answer

Leave it to the Product Owner

Answer

Ask senior management to decide

Answer

Vote in the team meeting

Question 5

Your team is struggling with frequent context switching. As a Disciplined Agile practitioner, which process blade would you consult to better manage your work flow?

Accepted Answer

Coordinate Activities. The Coordinate Activities process blade in Disciplined Agile focuses on managing the flow of work across teams, including planning, scheduling, and coordinating dependencies. It directly addresses issues like context switching by providing practices to visualize and limit work in progress, manage queues, and coordinate activities to reduce multitasking. This blade encompasses techniques such as kanban, Scrum of Scrums, and other coordination mechanisms that help teams maintain a smooth workflow.

Answer

Team Development

Answer

Financial Management

Answer

People Management

Question 6

What is the primary goal of the 'Form Team' process blade?

Accepted Answer

To define roles and organizational structure. The primary goal of the 'Form Team' process blade in Disciplined Agile is to define roles and organizational structure for the team. This involves establishing the team's composition, roles, responsibilities, and how they will work together. It ensures the team is set up for success by clarifying expectations and structure.

Answer

To handle stakeholder complaints

Answer

To improve technical skills

Answer

To increase team size

Question 7

Which DA process goal is most relevant when preparing to release a product?

Accepted Answer

Produce a Potentially Consumable Solution. 'Produce a Potentially Consumable Solution' is the DA process goal focused on creating a solution that is potentially shippable, which is exactly what you need when preparing to release a product. It covers activities like continuous integration, testing, and building a deployable increment. The other goals address team formation, coordination, and risk, which are not release-preparation focused.

Answer

Form Team

Answer

Coordinate Activities

Answer

Address Risk

Question 8

A team is consistently failing to complete their planned work. According to DA, what is the best first move?

Accepted Answer

Review their planning practices and choose a more appropriate estimation method from the DA toolkit.. DA's first move when a team consistently misses planned work is to examine the planning and estimation decision points in the toolkit and select practices that better fit the team's context — for example, switching from story points to flow-based forecasting, or adjusting the planning cadence. This is guided continuous improvement applied to a planning problem: diagnose, then choose a better-fitting option from the toolkit.

Answer

Extend the sprint length.

Answer

Assign blame to the team members.

Answer

Work weekends to catch up.

Question 9

What is the primary purpose of the 'Disciplined Agile' toolkit?

Accepted Answer

To help teams tailor their WoW. The Disciplined Agile toolkit is designed to help teams tailor their Way of Working (WoW) to fit their unique context. It provides a comprehensive set of process goals, practices, and strategies that teams can mix and match to create a customized approach. The primary purpose is to guide teams in making informed choices rather than prescribing a one-size-fits-all method.

Answer

To automate all documentation

Answer

To force teams to use Scrum

Answer

To replace all project managers

Question 10

Which TWO of the following are ways to 'Improve Process' in DA?

Accepted Answer

Experimenting with new techniques. In the DevOps Agile Skills Association (DASA) DevOps Agile (DA) framework, improving process means continuously refining how work flows through the value stream. Option A, experimenting with new techniques, is correct because DA encourages a culture of continuous experimentation and innovation, letting teams test new practices and adopt those that demonstrably improve flow and outcomes. Option D, conducting retrospectives, is correct because retrospectives are the structured inspect-and-adapt ceremony where teams regularly review their process, identify impediments, and agree on concrete improvements. Option B, increasing management oversight, is not a process improvement technique; added control tends to slow flow and undermine the autonomy and self-organization DA promotes. Option C, ignoring all feedback, is the opposite of improvement since feedback loops are essential to learning and adaptation. Option E, reducing team size, is a staffing change rather than a process improvement and can harm the team's capacity and cross-functionality.

Answer

Increasing management oversight

Answer

Ignoring all feedback

Answer

Reducing team size

Question 11

A team discovers that their cycle time is highly variable. What is the most likely culprit from a Lean perspective?

Accepted Answer

Lack of process standardization.. In Lean thinking, cycle time variability is primarily driven by inconsistent work methods, not by workload size or tooling. Lack of process standardization means each work item may follow a different path, with different handoffs, definitions of done, and decision points, which produces unpredictable durations. Standardized work is a foundational Lean countermeasure because it creates a stable baseline from which variation can be measured and reduced.

Answer

Having a very small backlog.

Answer

The use of an electronic board.

Answer

Too many team members.

Question 12

What is the relationship between Portfolio Management and the Team layer in DA?

Accepted Answer

Portfolio provides direction to teams. In Disciplined Agile, Portfolio Management provides strategic direction to teams by aligning team-level work with organizational goals, funding, and governance. The Portfolio layer sets the context within which teams operate, ensuring that team efforts contribute to the broader enterprise strategy. This relationship is not independent; it is a directional flow from portfolio to teams.

Answer

Teams ignore portfolio management

Answer

They are completely independent

Answer

Teams set the portfolio strategy

Question 13

A team has identified 'task switching' as a primary source of waste. What is the most effective Lean practice to address this?

Accepted Answer

Establish strict WIP limits for each workflow state.. WIP limits directly cap the number of items allowed in each workflow state, which forces the team to finish work before starting new work. This eliminates the multitasking and context-switching overhead that arises when people juggle multiple in-progress items simultaneously. Lean theory (and the Kanban method) treats WIP limits as the primary mechanism for reducing task switching and improving flow.

Answer

Host more frequent brainstorming meetings.

Answer

Assign a dedicated task-manager to monitor progress.

Answer

Rotate team members daily to ensure skill diversity.

Question 14

Why does DA distinguish between 'Process Goals' and 'Practices'?

Accepted Answer

To separate the goal (what) from the technique (how).. DA separates Process Goals (the 'what' — the outcomes a team aims to achieve, such as 'Produce a Potentially Consumable Solution') from Practices (the 'how' — the specific techniques or approaches used to achieve those goals, such as continuous integration or test-driven development). This separation allows teams to choose different practices that all serve the same goal, depending on their context. It reinforces the fit-for-purpose philosophy by keeping the goal stable while allowing the technique to vary.

Answer

To make the toolkit more complicated.

Answer

Because they are the same thing.

Answer

Because only one practice can fulfill a goal.

Question 15

When applying the Lean principle of 'Optimize the Whole', what should you avoid doing?

Accepted Answer

Optimizing a sub-process without considering the impact on the overall value stream.. 'Optimize the Whole' in Lean means focusing on improving the entire value stream end-to-end rather than optimizing individual sub-processes in isolation. The key thing to avoid is local optimization — improving one sub-process without considering its impact on the overall flow, which can actually harm the whole system. For example, speeding up one station may create a bottleneck downstream or increase WIP elsewhere.

Answer

Identifying bottlenecks in the production pipeline.

Answer

Aligning team goals with organizational objectives.

Answer

Analyzing the end-to-end value stream.

Question 16

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

Accepted Answer

Stakeholders collaborating on feature prioritization. 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.

Answer

Stakeholders only reading the final report

Answer

Stakeholders dictating the team's internal coding style

Answer

Stakeholders attending daily stand-up meetings

Question 17

What does 'Kaizen' represent in a Lean context?

Accepted Answer

Continuous, incremental improvement.. Kaizen is the Japanese term for continuous, incremental improvement, a foundational Lean principle where every team member is empowered to identify and eliminate waste in small, ongoing steps rather than waiting for large transformative events. In a Lean context, Kaizen emphasizes steady refinement of processes, people, and products through frequent small changes that accumulate into significant gains over time.

Answer

The elimination of all management roles.

Answer

A sudden, radical organizational overhaul.

Answer

A specific software testing methodology.

Question 18

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

Accepted Answer

It increases the risk of delay and quality issues due to context switching. 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.

Answer

It allows for better utilization of team members

Answer

It is the standard way of working in DAD

Answer

It increases their total output

Question 19

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

Accepted Answer

Ability to adapt to changing business needs.. 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.

Answer

Elimination of all documentation.

Answer

Guaranteed delivery of all original requirements on day one.

Answer

Reduced focus on software quality.

Question 20

You are identifying 'non-value-add' work in your process. What is the most important first step?

Accepted Answer

Create a current-state Value Stream Map.. Before you can eliminate waste, you must visualize the current state to know what is actually happening.

Answer

Hire an outside consultant to audit the process.

Answer

Immediately delete all documentation.

Answer

Interview every team member about their tasks.