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

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

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.

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 Development 2: What is the Agile Manifesto? | Agile Principles and Values - ProductPlan 3: The Agile Manifesto - Project Management Institute

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 5 for Lean Enterprises article on the Scaled Agile Framework website, the three configurations of SAFe 5.0 are Essential SAFe, Portfolio SAFe, and Full SAFe. The article states that “SAFe 5 for Lean Enterprises is a knowledge base of proven, integrated principles, practices, and competencies for Lean, Agile, and DevOps. It’s configurable and scalable for a single team, a large program, a portfolio, or an entire enterprise. SAFe 5 for Lean Enterprises is available in three configurations: Essential SAFe, Portfolio SAFe, and Full SAFe.” Therefore, the correct answers are A, Essential SAFe, B, Portfolio SAFe, and E, Full SAFe. The other options are not accurate, as they are not the configurations of SAFe 5.0. Team SAFe © is not a configuration, but a level within the Essential SAFe configuration. Multi-train SAFe (D) is not a configuration, but a term that refers to multiple Agile Release Trains (ARTs) working together. Lean Enterprise SAFe (F) is not a configuration, but a goal that SAFe 5.0 aims to help organizations achieve.

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

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 Framework 2: Core Values - Scaled Agile Framework

Two reasons the Agile Manifesto for Software Development is still relevant to Lean-Agile Enterprises are:

It provides the foundation for empowered, self-organizing Agile teams. The Agile Manifesto values individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan1. These values support the creation of cross-functional, autonomous, and collaborative teams that can deliver value to customers and stakeholders in an agile way2.

SAFe extends the value system and principles of the Agile Manifesto to teams of Agile teams. SAFe is based on the Agile Manifesto, but also incorporates additional values and principles that address the challenges of scaling agile to the enterprise level3. SAFe values alignment, built-in quality, transparency, and program execution, as well as the four original values of the Agile Manifesto4. SAFe also applies nine additional principles that guide the behavior of teams of Agile teams, or Agile Release Trains (ARTs), in a Lean-Agile context5.

1: Agile Manifesto for Software Development | Agile Alliance 2: The Agile Manifesto at 20: What’s still relevant—and what’s not | TechBeacon 3: SAFe Lean-Agile Principles - Scaled Agile Framework 4: Core Values - Scaled Agile Framework 5: SAFe Lean-Agile Principles - Scaled Agile Framework

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.