What are the minimum requirements for a Feature?
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.
What helps visualize work during PI Planning?
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.
* ART Planning Board - Scaled Agile Framework
* PI Planning - Scaled Agile Framework
What is one input to the Vision?
One input to the Vision is customer feedback. Customer feedback is the information and opinions that customers and stakeholders provide about the solution, its features, and its value proposition1. Customer feedback helps to validate the assumptions, test the hypotheses, and measure the satisfaction of the solution2. Customer feedback also helps to identify the needs, preferences, and expectations of the customers and stakeholders, which are essential for defining and communicating the Vision3. The Vision is a description of the future state of the solution under development, and it reflects the problem(s) that the solution will solve and the benefits that it will deliver4.
* Customer Feedback - Scaled Agile Framework
* Continuous Exploration - Scaled Agile Framework
* Solution Vision - Scaled Agile Framework
* Vision - Scaled Agile Framework
What system delivers a product or service to a Customer?
An Operational Value Stream (OVS) is the sequence of activities needed to deliver a product or service to a customer1. Examples include manufacturing a product, fulfilling an order, admitting and treating a medical patient, providing a loan, or delivering a professional service1. An OVS is the system that delivers value to the customer and generates revenue for the enterprise2. In SAFe, OVSs are the primary focus of the Customer Centricity competency, which aims to understand and meet the needs and expectations of the customer3.
Some additional information that might be helpful for you are:
* The other options (A, C, and D) are not systems that deliver a product or service to a customer, but rather systems or concepts that support or enable the delivery of value.
* A Kanban System is a method of visualizing and managing the flow of work in a value stream4. A Kanban System can be applied to any type of value stream, whether operational or developmental, to improve efficiency, quality, and predictability4.
* A Development Value Stream (DVS) is the sequence of activities needed to convert a business hypothesis into a digitally-enabled solution that delivers customer value. A DVS is the system that develops and supports the solutions used by the OVSs. In SAFe, DVSs are the primary focus of the Agile Product Delivery competency, which aims to continuously explore, integrate, deploy, and release value.
* A Dual Operating System is a concept proposed by John Kotter that describes the need for organizations to balance the traditional hierarchical structure with a more agile and networked structure. A Dual Operating System enables organizations to exploit their existing capabilities while exploring new opportunities for innovation and growth. In SAFe, a Dual Operating System is achieved by applying the Lean-Agile Leadership competency, which fosters a culture of learning and empowerment.
Which of the following Agile Manifesto principles aligns with conducting a System Demo?
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.
* System Demo - Scaled Agile Framework
* 12 Principles Behind the Agile Manifesto | Agile Alliance
* Manifesto for Agile Software Development
