SAFe-Agilist Product Development Flow Practice Test 4 — 15 Questions

Question 1

Which practice helps a SAFe ART address high variability in arrival rates?

Accepted Answer

Using capacity buffers to manage surges in work demand.. High variability in the arrival of work can cause unpredictable surges, leading to queue buildup. Using buffers (such as an uncommitted portion of the PI plan or a 'ready' backlog) allows the team to absorb this variability without disrupting the flow. This ensures that the team maintains a steady pace, which is critical for predictability and for maintaining the integrity of the planned delivery commitments.

Answer

Eliminating all planning and working on items as they arrive.

Answer

Requiring all stakeholders to submit requests six months in advance.

Answer

Increasing the size of every team on the train.

Question 2

Why does high utilization in a SAFe environment often lead to decreased performance?

Accepted Answer

Because it eliminates the buffer needed to handle variability.. High utilization (near 100%) eliminates the system's ability to handle variability. When every resource is fully occupied, any minor delay or new priority causes an immediate queue buildup, as there is no slack time to absorb the variance. This leads to longer lead times, increased multitasking, and a decrease in overall system throughput. Maintaining some level of slack is essential for a high-performing, flexible system.

Answer

Because it makes it difficult for managers to track team progress.

Answer

Because teams are more likely to work on the wrong features.

Answer

Because it discourages teams from using automated tools.

Question 3

Which TWO of the following are benefits of decentralized decision-making in the context of flow? (Select exactly two)

Accepted Answer

Improved responsiveness by reducing wait times for approvals.. Decentralized decision-making is essential for keeping work moving without waiting for approvals from higher levels of management. By empowering those closest to the work to make routine decisions, the organization significantly reduces wait times and improves the speed of feedback. This approach promotes a more responsive and agile culture, where teams can adapt quickly to challenges without being held back by a slow, centralized hierarchy.

Answer

Consistency in company-wide branding and strategy.

Answer

Lowering the salary costs of technical staff.

Answer

Elimination of the need for any management or leadership.

Question 4

Which TWO of the following are primary benefits of visualizing the flow of work using a Kanban board in a SAFe environment?

Accepted Answer

It highlights bottlenecks in the development process.. Visualizing work is a core pillar of Lean-Agile flow. By using a Kanban board, the ART can explicitly see the state of all work items, which makes bottlenecks immediately apparent. This transparency facilitates better communication, enables teams to manage work-in-progress limits effectively, and ensures that everyone has a shared understanding of where value is currently stalled or progressing, leading to more proactive problem-solving and improved delivery predictability.

Answer

It eliminates the need for daily stand-up meetings.

Answer

It automatically adjusts the capacity of the team.

Answer

It forces developers to work faster to clear the board.

Question 5

Which concept best describes the practice of organizing development work into smaller, manageable increments to reduce risk and accelerate feedback?

Accepted Answer

Small batch sizes.. Small batch sizes are fundamental to Product Development Flow because they reduce the amount of work in progress, which minimizes the probability of errors, makes defects easier to isolate, and provides faster feedback loops. By working in small increments, teams can validate assumptions earlier, adjust their approach based on real-world data, and deliver customer value incrementally, which significantly lowers the overall project risk and increases the ability to pivot when necessary.

Answer

Resource utilization maximization.

Answer

Large-scale batch processing.

Answer

Waterfall planning cycles.

Question 6

Which THREE factors contribute to the 'Cost of Delay' in the WSJF prioritization model?

Accepted Answer

User-business value.. Cost of Delay is a multi-dimensional metric. It combines user-value, which represents the benefit to the customer, time-criticality, which accounts for external deadlines or market windows, and risk reduction/opportunity enablement, which considers the future value of the feature. By analyzing these components, teams can make objective decisions about which features provide the highest economic benefit if delivered immediately, ensuring alignment between development efforts and the business's most urgent priorities.

Answer

Team velocity.

Answer

Developer salary costs.

Question 7

What is the primary purpose of implementing Work-in-Process (WIP) limits in a flow-based system?

Accepted Answer

To prevent context switching and improve cycle time.. WIP limits are designed to prevent overloading the system, which causes context switching, delays, and poor quality. By capping the amount of work allowed in any given state, the team is forced to finish existing tasks before starting new ones. This discipline creates a 'pull' system that smooths out workflow, exposes hidden bottlenecks, and results in faster overall cycle times, ensuring the team stays focused on delivering value continuously rather than juggling multiple incomplete items.

Answer

To reduce the amount of technical debt.

Answer

To increase the number of features delivered per sprint.

Answer

To automatically prioritize the most valuable features.

Question 8

Refer to the exhibit. Based on the provided metrics, what is the most significant indicator of a flow efficiency problem?

Accepted Answer

The large queue size of 12 features.. The large queue size relative to team velocity suggests that features are waiting significantly longer than they are being worked on. In a flow-based system, excessive queue sizes are the primary indicator that the system is 'stalled.' This waiting period represents a massive cost of delay and indicates that the team is failing to maintain a smooth, continuous flow of value, requiring an immediate reduction in active WIP to clear the backlog.

Answer

High team velocity.

Answer

Average feature duration of 2 weeks.

Answer

The iteration length is too short.

Question 9

In the context of SAFe, what does 'Shift Left' mean in relation to testing and quality?

Accepted Answer

Integrating testing earlier in the development lifecycle.. Shifting left means moving testing and quality activities earlier in the development process, ideally starting as soon as coding begins or even during the design phase. This approach ensures that defects are found and fixed immediately when they are cheapest to resolve. It prevents the accumulation of technical debt and long 'testing' phases at the end of a cycle, which are major obstacles to maintaining a continuous and predictable flow of value.

Answer

Moving testing to the very end of the PI.

Answer

Reducing the amount of automated testing.

Answer

Only testing the most critical features.

Question 10

Which of the following is a key characteristic of a 'Pull' system in Lean product development?

Accepted Answer

Starting new tasks based on capacity availability.. A pull system is characterized by work being started only when there is available capacity, rather than being pushed onto the team based on arbitrary schedules. This ensures that the team is not overwhelmed and that work is completed before new tasks are initiated. It is critical for maintaining stable flow and ensuring that the most important items move through the system as quickly as possible without getting stuck in congested queues.

Answer

Pushing work to the team based on a master schedule.

Answer

Prioritizing tasks based on the longest duration.

Answer

Maintaining 100% utilization at all times.

Question 11

Why is 'Multitasking' considered a major enemy of flow in a SAFe ART?

Accepted Answer

It increases the cost of context switching.. Multitasking introduces significant context-switching costs, where the team loses time and focus whenever they shift between different tasks. This reduces overall productivity, increases the likelihood of errors, and extends the lead time for all items being worked on. In a flow-based system, it is much more efficient to focus on completing a single item before beginning another, as this ensures rapid progress and minimizes the time that work sits idle in a partially finished state.

Answer

It decreases the visibility of the work.

Answer

It makes it harder to track team velocity.

Answer

It forces developers to learn more skills.

Question 12

A Release Train Engineer (RTE) notices that the ART consistently meets its PI Objectives, yet stakeholders complain about long delays between feature ideation and delivery. The RTE reviews the Value Stream and finds that features frequently wait in a 'ready' queue for weeks before development begins, even though teams are not fully utilized. Which action best addresses this situation according to SAFe's Product Development Flow principles?

Accepted Answer

Apply WIP limits to the 'ready' queue and pull features into development only when capacity is available.. The scenario describes a classic queueing problem: excessive WIP in the 'ready' state causing long lead times despite teams not being fully utilized. SAFe's Product Development Flow principle advocates limiting WIP and using a pull system to match demand with capacity. Applying WIP limits to the ready queue reduces the number of items waiting, thereby shortening wait times and improving overall flow efficiency.

Answer

Implement a new tool to track features more accurately in the ready queue.

Answer

Ask teams to work overtime to clear the ready queue faster.

Answer

Increase the number of features in the Program Backlog to keep teams busy and reduce idle time.

Question 13

A SAFe Agile Release Train (ART) is experiencing high variability in the arrival of new features, leading to uneven flow and frequent context switching. The RTE wants to apply Product Development Flow principles to stabilize the system. Which TWO actions should the RTE take? (Choose two.)

Accepted Answer

Use a Kanban board to visualize the workflow and explicitly manage queue sizes.. High variability in feature arrival disrupts flow. SAFe recommends implementing a pull system with WIP limits to cap work in process and using a Kanban board to visualize and manage queues. These practices reduce context switching, prevent overload, and create a more predictable flow. They directly address the root cause of uneven flow by controlling the amount of work entering the system and making bottlenecks visible.

Answer

Increase the batch size of features to reduce the number of handoffs.

Answer

Eliminate all buffers and slack time to maximize utilization.

Answer

Mandate that all teams work on the same feature simultaneously to synchronize delivery.

Question 14

A Release Train Engineer notices that a feature has been in the program backlog for 12 weeks but only 3 weeks of actual work was performed on it. The rest of the time it sat in various queues. Which SAFe flow metric best highlights this issue?

Accepted Answer

Flow efficiency. Flow efficiency is the SAFe metric that compares active work time to total lead time. With only 3 weeks of active work out of 12 weeks total, the flow efficiency is 25 percent, revealing that most of the delay is due to waiting in queues. This metric helps teams target queue reduction and improve overall flow.

Answer

Flow load

Answer

Flow velocity

Answer

Flow distribution

Question 15

A Scrum Master on a SAFe Agile Team notices that the team often starts new user stories before finishing current ones, leading to a large number of partially completed stories at the end of the Sprint. Which SAFe principle for Product Development Flow does this behavior violate?

Accepted Answer

Visualize and limit WIP, reduce batch sizes, and manage queue lengths.. The team's behavior of starting new stories before finishing current ones is a classic WIP violation. SAFe's flow principle explicitly states to visualize and limit WIP, reduce batch sizes, and manage queue lengths. By limiting WIP, the team would finish work before starting new items, reducing partially completed stories and improving flow. This principle is foundational to achieving predictable delivery.

Answer

Decentralize decision-making.

Answer

Apply systems thinking.

Answer

Assume variability; preserve options.