What helps visualize work during PI Planning?

1. A. ART PI Kanban Board
2. B. ART Planning Board
3. C. ART PI Risks
4. D. ART PI Objectives

Correct Answer: B
The ART Planning Board is a physical or virtual board that helps visualize the work of the Agile Release Train (ART) during PI Planning. It shows the features and dependencies for each team and iteration in the Program Increment (PI)1. The ART Planning Board helps the teams and stakeholders to see the big picture, identify and resolve issues, and collaborate on the delivery plan2.
References:
•ART Planning Board - Scaled Agile Framework
•PI Planning - Scaled Agile Framework

What is a pattern for splitting Features into Stories?

1. A. Tasks to complete
2. B. Variations in data
3. C. Team skills
4. D. Layers of the technology stack

Correct Answer: B
A pattern for splitting Features into Stories is to use variations in data, which means identifying different types of data that the feature can handle and creating a story for each type. For example, a feature that allows users to upload files can be split into stories for different file formats, sizes, or sources. This way, the stories are independent, testable, and valuable12
References:
• Story – Scaled Agile Framework
• User stories splitting by data variations and interfaces

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

Which Agile Team event supports relentless improvement?

1. A. Inspect and Adapt
2. B. System Demo
3. C. Iteration Retrospective
4. D. Team Sync

Correct Answer: C
The iteration retrospective is an Agile Team event that supports relentless improvement by allowing the team to reflect on the iteration just completed and to derive new ideas to improve the team??s process12. This reflection helps instill the concept of relentless improvement—one of the pillars of the SAFe House of Lean3—in the individuals and the team.
References:
•Iteration Retrospective - Scaled Agile Framework
•SAFe POPM 5 Flashcards | Quizlet
•SAFe Lean-Agile Principles - Scaled Agile Framework

What increases the effectiveness of System Demos?

1. A. Spend a lot of time preparing for the demo
2. B. Limit team attendance to minimize disruptions to the team
3. C. Focus on team-level Metrics
4. D. Consider how and what to demo during Iteration Planning

Correct Answer: D
Considering how and what to demo during Iteration Planning increases the effectiveness of System Demos, which are events that provide an integrated view of new features delivered by the Agile Release Train (ART) in each Iteration12. By thinking ahead of how and what to demo, the teams can:
•Align on the product vision and roadmap and ensure that the work items are aligned with the customer value and the PI objectives12.
•Define clear and testable acceptance criteria for each work item and plan how to verify them in the demo12.
•Identify and resolve any dependencies, risks, or impediments that may affect the demo12.
•Prepare the demo environment and the necessary tools and data to support the demo12.
•Practice the demo and rehearse the script and the roles of the presenters12. Some additional information that might be helpful for you are:
•The other options (A, B, and C) are not actions that increase the effectiveness of System Demos, but rather actions that may reduce it.
•Spending a lot of time preparing for the demo may not be effective, as it may take away time and focus from the actual development and testing of the work items. Instead, the teams should aim for continuous integration and built-in quality practices that enable them to demo the work items as soon as they are done12.
•Limiting team attendance to minimize disruptions to the team may not be effective, as it may reduce the feedback and collaboration opportunities that the demo provides. Instead, the teams should invite and engage all the relevant stakeholders, such as Business Owners, executive sponsors, other Agile Teams, development management, and customers, to the demo12.
•Focusing on team-level metrics may not be effective, as it may not reflect the true value and progress of the integrated work across the ART. Instead, the teams should focus on system-level metrics, such as PI objectives, solution quality, and customer satisfaction, to evaluate the outcome and impact of the demo12.