How feedback is connected with optimum batch size?
Answer(s): B
The economically optimal batch size depends on both the holding cost (the cost for delayed feedback, inventory decay, and delayed value delivery) and the transaction cost (the cost of preparing and implementing the batch). To improve the economics of handling smaller batches—and thus increase throughput—teams must focus on reducing the transaction costs of any batch. This typically involves increasing the attention to and investment in infrastructure and automation, including things such as continuous integration, automating the build environment, automated regression testing and more. (This is a primary purpose of implementing DevOps.)
What is defining the best the Program Vision?
Answer(s): D
When using Full SAFe or Large Solution SAFe, each ART will likely have its own vision, detailing the direction of the specific capabilities or subsystems that it produces. This vision should be tightly coupled to the solution vision it supports.
What kind of items is describing behaviors in the Large Solution view?
Answer(s): A
Large Solution SAFe describes additional roles, practices, and guidance to build and evolve the world’s largest applications, networks, and cyber-physical systems. Large Solution SAFe (Figure 1) configuration includes the following constructs: The Essential SAFe configuration An additional competency, Enterprise Solution Delivery that describes how to apply Lean-Agile principles and practices to the specification, development, deployment, operation, and evolution of the world’s largest and most sophisticated software applications, networks, and cyber-physical systems. The large solution level roles, artifacts, and events The full spanning palette A connection to the Enterprise or Government entity the solution supports The following Large Solution SAFe artifacts help coordinate multiple ARTs and suppliers: Capabilities – Capabilities are a higher-level solution behavior that typically spans multiple ARTs. They are sized and split into multiple features so that they can be implemented in a single PI. Enabler Capabilities– Enabler capabilities support the activities needed to extend the Architectural Runway to provide future business functionality and include exploration, architecture, infrastructure, and compliance. Solution Epics – Solution Epics are epics implemented by a single Solution Train. Nonfunctional Requirements (NFRs) – NFRs define system attributes such as security, reliability, performance, maintainability, scalability, and usability. These are incorporated in solution intent. Solution Backlog – Solution Backlog is the holding area for upcoming capabilities and enablers, each of which can span multiple ARTs and are intended to advance the solution and build its architectural runway.
What are the three pillars of Scrum: transparency, inspection ...?
Scrum pillars are Transparency, Inspection and Adaptation.
Post your Comments and Discuss Scaled Agile SAFe-Agilist exam with other Community members:
DA commented on October 30, 2024 Very good and help a lot for practice INDIA upvote
Prasun Adhikary commented on September 07, 2024 This is a cool practice test! Anonymous upvote
Our website is free, but we have to fight against bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the SAFe-Agilist content, but please register or login to continue.