Explanation 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.
Question 22
During PI Planning, capacity allocation helps an ART to:
Correct Answer: B
The SAFe POPM workbook states that capacity allocation helps balance functionality with Architectural Runway. It also shows allocation categories such as New Features , Enablers , and Tech Debt and Maintenance , and says teams agree on the percentage of capacity devoted to new Feature development versus Enablers, tech debt, and maintenance.
Question 23
Which of the following Agile Manifesto principles aligns with conducting a System Demo?
Correct Answer: D
The System Demo is an event where the Agile Release Train (ART) demonstrates the integrated and working software to the stakeholders and customers1. The System Demo aligns with the Agile Manifesto principle that states: " Working software is the primary measure of progress " 2. This principle emphasizes the value of delivering functional and usable software over comprehensive documentation or adherence to a plan3. The System Demo provides feedback on the quality, usability, and value of the software, as well as the effectiveness of the ART1. References: * System Demo - Scaled Agile Framework * 12 Principles Behind the Agile Manifesto | Agile Alliance * Manifesto for Agile Software Development
Question 24
What increases the effectiveness of System Demos?
Correct Answer: D
Explanation 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.
Question 25
Communicating and refining the Vision to the Agile Release Train during PI Planning supports which SAFe Core Value?
Correct Answer: B
Communicating and refining the Vision to the Agile Release Train (ART) during PI Planning supports the SAFe Core Value of Alignment. Alignment is one of the four core values of SAFe that guides the behaviors and actions of the people who work under the framework1. Alignment means that everyone understands the strategic direction, the value streams, and the solution intent, and how their role and work contribute to them2. PI Planning is a crucial event in SAFe where all the teams within the ART come together to plan their work for the upcoming Program Increment (PI)3. During PI Planning, the Product Management presents the Vision, which describes the future state of the solution and its features4. The Vision helps align the teams and stakeholders to a shared mission and goal, and provides the context and purpose for the PI objectives. References: * SAFe Core Values - Scaled Agile Framework * Alignment - Scaled Agile Framework * PI Planning - Scaled Agile Framework * Vision - Scaled Agile Framework
