SAFe-SGP SAFe 5 Government Practitioner Exam (5.0) Questions and Answers

According to the Applying Lean Estimating and Forecasting in Cadence article 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.

According to the Implementation Roadmap article 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.

According to the Government Article on the Scaled Agile Framework website, using firm fixed price contracts may significantly affect lead time for systems development. The article states that “Firm fixed price (FFP) contracts are often used in government programs, but they are not well suited for Agile development. FFP contracts typically require detailed specifications and fixed scope, which are incompatible with the iterative and adaptive nature of Agile. FFP contracts also create a misalignment of incentives between the contractor and the government, as they reward the contractor for delivering the minimum acceptable solution, rather than the best possible value. FFP contracts also discourage collaboration and feedback, as any change in scope or requirements may trigger lengthy negotiations and contract modifications.” Therefore, the correct answer is A, using firm fixed price contracts. The other options are not accurate, as they are not the types of decisions that may significantly affect lead time for systems development. Using relative size estimating (B) is a common Agile practice that helps teams plan and track their work. Approved budget, required development tools, and dedicated team members © are enablers, not impediments, of systems development. Prioritizing the product backlog using WSJF (D) is a method of applying an economic view to optimize value delivery.

According to the Core Values article on the Scaled Agile Framework website, the three items that are part of SAFe’s Core Values are alignment, relentless improvement, and transparency. The article states that “The four Core Values of alignment, transparency, respect for people, and relentless improvement represent the foundational beliefs that are key to SAFe’s effectiveness. These tenets help guide the behaviors and actions of everyone participating in a SAFe portfolio.” Therefore, the correct answers are A, alignment, B, relentless improvement, and F, transparency. The other options are not accurate, as they are not the core values of SAFe. Decentralized decision-making is a principle, not a value, of SAFe. Program execution is an outcome, not a value, of SAFe. Assume variability is not a term used in SAFe.

Taking an economic view is the SAFe principle that ensures the maximum benefit is generated by understanding trade-offs between risks, cost of delay, operational costs, and development costs for each program and value stream1. This principle requires a fundamental understanding of the economics of building systems and making decisions in a proper economic context. This includes the strategy for incremental value delivery and the broader economic framework for each value stream2. Taking an economic view helps to optimize the flow of value, reduce waste, and deliver solutions that meet customer and stakeholder needs3.

1: SAFe Lean-Agile Principles - Scaled Agile Framework 2: Principle #1 – Take an economic view - Scaled Agile Framework 3: Adopting Lean Budgeting Aligned to Development Value Streams

 According to the System Demo article on the Scaled Agile Framework website, objective milestones, like the System Demo, are useful because they provide tangible evidence of progress and allow for cost-effective adjustments towards an optimum solution. The article states that “The system demo offers the ART a fact-based measure of current, system-level progress within the PI. It’s the true measure of ART velocity and progress. Achieving this requires implementing the scalable engineering practices necessary to support Continuous Integration across the ART.” The article also states that “The system demo provides the opportunity to get fast feedback from the stakeholders, which is essential for building the right solution. The feedback can be used to validate assumptions, evaluate hypotheses, and identify potential pivots or changes in direction. The system demo also helps to identify and resolve any integration issues, dependencies, or risks that may affect the solution’s fitness for purpose or compliance.” Therefore, the correct answers are D, they provide tangible evidence of progress, and E, they allow for cost-effective adjustments towards an optimum solution. The other options are not accurate, as they are not the reasons why objective milestones are useful. They do not necessarily allow the contracting officer to release funds for payment, satisfy phase-gate governance processes, or satisfy a SAFe requirement.

According to the SAFe® for Government course, strategic themes assist with epic evaluation and decision-making. Strategic themes are specific, itemized business objectives that connect a portfolio to the enterprise’s business strategy1. They provide guidance for the portfolio vision, budget allocation, and the prioritization of epics1. Strategic themes help to align the portfolio with the enterprise’s mission and vision, and to ensure that the epics deliver the most value to the customers and stakeholders1.

Strategic themes are specific business objectives that connect a portfolio to the enterprise strategy. They provide guidance for the portfolio vision, budget allocation, and metric selection. They also assist with epic evaluation and decision-making by providing a context for assessing the value and alignment of epics12

1: [Strategic Themes - Scaled Agile Framework] 2: Epic - Scaled Agile Framework

According to the Build Incrementally with Fast, Integrated Learning Cycles article 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.

According to the PI Planning article on the Scaled Agile Framework website, confidence votes are taken at the program and team levels once dependencies and program risks are addressed. The article states that “After discussing plans and dependencies, each team member casts a vote, usually on a scale of 1 to 5. This collective feedback helps identify potential risks, enabling teams to address concerns and enhance their overall chances of success.” The article also states that “The RTE then facilitates a program-level confidence vote, where the Business Owners and other stakeholders assess the feasibility and economic outcomes of the plan.” Therefore, the correct answer is D, program and team. The other options are not accurate, as they are not the levels at which confidence votes are taken. Portfolio, branch, and train are not relevant terms in the context of PI planning.

The true statement about Lean-Agile development and contracting is A. Quality is built-in through collaboration and automation. Lean-Agile development is an iterative and incremental approach to software development that emphasizes flexibility, adaptability, and continuous improvement. Quality is not something that is added at the end of the development cycle, but rather something that is embedded throughout the process. Lean-Agile teams collaborate with customers and stakeholders to define clear and testable acceptance criteria for each work item. They also use automation tools to perform frequent testing, integration, and deployment of the software, ensuring that the solution meets the quality standards and compliance requirements12.

1: Advanced Topic - Agile Contracts - Scaled Agile Framework 2: Government - Building in Quality and Compliance - Scaled Agile Framework