Pass the Scaled Agile Certification SAFe-SGP Questions and answers with ValidTests

Strategic themes are specific, defined business objectives that connect a portfolio to the enterprise’s strategy1. They provide business context for portfolio decision-making and influence the investments in value streams and solutions2. They also serve as inputs to the vision, budget, and backlogs of the portfolio, large solution, and program levels3. Strategic themes help align the portfolio with the mission and goals of the enterprise or government agency.

1: Strategic Themes - Scaled Agile Framework 2: Strategic Themes - Scaled Agile Framework 3: The Influence of Strategic Themes across a Portfolio - Scaled Agile Framework

According to the Decentralize Decision-Making article on the Scaled Agile Framework website, the type of decision that should be decentralized is the one that has a high cost of delay. The article states that “All other decisions should be decentralized. Characteristics of these types of decisions include: Frequent – The problems addressed by decentralized decisions are recurrent and common (e.g., Team and Program Backlog prioritization, real-time Agile Release Train [ART] scoping, response to defects and emerging issues). Time-critical – The cost of delay for these decisions is high, and waiting for approval or consensus would cause significant waste or missed opportunities. Reversible – The consequences of these decisions are not long-lasting or irreversible and can be easily changed or corrected if needed.” Therefore, the correct answer is A, high cost of delay. The other options are not accurate, as they are either irrelevant or better suited for centralized decisions.

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

Two statements that accurately describe the SAFe Implementation Roadmap are:

It reflects success patterns from previous implementations of SAFe. The SAFe Implementation Roadmap is based on the experiences and learnings of hundreds of enterprises that have successfully adopted SAFe1. It captures the common critical moves and best practices that have proven to be effective in implementing SAFe in a reliable and predictable way2.

It provides recommended sequencing of role-based training. The SAFe Implementation Roadmap includes a step for training Lean-Agile change agents, who are the key enablers and coaches of the transformation3. It also suggests the appropriate role-based training for executives, managers, leaders, and teams, as well as the timing and sequence of the training in relation to the launch of the ARTs. The training helps to build the knowledge and skills needed to apply SAFe principles and practices at various levels of the enterprise.

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.

Business epics are large initiatives in SAFe that drive business value and typically cross the organizational boundaries (release trains), time boundaries (Program Increments), or both1. They are solution descriptions for the business that capture the more substantial investments that occur within a portfolio2. Business epics directly deliver business value, while enabler epics are used to advance the Architectural Runway to support upcoming business or technical needs2.

1: Implementation Strategies for Business Epics - Scaled Agile Framework 2: Epic - Scaled Agile Framework

According to the PI Objectives article on the Scaled Agile Framework website, uncommitted objectives are used to identify work that can be variable within the scope of a PI. The article states that “Uncommitted objectives help improve the predictability of delivering business value since they are not included in the team’s commitment or counted against teams in the ART predictability measure. Uncommitted objectives are used to identify work that can be variable within the scope of a PI. The work is planned, but the outcome is simply not certain. Teams can apply uncommitted objectives whenever there is low confidence in meeting the objective, but include in their plan.” Therefore, the correct answer is B, teams have low confidence they can meet the objective, but include in their plan. The other options are not accurate, as they do not reflect the definition of uncommitted objectives.

According to the Apply Cadence, Synchronize with Cross-Domain Planning article on the Scaled Agile Framework website, cadence is the term that describes converting unpredictable events into predictable ones. The article states that “Cadence is the rhythm, or heartbeat, of the Agile Release Train (ART). It provides a steady and predictable pattern for planning, developing, and delivering value. Cadence helps teams manage the variability inherent in product development. By converting unpredictable events into predictable ones, cadence enables fast and reliable decision-making.” Therefore, the correct answer is C, cadence. The other options are not accurate, as they are not the terms that describe converting unpredictable events into predictable ones. Innovation and Planning (IP) Iteration (A) is a special iteration that occurs at the end of every Program Increment (PI) and provides an opportunity for innovation, planning, and system-level integration and testing. Program Increment (PI) Planning (B) is a face-to-face event that serves as the heartbeat of the ART, aligning all the teams on the ART to a shared mission and vision. Backlog refinement (D) is the process of breaking down, estimating, and prioritizing the backlog items.

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 System Demo article on the Scaled Agile Framework website, system demos provide objective evidence of built-in quality and compliance. The article states that “The System Demo is a significant event that provides an integrated view of new Features for the most recent Iteration delivered by all the teams in the Agile Release Train (ART). Each demo gives ART stakeholders an objective measure of progress during a Program Increment (PI). The system demo is part of the inspect and adapt cycle and provides ARTs with the opportunity to assess their current state, adjust, and improve. The system demo also provides feedback on functional and nonfunctional requirements, such as compliance, performance, security, and usability.” Therefore, the correct answer is C, system demos. The other options are not accurate, as they are not the events that provide objective evidence of built-in quality and compliance. PI planning (A) is a face-to-face event that serves as the heartbeat of the ART, aligning all the teams on the ART to a shared mission and vision. Backlog refinement (B) is the process of breaking down, estimating, and prioritizing the backlog items. ART syncs (D) are meetings that facilitate cross-team collaboration and alignment.