SAFe-SGP Sample Questions Answers

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, relentless improvement is one of the four core values of SAFe, along with alignment, transparency, and respect for people. The article states that “Relentless improvement is a constant sense of danger combined with a paranoid desire to find a better way. It’s a culture of organizational self-assessment, problem-solving, and action. It’s a willingness to change before the crisis forces us to do so. It’s a commitment to relentless reflection and a continuous learning journey.” Therefore, the correct answer is C, relentless improvement. The other options are not accurate, as they are not the core values of SAFe. Intrinsic motivation of knowledge workers is a principle, not a value, of SAFe. Individuals and interactions is a value of the Agile Manifesto, not of SAFe. Built-in quality is an aspect of SAFe, not a value.

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.

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

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

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

The Innovation and Planning (IP) Iteration is critical to success in SAFe because it provides the following benefits12:

It creates a guard band that ensures program predictability on cadence. The IP iteration acts as an estimating buffer that helps the ART meet their PI objectives and avoid carrying unfinished work into the next PI.

It ensures time for creative problem-solving needed by knowledge workers. The IP iteration allows the ART to explore innovative ideas, conduct research and design activities, and learn new skills and technologies.

It provides a consistent time for PI Planning. The IP iteration includes time for the PI planning event, which aligns the ART with the vision, roadmap, and strategic themes, and establishes the PI objectives and dependencies.

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

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.