Free Scaled Agile SAFe 5 Government Practitioner Exam (5.0) SAFe-SGP Exam Questions

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.

According to theApplying Lean Estimating and Forecasting in Cadencearticle on the Scaled Agile Framework website, ART velocities are used to conduct 'what if' analysis for estimating and forecasting in SAFe. The article states that ''The ART velocity is used to conduct 'what if' analysis, which helps determine the feasibility of the plan and the number of features that can be delivered in a PI. The ART velocity is also used to forecast the delivery of features and capabilities beyond the current PI.'' Therefore, the correct answer is C, ART velocities are used to conduct 'what if' analysis. The other options are not accurate, as they are not the statements that are true for estimating and forecasting in SAFe. Feature estimation is not independent of team-level input (A), as teams are involved in estimating the size and complexity of features using story points or normalized story points. Epics are not estimated by the Epic Owner (B), as they are estimated collaboratively by the Epic Owner, Enterprise Architect, and Lean Portfolio Management. Work breakdown structure to the task level does not help increase estimation accuracy (D), as it introduces unnecessary overhead and delays feedback.

One way that Lean-Agile leaders can exemplify the SAFe Core Value of alignment is by participating in backlog visibility, review, and preparation1. This means that leaders are actively involved in understanding and prioritizing the work items that deliver value to the customers and stakeholders. They also provide feedback and guidance to the teams and trains that execute the work.By participating in backlog management, leaders can ensure that the work is aligned with the vision, mission, and strategy of the enterprise or government agency2.

1:The Evolving Role of Managers in Lean-Agile Development - Scaled Agile Framework2:Core Values - Scaled Agile Framework

According to theImplementation Roadmaparticle on the Scaled Agile Framework website, organizations begin realizing better results when following the Implementation Roadmap as soon as the first Program Increment (PI). The article states that ''The first PI is a critical milestone. It's the first time the new ART delivers a fully integrated and tested increment of value. It's also the first time the ART demonstrates its new way of working to the enterprise and its stakeholders. The first PI is a big deal. It's a celebration of the new culture and the new way of working. It's also the first time the enterprise can see the benefits of the new approach.'' Therefore, the correct answer is B, as soon as the first Program Increment. The other options are not accurate, as the roadmap consists of more than just steps, training, or metrics. It is a continuous journey of learning and improvement.

One benefit of Program Increment (PI) Planning is that it builds the social network on which the Agile Release Train (ART) depends1.PI planning is a face-to-face event that establishes communication and collaboration among all team members and stakeholders2.It fosters a sense of shared mission and vision, trust and respect, and collective ownership and accountability3.It also helps to create a culture of learning and innovation within the ART4.

1:PI Planning - Scaled Agile Framework2:The Ultimate Guide to PI Planning [2023 SAFe Edition] - Easy Agile3:Program Increment (PI) is the Heart of Scaled Agile Framework (SAFe)4:PI Planning - Scaled Agile Framework

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