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 is one step when determining initial team capacity during PI Planning?

1. A. Add together all of the points from recently completed Features
2. B. Compare final team capacity across all teams
3. C. Ensure Product Owner/Product Manager approval for all time-based capacity adjustments
4. D. Subtract one point for every team member's vacation day, public holiday, or training day

Correct Answer: D
One step when determining initial team capacity during PI Planning is to subtract one point for every team member??s vacation day, public holiday, or training day. This step helps the team to adjust their capacity based on the actual availability of each team member for the upcoming Program Increment (PI)1. By accounting for the time-based capacity adjustments, the team can plan their work more realistically and avoid overcommitting or underdelivering2.
References:
•PI Planning - Scaled Agile Framework
•How to Improve Your Agile Team??s Capacity Planning - Method

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

Why is the problem-solving workshop more effective than traditional lessons learned documents?

1. A. Collaboration over documentation is a key recommendation of the Agile Manifesto
2. B. It makes improvements actionable through backlog items for the next PI
3. C. It involves a small group of leaders
4. D. Workshops are more engaging than document writing

Correct Answer: B
The problem-solving workshop is more effective than traditional lessons learned documents because it makes improvements actionable through backlog items for the next Program Increment (PI). A problem-solving workshop is a structured approach to identify and solve problems that affect the performance and quality of the Agile Release Train (ART) or Solution Train1. Unlike traditional lessons learned documents, which are often passive and rarely implemented, a problem-solving workshop results in a set of improvement backlog items that are prioritized and planned for the next PI2. This way, the teams can implement the improvements and measure their impact on the value delivery3.
References:
•Inspect and Adapt - Scaled Agile Framework
•Why is the problem-solving workshop more effective than traditional ??
•Problem-solving workshop: Step-by-Step - Agilephoria

Why do Agile Teams use Iteration Goals?

1. A. To summarize the business outcomes an Agile Team intends to achieve during the PI
2. B. To ensure the team accomplishes the committed Stories for each Iteration
3. C. To align the team members and the Product Owner to a common purpose
4. D. To hold the team accountable to their PI Objectives

Correct Answer: C
Iteration Goals are a high-level summary of the business and technical goals that an Agile Team agrees to accomplish in an Iteration. They are vital to coordinating an Agile Release Train (ART) as a self-organizing, self-managing team of teams1. Iteration Goals help the team and the Product Owner to reach agreement on the business value they intend to deliver, align their work to their team PI objectives, and ground everyone on their shared purpose2.
References:
•Iteration Goals - Scaled Agile Framework
•What Is The Purpose Of Iteration Goals? - GoRetro