According to theBuild Incrementally with Fast, Integrated Learning Cyclesarticle on the Scaled Agile Framework website, convergence of requirements with designs reduces the cone of uncertainty. The article states that ''The cone of uncertainty describes the uncertainty and risk in estimates at different phases of development. The cone narrows as the project progresses, reflecting the fact that there is less uncertainty and risk as more is learned about the requirements and design of the system. The goal is to reduce the cone of uncertainty as quickly as possible by converging on the requirements and design through fast feedback and learning cycles.'' Therefore, the correct answer is A, convergence of requirements with designs. The other options are not accurate, as they are not the terms that describe reducing the cone of uncertainty. Convergence of alternatives with flexible specifications (B), convergence of architectures with design sets , and convergence of flexible specifications with design sets (D) are not concepts that are used in the Scaled Agile Framework.
Question 2
Which role in SAFe has content authority over the Agile Team's backlog?
Answer : B
According to theEssential SAFearticle on the Scaled Agile Framework website, the Product Owner (PO) is the role in SAFe that has content authority over the Agile Team's backlog. The article states that ''The Product Owner (PO) is the content authority for the team backlog. The PO is responsible for defining stories and prioritizing the backlog.'' Therefore, the correct answer is B, Product Owner. The other options are not accurate, as they are not the roles that have content authority over the Agile Team's backlog. The Release Train Engineer (A) is the servant leader and chief Scrum Master for the Agile Release Train (ART). The Product Management is the content authority for the program backlog. The Agile Team (D) is the cross-functional group of developers, testers, and other specialists that deliver value in an iteration.
Question 3
What is the appropriate Lean action to take once all of the expected value of an Epic has been delivered, even if all of the planned Features have not been completed?
Answer : A
The appropriate Lean action to take once all of the expected value of an Epic has been delivered, even if all of the planned Features have not been completed, is to close the Epic1. This means that the Epic Owner declares that the epic is done and no further work is required. Closing the epic frees up the resources and budget that were allocated to it, and allows the teams to focus on other value streams and initiatives.Closing the epic also enables the Epic Owner to measure the actual outcomes and benefits of the epic, and compare them with the expected ones in the Lean business case2. Closing the epic does not mean that the solution is fixed and cannot be changed or improved later.It simply means that the current hypothesis of the epic has been validated or invalidated, and that further work can be initiated as new epics or features if needed3.
According to theGovernment Articleon the Scaled Agile Framework website, governance in a SAFe context is a framework for decision-making to ensure programs achieve desired mission outcomes. The article states that ''Governance is not the natural enemy of the lean flow of value in technology development. In fact, governance plays a vital role in many high-assurance systems where the economic and human cost of failure is unacceptable. It is merely a framework for decision-making and oversight to ensure that programs achieve the desired mission outcomes.'' Therefore, the correct answer is B, a framework for decision-making to ensure programs achieve desired mission outcomes. The other options are not accurate, as they are not the definitions of governance in a SAFe context. Oversight that is provided by the PMO (A) is not governance, but a function that supports governance by providing guidance and coordination. Agency level regulations that ensure compliance with federal laws are not governance, but a set of rules that programs must follow. Participatory budgeting events conducted twice annually by LPM (D) are not governance, but a mechanism for allocating funds based on value and strategic alignment.
Question 5
In a SAFe Roadmap, which PIs are committed?
Answer : A
According to theRoadmaparticle on the Scaled Agile Framework website, in a SAFe Roadmap, only the first PI is committed. The article states that ''The committed PI shows the results of the teams' most recent PI Planning event where they committed to event the program's PI Objectives. The forecast may provide the deliverables and milestones for the following two PIs.'' Therefore, the correct answer is A, the first one. The other options are not accurate, as they imply that more than one PI is committed, which is not the case. The roadmap is a forecast, not a guarantee, of future PIs.
Question 6
In addition to Program Increment (PI) Objectives and uncommitted objectives, what also must be identified during PI Planning?
Answer : B
In addition to PI objectives and uncommitted objectives, program risks must also be identified during PI planning1.Program risks are the uncertainties or impediments that may affect the ART's ability to deliver value in the PI2. Identifying and managing program risks is a collaborative activity that involves all the teams and stakeholders in the ART.The program risks are captured in the program risks board, which is a visual tool that helps prioritize and track the resolution of the risks3.
What is the Manifesto for Agile Software Development?
Answer : B
The Manifesto for Agile Software Development, also known as the Agile Manifesto, is a shared set of values and principles intended to improve software development1. The Agile Manifesto was created in 2001 by a group of 17 software practitioners who wanted to find a better way of developing software than the traditional, documentation-driven, and heavyweight processes.The Agile Manifesto states four values and twelve principles that guide the agile approach to software development, which emphasizes individuals and interactions, working software, customer collaboration, and responding to change2.The Agile Manifesto is not a specific methodology or practice, but rather a philosophy that can be applied to various agile frameworks, such as Scrum, Kanban, XP, and SAFe3.
1:Manifesto for Agile Software Development2:What is the Agile Manifesto? | Agile Principles and Values - ProductPlan3:The Agile Manifesto - Project Management Institute
All Official Question Types