SAFe-POPM Free Practice Test

What does a Kanban board demonstrate?

1. A. The cost of delay of each item on the board
2. B. Where a team has too much work-in-process (WIP)
3. C. The accumulated value of a team's work
4. D. A burndown chart of work completed in the Iteration

Correct Answer: B
A Kanban board is a visual tool that helps teams manage the flow of work from start to finish. It shows the steps of the team??s workflow, the work items in each step, and the work-in-process (WIP) limits for each step1. A Kanban board demonstrates where a team has too much work-in-process (WIP), which is the number of work items that are being worked on at any given time. Having too much WIP can cause delays, bottlenecks, and waste in the value stream2. By using a Kanban board, teams can identify and resolve the sources of excessive WIP, and optimize their flow and throughput3.
References:
•SAFe Team Kanban - Scaled Agile Framework
•Applying Kanban in SAFe - Scaled Agile Framework
•What is a Kanban Board, and How Do You Use It? - How-To Geek

What is one strategy for managing complex critical path challenges?

1. A. Adjust work between teams or split Features and Stories
2. B. Distribute work to other teams
3. C. Sequence work to eliminate same Iteration dependencies
4. D. Allocate work between teams based on forecasted capacity

Correct Answer: A
One strategy for managing complex critical path challenges is to adjust work between teams or split Features and Stories. Complex critical path challenges are situations where the delivery of value depends on the completion of multiple interdependent tasks by different teams1. These challenges can cause delays, bottlenecks, and inefficiencies in the value stream. To overcome these challenges, one option is to adjust work between teams or split Features and Stories, so that the dependencies are minimized or eliminated2. This can help improve the flow of work, reduce the risk of integration issues, and increase the flexibility and responsiveness of the teams3.
References:
•Accelerating Flow with SAFe - Scaled Agile Framework
•Managing Dependencies - Scaled Agile Framework

Why is it important to establish a definition of done?

1. A. To create alignment on when Stories are complete
2. B. To create standardized work between all Agile Teams
3. C. To enable Scrum Masters/Team Coaches to enforce quality
4. D. To ensure Features provide the expected business benefits

Correct Answer: A
The definition of done specifies the requirements for completeness of a work product or increment of value1. It is important to establish a clear and consistent definition of done across all Agile Teams to ensure that the work products meet the appropriate quality standards and are ready for integration and delivery23. Without a common definition of done, there may be confusion, rework, delays, and technical debt3.
References:
•What is the Definition of Done (DOD) in SAFe®? - Agilemania
•Built-In Quality - Scaled Agile Framework
•Definition of Done - Scaled Agile Framework

What is a PI Planning input that demonstrates how Product Management plans to accomplish the Vision?

1. A. The business context
2. B. The ART planning board
3. C. The top ten Features
4. D. The Team Backlog

Correct Answer: C
The top ten Features are a PI planning input that demonstrates how Product Management plans to accomplish the Vision. The vision is a description of the future state of the solution under development, reflecting customer and stakeholder needs, as well as the features and capabilities proposed to meet those needs1. The top ten Features are the highest priority features of the ART backlog, which are derived from the vision and roadmap, and provide the most value to the customers and stakeholders2. By presenting the top ten Features to the Agile Release Train (ART) during PI planning, Product Management communicates the main objectives and scope of the upcoming Program Increment (PI), and guides the teams to plan their work accordingly2. The top ten Features also help align the teams and stakeholders to a shared mission and vision, and foster cross-team and cross-ART collaboration2.
References: 1 Vision - Scaled Agile Framework, 2 PI Planning - Scaled Agile Framework

What are the minimum requirements for a Feature?

1. A. Acceptance criteria, data models, and priority
2. B. Name, benefit hypothesis, and acceptance criteria
3. C. Benefit hypothesis, acceptance criteria, and priority
4. D. Non-functional requirements, data models, and architecture

Correct Answer: B
The minimum requirements for a feature are a name, a benefit hypothesis, and acceptance criteria12. A name is a brief and descriptive phrase that summarizes the feature. A benefit hypothesis is a statement that describes the expected outcome and value of the feature for the customer or user. Acceptance criteria are a set of conditions that the feature must satisfy to be accepted by the customer or stakeholder12. Some additional information that might be helpful for you are:
•The other options (A, C, and D) are not the minimum requirements for a feature, but rather additional or optional elements that may be included in the feature definition.
•Data models are representations of the data structures and relationships that the feature requires or affects. Data models are not mandatory for a feature, but they may be useful for complex or data-intensive features3.
•Priority is the relative importance or urgency of a feature compared to other features. Priority is not a requirement for a feature, but it is a factor that influences the feature selection and sequencing4.
•Non-functional requirements (NFRs) are system qualities that guide the design of the solution and often serve as constraints across the relevant backlogs. NFRs are not specific to a feature, but they may affect the feature implementation or testing5.
•Architecture is the design and structure of the system that supports the solution. Architecture is not a requirement for a feature, but it is an enabler that facilitates the feature delivery.