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.

The appropriate Lean action to take once all of the expected value of an Epic has been delivered, even if all of the planned Features have not been completed, is to close the Epic1. This means that the Epic Owner declares that the epic is done and no further work is required. Closing the epic frees up the resources and budget that were allocated to it, and allows the teams to focus on other value streams and initiatives. Closing the epic also enables the Epic Owner to measure the actual outcomes and benefits of the epic, and compare them with the expected ones in the Lean business case2. Closing the epic does not mean that the solution is fixed and cannot be changed or improved later. It simply means that the current hypothesis of the epic has been validated or invalidated, and that further work can be initiated as new epics or features if needed3.

1: Epic - Scaled Agile Framework 2: Epic - Scaled Agile Framework 3: Epic - Scaled Agile Framework

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 Government Article on the Scaled Agile Framework website, tagging backlog items with funding metadata for future reporting and calculating a fixed cost labor cost per ART based on actual salaries are two recommendations for tracking expenditures using the Program Backlog. The article states that “To track expenditures, the Program Backlog can be tagged with funding metadata for future reporting. Additionally, a fixed cost labor cost per ART can be calculated based on actual salaries. This simplifies the tracking of labor costs and allows for more accurate forecasting.” Therefore, the correct answers are A, tagging backlog items with funding metadata for future reporting, and E, calculating a fixed cost labor cost per ART based on actual salaries. The other options are not accurate, as they are not the recommendations for tracking expenditures using the Program Backlog. Organizing ARTs by funding classification (B) is not a recommended practice, as it may create silos and reduce collaboration across ARTs. Including a fiduciary expert in backlog refinement © is not a necessary step, as the backlog items should be prioritized based on value and not on cost. Using charge codes assigned by each program (D) is not a simple or effective way to track expenditures, as it may introduce overhead and complexity.

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 Strategic Themes article on the Scaled Agile Framework website, strategic themes are portfolio-level business objectives that provide competitive differentiation and strategic advantage. They provide business context for portfolio strategy and decision-making, representing aspects of the enterprise’s strategic intent. Strategic themes are best stated in Objective and Key Result (OKR) format. Written in plain business language, these OKRs say what the portfolio will pursue, thus providing decision-makers and contributors at all levels the clarity needed for decentralized decision-making. Therefore, the correct answer is D, create a ‘one-stop shop’ for all citizen-facing services provided by the agency. This is a good example of an agency strategic theme, as it expresses a clear and measurable goal that aligns with the agency’s vision and mission. The other options are not accurate, as they are not good examples of agency strategic themes. Comply with agency development lifecycle regulations (A) is not a strategic theme, but a compliance requirement that applies to all solutions. Reduce agency IT spend (B) is not a strategic theme, but a cost-cutting measure that does not reflect the value proposition of the agency. Improve cost and schedule performance of IT projects © is not a strategic theme, but a project management metric that does not capture the business outcomes of the solutions.

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 Lean-Agile Leadership article on the Scaled Agile Framework website, psychological safety occurs when leaders create an environment for risk-taking that supports change without fear of negative consequences to self-image, status, or career. The article states that “Psychological safety is a shared belief that the team is safe for interpersonal risk-taking. It can be defined as ‘being able to show and employ one’s self without fear of negative consequences of self-image, status, or career.’ In psychologically safe teams, team members feel accepted and respected. They are confident that no one on the team will embarrass or punish anyone else for admitting a mistake, asking a question, or offering a new idea.” Therefore, the correct answer is B, psychological safety. The other options are not accurate, as they are not the terms that describe the outcome of creating an environment for risk-taking that supports change without fear of negative consequences. Decentralized decision-making (A) is a principle, not an outcome, of Lean-Agile leadership. Emotional intelligence © is a skill, not an outcome, of Lean-Agile leadership. Alignment (D) is a value, not an outcome, of Lean-Agile leadership.