Free Scaled Agile SAFe-SGP Practice Exam with Questions & Answers

According to the Government Article on 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.

Authenticity is the aspect of leading by example that challenges Lean-Agile leaders to ‘walk the talk’ by being a role model of desired professional and ethical behaviors by acting with honesty, integrity, and transparency1. Authentic leaders are genuine, self-aware, and trustworthy. They align their actions with their words and values, and they inspire trust and respect from others2. Authenticity helps leaders create a culture of openness, collaboration, and continuous learning in their organizations3.

1: Lean-Agile Leadership - Scaled Agile Framework 2: What Is One Way Lean-agile Leaders Lead by Example? - CGAA 3: Three Dimensions of Lean-Agile Leadership: A Guide for Leading Your …

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 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

Governance is a framework for decision-making and oversight to ensure that programs achieve the desired mission outcomes1. It is not merely a set of constraints or compliance requirements, but a way to align the program vision, strategy, and execution with the agency goals and values2. Governance helps to ensure that the solutions delivered by the program are fit for purpose, meet the user needs, and provide value to the public3.

1: Government - Adapting Governance Practices to Support Agility and Lean Flow of Value - Scaled Agile Framework 2: Government - Scaled Agile Framework 3: Agile Government and Agile Governance: We Need both

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 Adapting Governance Practices to Support Agility and Lean Flow of Value article on the Scaled Agile Framework website, the Incremental Capability Review is an objective-based progress review that replaces the traditional phase-gate reviews. The article states that “The Incremental Capability Review (ICR) is a new governance practice that provides a more effective way to measure progress and manage risk. It is based on the principle of objective evidence of working systems rather than subjective opinions and documentation. The ICR is a lightweight, collaborative, and transparent review process that aligns with the PI cadence and events. It leverages the System Demo, Inspect and Adapt, and PI Planning to provide frequent and incremental checks of the solution’s fitness for purpose and compliance with relevant standards and regulations.” Therefore, the correct answer is A, it is an objective-based progress review. The other options are not accurate, as the ICR is not the default for phase-gate reviews, it is not a document-based progress measure, and it does not ensure manual review of processes.

According to the Scrum Master article on the Scaled Agile Framework website, the Scrum Master should talk to the Product Owner, compare the new work to existing backlog priorities, and negotiate a sustainable solution when the Product Owner raises a red flag stating there is an additional requirement that needs to be added to the current Iteration. The article states that “The Scrum Master helps the Product Owner manage the backlog effectively by facilitating backlog refinement and prioritization. The Scrum Master also helps the Product Owner understand and apply the concepts of WSJF, MVP, MMF, and other economic prioritization methods. The Scrum Master supports the Product Owner in negotiating with stakeholders, customers, and the team to ensure that the backlog items are clear, concise, and ready for implementation.” Therefore, the correct answer is B, talk to the Product Owner, compare the new work to existing backlog priorities, and negotiate a sustainable solution. The other options are not accurate, as they do not follow the Scrum principles of self-organization, time-boxing, and delivering value. Meeting with the team and accepting the work if they agree to work overtime (A) would violate the team’s autonomy and sustainability. Accepting the work and extending the Iteration © would disrupt the cadence and synchronization of the team and the ART. Refusing the new requirement (D) would ignore the feedback and collaboration of the Product Owner and the stakeholders.

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.