Scrum SAFe-Practitioner SAFe Practitioner Exam (6.0) Exam Practice Test

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, a work in process (WIP) constraint is a limit on the amount of work that can be done at any stage of the value stream. The purpose of a WIP constraint is to reduce the batch size, manage the queue length, and improve the flow of value. By limiting the WIP, teams can focus on completing the most important work items, collaborate more effectively, and deliver value faster and more frequently. A WIP constraint also helps teams identify and resolve bottlenecks, reduce waste, and increase quality. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe® for Teams - Know Your Role on an Agile Team, [Visualize and limit WIP, reduce batch sizes, and manage queue lengths]

A program event is an event that involves all the teams in an Agile Release Train (ART) and occurs at the program level. According to the SAFe for Teams SP (6.0) handbook, there are three program events: PI Planning, System Demo, and Inspect and Adapt1. Innovation and Planning (IP) is also a program event, as it is a special iteration that occurs at the end of each Program Increment (PI) and provides time for the ART to innovate, plan, and improve2. Therefore, Innovation and Planning is an example of a program event. The other options are not program events, but team events, as they occur at the team level and involve only one agile team. Scrum of scrums, Iteration review, and Daily stand-up are team events that are part of the iteration execution cycle3. References: SAFe for Teams SP (6.0) - SAFe Practitioner handbook, Innovation and Planning Iteration - Scaled Agile Framework, Iteration Execution - Scaled Agile Framework

The Scrum Master is a servant leader and coach for the Agile team. One of their main responsibilities is to remove impediments that hinder the team’s progress and performance. Impediments can be anything that blocks the team from delivering value, such as technical issues, dependencies, conflicts, or lack of resources. The Scrum Master helps the team identify and resolve impediments as quickly as possible, and escalates them to the appropriate level if needed. By removing impediments, the Scrum Master helps the team stay focused, productive, and motivated. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, [Scrum Master]

 User Stories are the types of work that are found within the Agile Team Backlog. User Stories are short descriptions of a small piece of functionality that provides value to a user or customer. They are written from the perspective of the user or customer and follow the format: “As a , I want , so that ”. User Stories are the primary way of expressing the requirements and features in the Agile Team Backlog. They are estimated, prioritized, and implemented by the Agile Team in Iterations. User Stories are derived from Features in the Program Backlog, as well as from the team’s local context and other stakeholders. References: Team Backlog, User Stories, Story

According to the Lean-Agile Leadership competency of SAFe, management must commit to quality and take responsibility to change the system for a successful Agile transformation. This means that leaders must lead by example, learn and model the Lean-Agile mindset, values, principles, and practices, and lead the change to a new way of working. They must also empower and engage individuals and teams to reach their highest potential, and create a culture of relentless improvement and innovation1. Management cannot delegate or outsource the responsibility of leading the Agile transformation, as they are the ones who have the authority and influence to change and improve the systems that govern how work is performed2. References: 1: Lean-Agile Leadership - Scaled Agile Framework2: What Must Management Do for a Successful Agile Transformation?

Lean Portfolio Management, Agile Product Delivery, and Lean-Agile Leadership are three of the seven SAFe Core Competencies. These competencies are essential to achieving Business Agility, which is the ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative business solutions1. The SAFe Core Competencies are as follows2:

Lean-Agile Leadership: Inspires, empowers, and coaches the people who design, build, and support the world’s solutions

Team and Technical Agility: Drives high-quality, innovative solutions that delight customers and operate reliably

Agile Product Delivery: Builds solutions that customers love, delivered with high frequency and quality

Enterprise Solution Delivery: Builds and evolves the world’s largest and most sophisticated software, hardware, cyber-physical, and systems-of-systems solutions

Lean Portfolio Management: Aligns strategy and execution by applying Lean and systems thinking approaches to strategy and investment funding, Agile portfolio operations, and governance

Organizational Agility: Adapts quickly to changing market conditions and customer needs by reconfiguring strategy, structure, processes, people, and technology toward value-creating and value-preserving opportunities

Continuous Learning Culture: Improves the competency and skills of individuals and teams, fosters a culture of innovation, and creates organizational resiliency References: 1: Business Agility - Scaled Agile Framework2: Core Competencies - Scaled Agile Framework

 WIP stands for work in process, which is the amount of work that is currently being done in a system. One way to understand WIP is to make it visible to all stakeholders, using tools such as Kanban boards, cumulative flow diagrams, or burn-up charts. By making WIP visible, we can see the current state of the work, identify bottlenecks, limit WIP to match capacity, and improve flow efficiency. References: Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths, Make Value Flow without Interruptions, SAFe Principle 6: Visualise and limit WIP, reduce batch sizes, and manage queued lengths

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, one of the core values of SAFe is alignment, which means that everyone involved in the solution development has a common understanding of the vision, strategy, and goals. To achieve alignment, teams need to demonstrate progress by showing the actual working product to the stakeholders and getting feedback. This is done through the sync events such as the Team Demo and the System Demo, where teams showcase the features and stories they have completed in the iteration or the PI. By showing the actual working product, teams can validate their assumptions, measure the value delivered, and identify improvement opportunities. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe® for Teams - Know Your Role on an Agile Team, SAFe for Teams | SAFe Practitioner (SP) Certification

 Business agility is the ability to compete and thrive in the digital age by quickly responding to market changes and emerging opportunities with innovative business solutions1. It is the primary goal of SAFe, as it enables enterprises to deliver value faster, better, and more sustainably2. SAFe provides a set of principles, practices, competencies, and values that help organizations achieve business agility3. References: 1: Business Agility 2: SAFe for Teams Student Workbook: materials and exercises from Lesson 1 3: SAFe Core Values

The product vision is a description of the future state of the product or service under development. It reflects customer and stakeholder needs, as well as the features and capabilities proposed to meet those needs. The product vision is both aspirational and achievable, providing the broader context and purpose of the product or service. It describes the markets, customer segments, user needs, and how the product or service will be different from the competition. The product vision is owned by the product owner, but its development requires input from stakeholders and the scrum team(s). The product vision helps align the team to the product direction and motivates them to deliver value to the customers and stakeholders. References: Vision, Solution Vision, An Insight Into 3 Types of Vision In SAFe®, Product Vision | Agile Product Management, What is a Product Vision | Scrum.org

Learn more

1blob:https://www.bing.com/887da8ea-10bc-44f4-a242-61b97911b7b4

v5.scaledagileframework.com2blob:https://www.bing.com/e2cea8b8-df2b-4b04-89c4-e68cf94d95e6

scaledagileframework.com

The Inspect and Adapt workshop is a significant event held at the end of each Program Increment (PI), where the current state of the Solution is demonstrated and evaluated by the train1. The first part of the workshop is the PI System Demo, which shows all the Features that the Agile Release Train (ART) has developed over the course of the PI2. The other options are not activities that occur during the Inspect and Adapt workshop. Refining the ART backlog is a continuous process that happens throughout the PI3. A retrospective of the Iteration is a team-level event that happens after every Iteration4. Planning the next PI is a separate event that happens before the start of the next PI.

The PI Planning event is a two-day event that brings together all the teams and stakeholders of an Agile Release Train (ART) to align on a common vision, mission, and goals for the upcoming Program Increment (PI). The goal of the PI Planning event is to achieve alignment on what needs to and can be built by the ART in the next PI, based on the business context, customer needs, and technical dependencies. The PI Planning event also fosters collaboration, communication, and commitment among the teams and stakeholders, and helps identify and address the risks and impediments that may affect the delivery of value. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, [PI Planning]

The SAFe Implementation Roadmap is a strategy and an ordered set of activities that have proven to be effective in successfully implementing SAFe. It is based on organizational change management strategies and provides the critical moves for adopting SAFe. The roadmap consists of 14 steps, from reaching the tipping point to sustaining and improving1. References: 1: Implementation Roadmap - Scaled Agile Framework

Release Governance is the process that guides the final approval for a release in SAFe. It involves a set of roles and responsibilities that ensure the quality, compliance, and fitness for purpose of the solution before it is released to customers. Release Governance also coordinates the timing and frequency of releases based on market demand and business needs. Release Governance is part of the Release on Demand aspect of the Continuous Delivery Pipeline, which is the fourth and last element in the four-part pipeline of Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand. References: Release on Demand - Scaled Agile Framework, SAFe for teams 93% Flashcards | Quizlet, Release on Demand - SAFe 4.5 Reference Guide: Scaled Agile Framework …

The Iteration Review is a regular SAFe Scrum event where the team inspects the iteration increment, assesses progress, and adjusts the team backlog. The purpose of the Iteration Review is to measure the team’s progress by showing working stories to the Product Owner and other stakeholders to get their feedback. The Iteration Review provides a way to gather immediate, contextual feedback from the team’s stakeholders on a regular cadence. The Iteration Review also allows the team to demonstrate their contributions, receive feedback to improve the solution, and adjust the Team Backlog based on new opportunities. References: Iteration Review, Iteration Review, What is Iteration review in SAFe® 6.0?, Iteration Review65

The Portfolio Kanban system is a method to visualize and manage the flow of portfolio Epics, from ideation through analysis, implementation, and completion1. The analyzing step of the Portfolio Kanban system involves developing a Lean business case for the Epic and presenting it to Lean Portfolio Management (LPM) for approval1. If the Epic receives a ‘go’ decision from LPM, it will be moved to the ready state in the Portfolio Kanban, where it will wait until one or more Agile Release Trains (ARTs) have the capacity to implement it1. The other options are incorrect because:

A. The Epic Owner does not have the authority to approve the Lean business case. Only LPM can make the final decision on whether to proceed with the Epic or not1.

C. The Epic will not remain in the analyzing step after receiving a ‘go’ decision from LPM. It will be moved to the ready state, where it will be prioritized using weighted shortest job first (WSJF) and other factors1.

D. The Epic will not be implemented based on its WSJF ranking alone. It will also depend on the availability and alignment of the ARTs that can deliver the Epic1. References: 1: Portfolio Kanban - Scaled Agile Framework

The team is waterfalling the Iteration, which means they are following a sequential and rigid process of development, testing, and fixing, instead of an iterative and incremental approach. This is not aligned with the Agile principles and practices, which advocate for delivering working software frequently, with continuous feedback and improvement. Waterfalling the Iteration reduces the team’s ability to respond to change, deliver value, and collaborate effectively. It also increases the risk of accumulating technical debt, defects, and rework. References: Iteration Execution - Scaled Agile Framework, SCALING: SP - SAFe for Teams 4.6 Flashcards - Brainscape

n: Agile development is more beneficial than waterfall development because it increases productivity and employee engagement by empowering teams to self-organize, collaborate, and deliver value in small increments. It also allows businesses to deliver value to the market more quickly by reducing the feedback cycle, adapting to changing requirements, and releasing high-quality products frequently. References: SAFe® for Teams - Know Your Role on an Agile Team, Exam Study Guide: SP (6.0) - SAFe® Practitioner, Lean-Agile Mindset, Continuous Delivery Pipeline

According to the SAFe-for-Teams-SAFe-Practitioner-6-0 documents, a minimum viable product (MVP) is an early and minimal version of a new solution sufficient to prove or disprove an epic hypothesis1. An MVP is not a prototype, a feature, or a product. It is a learning tool that helps validate assumptions, reduce uncertainty, and increase the likelihood of building the right thing2. Therefore, the correct answer is A. A minimal version of a new product used to test a hypothesis. References: Epic - Scaled Agile Framework, What is a Minimum Viable Product (MVP)? | Agile Alliance

Emergent design and intentional architecture are two complementary approaches to designing and evolving a system’s architecture. Emergent design enables fast, local control so that teams can react appropriately to changing requirements without excessive attempts to future-proof the system. Intentional architecture provides the guidance needed to ensure that the whole system has conceptual integrity and is fit for its purpose. Balancing these two approaches is required for speed of value delivery and Solution Intent, which is the representation of the desired and actual solution behavior, including the functional and nonfunctional aspects. Solution Intent guides the development and evolution of the solution and helps align the teams and stakeholders on the vision and goals of the solution. References: Architectural Runway, Agile Architecture in SAFe, Balancing Emergent Design and Intentional Architecture in Agile Software Development

According to SAFe, an Agile team is a cross-functional group of 5-11 individuals who define, build, test, and deliver an increment of value in a short time box1. This size allows for enough diversity of skills and perspectives while still allowing for close collaboration and communication among team members. Larger teams tend to have more communication overhead, coordination challenges, and reduced productivity. Smaller teams may lack some of the necessary skills or perspectives to deliver value effectively. References: Agile Teams - Scaled Agile Framework, What is the Recommended Size of an Agile Team? - StuffSure, The Number 7: Why is it so important? - agile42

 The ART Planning Board, also known as the Program Board, is a visualization of the PI’s feature delivery dates, feature dependencies among teams, and relevant milestones. The primary purpose of the ART Planning Board is to show dependencies between teams relating to the Feature development, so that they can be identified, managed, and resolved during PI Planning and execution. The ART Planning Board also helps align teams and stakeholders to a shared mission and vision, and provides transparency and visibility into the ART’s progress and risks. References: ART Planning Board, PI Planning, Exam Study Guide: SP (6.0) - SAFe Practitioner

 According to the SAFe principle, “unlock the intrinsic motivation of knowledge workers”, knowledge workers need autonomy, mastery, and purpose to be motivated and creative. Autonomy means giving them the freedom to choose how to do their work, without micromanagement or excessive control. Mastery means providing them with opportunities to learn new skills and improve their craft. Purpose means aligning their work with a meaningful and inspiring vision. These three factors foster intrinsic motivation, which is the drive to perform an activity without any obvious external rewards. References: Principle #8 - Unlock the Intrinsic Motivation of Knowledge Workers - Scaled Agile Framework, Principle #8 - Unlock the Intrinsic Motivation of Knowledge Workers - Scaled Agile Framework

 According to Kotter’s 8-step process for leading change, the first step is to create a sense of urgency among both managers and employees. This means making them aware of the existing problems or opportunities that require change, and motivating them to act with passion and purpose. Creating a sense of urgency helps to overcome complacency, resistance, and fear of change, and builds momentum for the change initiative. References: Kotter’s 8-step process for leading change, The Easy Guide to Kotter’s 8 Step Change Model, John Kotter’s Eight Step Change Model, Kotter’s 8 step Model of Change, How to Successfully Implement Kotter’s 8 Step Change Model

This statement is one of the 12 principles behind the Agile Manifesto1, which guides the agile software development approach. It means that agile teams should focus on delivering the most valuable features and avoid unnecessary work that does not add value to the customer or the product. By applying simplicity, agile teams can reduce waste, increase efficiency, and improve quality. References: 12 Principles Behind the Agile Manifesto

Flow efficiency is the ratio of the total time spent in value-added work activities divided by the total flow time. Flow time is the time it takes for a work item to move from the start to the end of the process. Value-added work activities are those that directly contribute to the customer value or the quality of the product. Non-value-added work activities are those that do not add value to the customer or the product, such as waiting, rework, or handoffs. Flow efficiency measures how well the organization is minimizing the non-value-added work and maximizing the value-added work. The formula to calculate flow efficiency is:

Flow efficiency=Flow timeTotal active time​×100%

A higher flow efficiency indicates a more streamlined and effective process, while a lower flow efficiency indicates a more wasteful and inefficient process. Flow efficiency can be used to identify and eliminate the sources of waste and improve the flow of value to the customer1234. References: Flow Efficiency - Scaled Agile Framework, Flow Efficiency: A great metric you probably aren’t using, Flow Efficiency: A Great Metric You Probably Aren’t Using - Nimblework, Flow Efficiency: A Kanban Metric Introduction - Everyday Kanban

According to the book Team Topologies by Matthew Skelton and Manuel Pais, the four types of team topologies are stream-aligned, platform, enabling, and complicated subsystem. These team types are designed to optimize the flow of work and information in an organization, and to align with the principles of DevOps and agile. A stream-aligned team is focused on a single stream of work, such as a product, a feature, a user journey, or a user persona. A platform team provides the infrastructure and services that enable other teams to deliver value to customers. An enabling team helps other teams overcome obstacles and learn new skills and technologies. A complicated-subsystem team handles tasks that require specialized knowledge and expertise, such as mathematics, algorithms, or cryptography. References: Team Topologies: The 4 Team Types Explained | Shortform Books, Team Topologies | Atlassian, Key Concepts — Team Topologies, The Four Team Types from Team Topologies - IT Revolution, What are the core team types in Team Topologies?

Decentralized decision-making is one of the principles of the Lean-Agile mindset, which is the foundation of SAFe. It empowers teams and individuals to make decisions based on the local context and the best available information, rather than waiting for approval from higher authorities. This reduces delays, increases speed, and improves responsiveness to customer needs. It also fosters innovation, learning, and ownership of the outcomes. References: Lean-Agile Mindset, Unlock the Intrinsic Motivation of Knowledge Workers, Exam Study Guide: SP (6.0) - SAFe Practitioner

 Empathy maps are a design thinking tool that promotes customer identification by helping teams develop a deep, shared understanding of others. They enable teams to imagine what a specific persona is thinking, feeling, hearing, and seeing as they use the solution. Empathy maps help teams to design with empathy, which is a key behavior of customer centricity. Empathy maps can be used to explore different aspects of the problem and solution space, and to validate assumptions and hypotheses about the customer’s needs and preferences. References: Design Thinking, Customer Centricity

Business Owners are key ART stakeholders who have the primary business and technical responsibility for return on investment (ROI), governance, and compliance. They evaluate the fitness for use and actively participate in ART events and solution development. They also use a scale of 1 (lowest) to 10 (highest) to assign the business value to the team PI objectives after negotiation with the teams and other stakeholders. They typically assign the highest values to the customer-facing objectives. References: Business Owners - Scaled Agile Framework, PI Objectives - Scaled Agile Framework

Collective ownership and standards are basic quality practices that apply to all teams, regardless of their domain or work product. They promote shared responsibility, accountability, and alignment among team members and across teams1. They also enable faster feedback, continuous improvement, and reduced waste2. The other options are not basic quality practices, but rather specific techniques or approaches that may be useful for some teams or domains, but not all. Agile architecture is a way of designing and evolving systems that support the delivery of value and quality3. Rapid prototyping is a way of creating and testing a minimum viable product (MVP) to validate assumptions and learn from customers4. Modeling and simulation are ways of representing and analyzing complex systems or phenomena using mathematical or computational methods.

The team’s initial capacity before calculating for time off is 48. This is based on the following formula: Give the team 8 points for every full-time developer and tester on the team. Since the team has two testers and three developers, that is 5 x 8 = 40 points. Then, add one point for every 10% of the Product Owner’s time dedicated to the team. Since the Product Owner is split between two teams, that is 0.5 x 10 = 5 points. Finally, add one point for every 10% of the Scrum Master/Team Coach’s time dedicated to facilitating the team. Since the Scrum Master/Team Coach is full-time, that is 1 x 10 = 10 points. The total is 40 + 5 + 10 = 55 points. However, since the team should not plan to 100% capacity, a buffer of 15% is recommended. Therefore, the final initial capacity is 55 x 0.85 = 46.75, which can be rounded up to 48 points. References: Iteration Planning, How to calculate the capacity, How to Estimate Capacity for Work in Agile Teams, SAFe Agile Planning - Plan Less than 100% Capacity, How to Improve Your Agile Team’s Capacity Planning

Quality is the first and foremost function of the second core value of SAFe, which is Built-in Quality1. Built-in Quality is a set of practices to help ensure that the outputs of Agile teams in business and technology domains meet appropriate quality standards throughout the process of creating customer value2. Built-in Quality requires a culture of shared responsibility, where everyone on the team is accountable for the quality of the work products and the system as a whole2. This culture fosters collaboration, feedback, and continuous improvement, and enables faster delivery and better outcomes2. References: Built-In Quality - Scaled Agile Framework, Quality is the first and foremost a function of what in a Lean-Agile …, Quality is first and foremost a function of what in a lean-agile …

 An Agile Team collects the Iteration Metrics they have agreed upon during the quantitative part of the team retrospective. This is the part where the team assesses whether they met the Iteration Goals using a binary (yes or no) measure, and reviews the metrics that provide visibility and insight into the team’s performance and process improvement. Examples of Iteration Metrics include flow metrics, such as flow velocity, load and distribution, defects addressed, and automated test coverage. The team uses these metrics to identify trends, patterns, and areas for improvement, and to inform their qualitative feedback and improvement stories. References: Iteration Retrospective - Scaled Agile Framework, Metrics - Scaled Agile Framework

According to the Scaled Agile Framework, the ART Planning Board is a visualization of the PI’s feature delivery dates, feature dependencies among teams, and relevant milestones1. Features are the primary elements that are planned and tracked on the ART Planning Board2.

Epics, user stories, and tasks are not found on the ART Planning Board, but they are related to features in different ways. Epics are large initiatives that span multiple ARTs and PIs, and they are decomposed into features and enablers2. User stories and tasks are smaller units of work that are used by teams to implement features within iterations2.

Acceptance criteria are the conditions that a story must satisfy to be accepted by the Product Owner and the stakeholders. They define the boundaries of the story and provide guidance on how to test it for completion. Acceptance criteria are usually written as a list of statements or scenarios that describe the expected behavior and outcomes of the story. They help to ensure that the story delivers value to the user and meets the Definition of Done1234. References: Story - Scaled Agile Framework, How to Write Agile Test Case Requirements | SmartBear, Agile Story Completion Checklist - SDLCforms, Module 2: Complete a story - IBM

Team and Technical Agility is one of the core competencies of the Lean Enterprise that helps drive Agile Quality practices. This competency describes the critical skills and Lean-Agile principles and practices that high-performing Agile teams and teams of Agile teams use to create high-quality solutions for their customers. The main aspects of this competency are: team and technical agility, Agile team, Built-in Quality, and Agile architecture. Built-in Quality is a set of practices to help ensure that the outputs of Agile teams in business and technology domains meet appropriate quality standards throughout the process of creating customer value. Built-in Quality practices include test-first, test automation, continuous integration, refactoring, pair work, code reviews, exploratory testing, and more. References: Team and Technical Agility - Scaled Agile Framework, Built-In Quality - Scaled Agile Framework

Lowering the work in process (WIP) limits improves the flow of value through the system by reducing the amount of work that is started but not finished, minimizing the waste of context switching and multitasking, and increasing the focus and collaboration of the teams. Lower WIP limits also help identify and eliminate bottlenecks, balance demand and capacity, and accelerate feedback and learning. According to the SAFe Principle #6, visualizing and limiting WIP is one of the key practices to achieve continuous flow and deliver value in the shortest sustainable lead time. References: Principle #6 - Visualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengths - Scaled Agile Framework, Understanding SAFe Work In Progress Limits - Strongback Consulting

Roadmaps are a visual tool that assists in the development and communication of planned deliverables, milestones, and investments over time and help distinguish different types of work1. Roadmaps are the glue that links strategy to execution and offer the ability to develop, evolve and adjust planned activities1. Roadmaps communicate intent, not commitment, as they are subject to change based on feedback, learning, and market conditions1. Roadmaps are not fixed at PI boundaries, but rather are updated frequently to reflect the current state of the solution and the environment1. Roadmaps provide multiple planning horizons, such as near-term, mid-term, and long-term, to show how the solution will evolve over time1. References: 1: Roadmap

The Portfolio Kanban is a method to visualize, manage, and analyze the flow of portfolio epics from ideation to implementation1. It brings structure to analysis and decision making around epics by defining the states and Work in Process (WIP) limits for each state, as well as the entry and exit criteria1. The Portfolio Kanban also helps prioritize and sequence the epics based on the Lean business case and the Weighted Shortest Job First (WSJF) technique1. The Portfolio Kanban enables the Lean Portfolio Management (LPM) to align the portfolio strategy and investment funding with the implementation capacity of the value streams2. References: Portfolio Kanban, Lean Portfolio Management

 = Making quality everyone’s responsibility is critical to successfully implementing quality in a Lean-Agile environment. This means that all the people involved in creating and delivering value to the customer, from business functions to software applications, share the same quality standards and practices. Quality is not something that can be delegated or outsourced to a separate team or department. It is embedded in the culture, mindset, and behavior of every individual and team. Making quality everyone’s responsibility enables faster feedback, continuous improvement, and higher customer satisfaction12. References: = 1: Built-In Quality - Scaled Agile Framework2; 2: How to Implement Quality in a Lean-Agile Environment Successfully1

 The Product Owner (PO) in the team is responsible for managing and prioritizing the Team Backlog, which is the single source of truth for the upcoming features of the system1. The PO works with the Product Manager, who owns the Vision and the Roadmap, to define and sequence the features in the Program Backlog2. The PO also collaborates with other POs in the Agile Release Train (ART) to manage dependencies and ensure alignment across teams3. The PO maintains and prioritizes the Team Backlog, which contains user stories, enablers, and other backlog items that the team needs to implement to deliver value to the customer4. The PO also participates in the backlog refinement sessions, where the team defines, discusses, estimates, and establishes acceptance criteria for the backlog items. References: Team Backlog - Scaled Agile Framework, Product Owner - Scaled Agile Framework, Program Backlog - Scaled Agile Framework, Story - Scaled Agile Framework, [Backlog Refinement - Scaled Agile Framework]

 The “C” in the CALMR approach to DevOps represents culture. Culture is the first element of the CALMR mindset, which guides the ART toward achieving continuous value delivery by enhancing culture, automation, lean flow, measurement, and recovery1. Culture refers to the shared values, beliefs, and behaviors that support collaboration, communication, and continuous improvement among the development, operations, security, and other teams involved in the value stream2. Culture also includes respecting and empowering the people and teams, fostering a learning and growth mindset, and creating a customer-centric focus3. Culture is the foundation of DevOps, as it enables the alignment and integration of the technical and organizational aspects of DevOps4. The other options are not what the “C” stands for in the CALMR approach to DevOps, although they are related to other elements of the mindset. Completion is not a specific term in the CALMR approach, but it could be associated with measurement, which tracks the progress and outcomes of the value delivery. Cycle-time is a metric that measures the time it takes to deliver value from idea to production, and it is influenced by lean flow, which optimizes the value stream and eliminates waste. Continuous integration is a technical practice that involves merging code changes frequently and automatically testing them, and it is part of automation, which reduces manual work and errors and accelerates feedback loops. References: CALMR - Scaled Agile Framework, The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut, Core Values - Scaled Agile Framework, CALMS DevOps : Defining 5 DevOps Principles | Cprime

SAFe provides a second operating system that enables Business Agility by creating a network of Agile teams and trains that are aligned to a common vision and strategy, and empowered to deliver value to customers and users. SAFe leverages the Lean-Agile mindset, the core competencies, and the principles and practices to foster a culture of innovation, learning, and collaboration. SAFe also supports the continuous delivery pipeline, which enables fast feedback and frequent value delivery. References: SAFe® for Teams - Know Your Role on an Agile Team | Scaled Agile, Exam Study Guide: SP (6.0) - SAFe® Practitioner - scaledagile.com, SAFe 6.0 for Teams with SP Certification - ICON Agility Serviceswq

Telemetry is a method for gathering customer feedback that relies on building analytic systems to deliver information about how customers are using the Solution. Telemetry is the automated collection and transmission of data from remote sources, such as sensors, devices, or software applications. Telemetry can provide valuable insights into customer behavior, preferences, satisfaction, and usage patterns, as well as identify potential issues, errors, or defects. Telemetry is often used in conjunction with other feedback methods, such as surveys, interviews, or user testing, to validate hypotheses and measure outcomes. References: Continuous Delivery Pipeline, Customer Feedback, Telemetry

Assuming variability and preserving options is one of the SAFe Lean-Agile Principles that includes the critical part of “delaying decisions to the last responsible moment”. This principle states that "instead of committing to a single, often premature, design or requirement, Agile teams build systems that have the flexibility to support multiple options. They defer making decisions until the last responsible moment, when they have the most information and can make the best choice."1 This principle helps teams cope with uncertainty, reduce risk, and increase innovation.2 References: SAFe Lean-Agile Principles, Exam Study Guide: SP (6.0) - SAFe® Practitioner

 = The “3 Cs” of user stories are three criteria that help to ensure that the requirements in your story are clear, complete, and correct. These three criteria are Card, Conversation, and Confirmation1.

Card: A user story card is a placeholder for a conversation. It is a brief and informal description of a software feature written from the perspective of the end user. It captures the essence of the user’s need, without going into too much detail or technical jargon. It is usually written on a physical or digital card that can be easily moved and prioritized2.

Conversation: A user story card is not enough to convey all the information needed to develop and deliver the feature. It is meant to trigger a conversation between the product owner, the development team, and other stakeholders. The conversation is where the details, assumptions, risks, and acceptance criteria are discussed and clarified. The conversation is also an opportunity to collaborate, negotiate, and validate the user story3.

Confirmation: A user story is not complete until it has a confirmation. This is a set of criteria that define what done looks like for the feature. It is also known as acceptance criteria, and it specifies the conditions that must be met for the user story to be accepted by the product owner and the customer. The confirmation is usually written as a series of testable statements that can be verified by the development team and the product owner4.

= Mindset and Principles is one of the three dimensions of Lean-Agile Leadership, along with Leading by Example and Leading the Change. Mindset and Principles refers to how leaders embed the Lean-Agile way of working in their beliefs, decisions, responses, and actions. Leaders model the expected norm throughout the organization by learning and applying the SAFe Core Values, Lean-Agile Mindset, and SAFe Principles. References: = Lean-Agile Leadership - Scaled Agile Framework, Exam Study Guide: SP (6.0) - SAFe® Practitioner

= Lean Portfolio Management (LPM) is one of the seven core competencies of the Lean Enterprise that helps align strategy and execution. LPM enables enterprises to establish and communicate a set of strategic themes that provide business context for decision making and investment allocation. LPM also helps to apply Lean budgeting and guardrails to empower decentralized program execution and foster innovation. LPM also supports Agile portfolio operations and governance by providing the necessary visibility, coordination, and collaboration across the portfolio. References: = SAFe for Lean Enterprises, Lean Portfolio Management

 The Continuous Delivery Pipeline represents the workflow, activities, and automation needed to deliver new functionality more frequently. It consists of four elements: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand. The pipeline enables faster value delivery, higher quality, and lower risk. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Continuous Delivery Pipeline, Lesson 4: Deliver Value

 A User Story is a short description of a piece of functionality that delivers value to a customer or stakeholder. It is typically written from the perspective of an end user and follows the format: “As a , I want , so that ”. User Stories are the primary elements of the Team Backlog and are used to plan and execute the Iteration. User Stories should be small enough to be completed within one Iteration, which is usually two weeks long. If a User Story is too large or complex, it should be split into smaller stories that can fit within the Iteration timebox. This ensures that the team can deliver value frequently and receive feedback quickly. References: SAFe for Teams Student Workbook: materials and exercises from Lesson 3; v6.scaledagileframework.com/story/

 Story Mapping is a design-thinking technique that helps break down Features while considering the end-to-end user flow. It is a collaborative practice that visually maps the user journey and the activities that the user performs to reach a desired outcome. Story Mapping helps teams understand the user needs, prioritize the backlog, and plan the iterations and PIs. References: Story Mapping, Story, Exam Study Guide: SP (6.0) - SAFe® Practitioner

According to the SAFe for Teams SP (6.0) - SAFe Practitioner handbook and study guide, the purpose of Iteration Planning is to plan the work that the team will commit to deliver in the Iteration. The team collaborates with the Product Owner to select the Stories from the Team Backlog, define the acceptance criteria, break them into tasks, estimate the effort, and identify the dependencies and risks. The team also defines the Iteration goals and the Iteration backlog, which reflect the scope of the Iteration. The Iteration Planning ensures that the team has a clear and realistic plan to deliver value in the Iteration. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe® for Teams - Know Your Role on an Agile Team, [Iteration Planning]

https://v5.scaledagileframework.com/iteration-planning/

A guardrail in Lean Portfolio Management (LPM) is a policy or practice that helps ensure that the portfolio is aligned and funded to create and maintain the solutions needed to meet business targets. One of the guardrails in LPM is the allocation of centralized vs decentralized decisions in the enterprise. This guardrail defines the boundaries and guidelines for decision making at different levels of the organization, such as strategic, tactical, and operational. Centralized decisions are those that require alignment and agreement across multiple value streams or portfolios, such as vision, strategy, budget allocation, and governance. Decentralized decisions are those that can be made by the value streams or teams closest to the customer and the work, such as backlog prioritization, solution design, and delivery. The goal of this guardrail is to empower the teams and value streams to make fast and effective decisions, while ensuring alignment and coherence at the portfolio and enterprise levels12. References: Lean Budget Guardrails - Scaled Agile Framework, Decentralize Decision Making - Scaled Agile Framework

 During the team breakout session, each team creates and estimates their Stories, and sequences them into a draft plan for the upcoming PI. This is where the team backlog is refined and prioritized, and dependencies are identified and resolved. References: SAFe for Teams - Know Your Role on an Agile Team, Exam Study Guide: SP (6.0) - SAFe® Practitioner, SAFe for Teams | SAFe Practitioner (SP) Certification

 A high-functioning Agile Team is a cross-functional group of typically ten or fewer individuals with all the skills necessary to define, build, test, and deliver value to their customer1. Team A is not cross-functional because they depend on another team to test and deploy their work, which creates handoffs and delays in the value delivery process. A cross-functional team should be able to perform all the activities required to deliver a potentially releasable increment of value in each iteration2. Team A should collaborate with the other team to integrate their testing and deployment capabilities and form a single Agile Team that can deliver value independently. References: Agile Teams - Scaled Agile Framework, 7 Qualities of High-Performing Agile Teams | AgileConnection

The modified Fibonacci sequence is a series of numbers that starts with 0, 1, 2, 3, 5, 8, 13, 20, 40, 100, and so on. It is used when estimating the relative size and complexity of backlog items, such as stories and features, using story points or normalized estimation. The modified Fibonacci sequence reflects the uncertainty in estimating larger items, as the gap between the numbers increases as the numbers get bigger. This means that the larger the item, the less precise the estimate, and the more likely it is to be split into smaller items. The modified Fibonacci sequence also helps to avoid the false sense of accuracy that comes from using linear scales, such as hours or days, which may not account for the variability and unpredictability of the work. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Story, Feature, Estimating

A Story is a short description of a small piece of desired functionality written from the user’s perspective and in their language. A Story has three primary components: Card, Conversation, and Confirmation. The Card captures the essence of the Story using the format: “As a (who), I want (what), so that (why).” The Conversation is the ongoing dialogue between the team and the customer or product owner to elaborate and refine the Story details. The Confirmation is the set of acceptance criteria and tests that verify the Story is done and meets the customer’s expectations. A Story provides just enough information for both business and technical people to understand the intent, but not so much that it becomes a specification or a contract. Details are deferred until the Story is ready to be implemented, which allows for more flexibility and feedback. A Story is not a static artifact, but a dynamic one that evolves through collaboration and learning12. References: Story - Scaled Agile Framework, [What is User Story? -

 According to the SAFe framework, some decisions are strategic, have far-reaching impact, and are outside the scope, knowledge, or responsibilities of the teams. These decisions should be centralized, as they are made by leaders who have the market knowledge, longer-range perspectives, and understanding of the business and financial landscape necessary to steer the enterprise. One of the characteristics of these types of decisions is that they provide significant economies of scale, meaning that they deliver large and broad economic benefits to the organization. Examples of such decisions are a common way of working, standard development languages, standard tooling, and offshoring. These decisions are infrequent, long-lasting, and require coordination and alignment across multiple teams and value streams. References: Principle #9 - Decentralize Decision-Making - Scaled Agile Framework, SAFe® and Importance of Decentralized Decision Making – Learnow

The Portfolio canvas is a tool that helps define the value streams, solutions, customers, budgets, and other key aspects of a SAFe portfolio. One of the inputs to the Portfolio canvas is the Enterprise Strategy, which describes the vision, mission, goals, and objectives of the organization. The Enterprise Strategy provides the context and direction for the portfolio vision, which in turn guides the identification and prioritization of portfolio epics and value streams. The Enterprise Strategy also influences the allocation of lean budgets and the alignment of strategic themes across the portfolio. References: Portfolio Vision, Portfolio SAFe, What Sections Are Included In SAFe® Portfolio Canvas?, [Exam Study Guide: SP (6.0) - SAFe Practitioner]

The team capacity is the sum of the allocation percentages of all team members. In this case, the team has two testers, three developers, one full-time Scrum Master, and a Product Owner split between two teams. Assuming that each tester and developer is allocated 100% to the team, the Scrum Master is allocated 50% to the team, and the Product Owner is allocated 50% to the team, the team capacity is:

2 x 100% + 3 x 100% + 1 x 50% + 1 x 50% = 600%

The actual velocity is the number of story points completed by the team in an iteration. Assuming that the team completed 40 story points in the first iteration, the actual velocity is:

40

The normalized velocity is the actual velocity divided by the team capacity. In this case, the normalized velocity is:

40 / 600% = 6.67

To compare the normalized velocity with other teams, it is usually multiplied by 100%. In this case, the normalized velocity is:

6.67 x 100% = 66.67

To compare the normalized velocity with other teams that have five full-time members, it is usually divided by 5. In this case, the normalized velocity is:

66.67 / 5 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team, it is usually multiplied by 6. In this case, the normalized velocity is:

14 x 6 = 84

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this case, the normalized velocity is:

80 / 5 = 16

To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the next lower multiple of 4. In this case, the normalized velocity is:

16

To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In this case, the normalized velocity is:

16 x 5 = 80

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of full-time equivalent members in the team, it is usually divided by 6. In this case, the normalized velocity is:

80 / 6 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team, it is usually multiplied by 6. In this case, the normalized velocity is:

14 x 6 = 84

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this case, the normalized velocity is:

80 / 5 = 16

To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the next lower multiple of 4. In this case, the normalized velocity is:

16

To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In this case, the normalized velocity is:

16 x 5 = 80

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of full-time equivalent members in the team, it is usually divided by 6. In this case, the normalized velocity is:

80 / 6 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team, it is usually multiplied by 6. In this case, the normalized velocity is:

14 x 6 = 84

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this case, the normalized velocity is:

80 / 5 = 16

To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the next lower multiple of 4. In this case, the normalized velocity is:

16

To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In this case, the normalized velocity is:

16 x 5 = 80

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of full-time equivalent members in the team, it is usually divided by 6. In this case, the normalized velocity is:

80 / 6 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team, it is usually multiplied by 6. In this case, the normalized velocity is:

14 x 6 = 84

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this case, the normalized velocity is:

80 / 5 = 16

To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the next lower multiple of 4. In this case, the normalized velocity is:

16

To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In this case, the normalized velocity is:

16 x 5 = 80

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of full-time equivalent members in the team, it is usually divided by 6. In this case, the normalized velocity is:

80 / 6 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team, it is usually multiplied by 6. In this case, the normalized velocity is:

14 x 6 = 84

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of iterations in a PI, it is usually divided by 5. In this case, the normalized velocity is:

80 / 5 = 16

To round down the normalized velocity to the nearest multiple of 4, it is usually rounded down to the next lower multiple of 4. In this case, the normalized velocity is:

16

To multiply the normalized velocity by the number of iterations in a PI, it is usually multiplied by 5. In this case, the normalized velocity is:

16 x 5 = 80

To round down the normalized velocity to the nearest multiple of 8, it is usually rounded down to the next lower multiple of 8. In this case, the normalized velocity is:

80

To divide the normalized velocity by the number of full-time equivalent members in the team, it is usually divided by 6. In this case, the normalized velocity is:

80 / 6 = 13.33

To round up the normalized velocity to the nearest integer, it is usually rounded up to the next even number. In this case, the normalized velocity is:

14

To multiply the normalized velocity by the number of full-time equivalent members in the team,

one way Lean-Agile leaders lead by example is by modeling SAFe’s Lean-Agile Mindset, values, principles, and practices. This means that they learn and embody the core beliefs and behaviors that enable business agility, such as respect for people and culture, flow, innovation, relentless improvement, and leadership. They also apply the SAFe principles and practices to their own work, such as organizing around value, building incrementally, applying systems thinking, and assuming variability. By doing so, they demonstrate their commitment to the transformation and inspire others to follow their lead12. References: 1: Lean-Agile Leadership - Scaled Agile Framework2: What Is One Way Lean Agile Leaders Lead By Example? - GoRetro

 The daily stand-up is a 15-minute meeting that occurs every day during the Iteration, where the Agile team members synchronize their work, share their progress, and identify any impediments or dependencies. The daily stand-up follows a simple format, where each team member answers three questions:

What did I do yesterday to advance the Iteration goals?

What will I do today to advance the Iteration goals?

Are there any impediments that will prevent the team from meeting the Iteration goals? These questions help the team members to align their actions with the Iteration goals, communicate their status and plans, and raise any issues or risks that need to be addressed. The daily stand-up also fosters collaboration, accountability, and transparency among the team members, and enables them to adjust their work as needed to deliver value. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Daily Stand-up

The Portfolio Canvas is a tool that defines the current state of the portfolio, as well as the future state vision, using the Business Model Canvas template1. It describes the development value streams, the solutions they deliver, the customers they serve, the budget allocated to each value stream, and other vital activities and events required to achieve the portfolio vision2. The Portfolio Canvas is used to capture and analyze the current state of the portfolio, as well as to generate and evaluate multiple future state scenarios, based on the SWOT and TOWS analysis2. The Portfolio Canvas provides input for defining the future state vision and the portfolio backlog2. References: Business Model Canvas, Portfolio Vision

 One of the activities that occurs during the PI Planning event is the identification and analysis of the potential risks that may affect the delivery of value by the Agile Release Train (ART). The risks are categorized using the ROAM board, which stands for Resolved, Owned, Accepted, and Mitigated. The Managed category is a subset of the Mitigated category, where the risks are assigned to owners who are responsible for monitoring and controlling them throughout the PI. The Managed category addresses the potential risks that cannot be resolved, owned, or accepted, but can be reduced or avoided by applying appropriate strategies and actions. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, ROAMing Risks

One of the Lean Thinking Principles is to make value flow without interruptions. This means that the organization should optimize the entire value stream, from the customer’s perspective, and eliminate any waste or delays that prevent the smooth and fast delivery of value. Waste can be anything that does not add value to the customer, such as defects, overproduction, waiting, inventory, transportation, motion, or overprocessing. Delays can be caused by handoffs, queues, approvals, dependencies, or variability. By making value flow without interruptions, the organization can increase customer satisfaction, reduce costs, improve quality, and accelerate time to market. References: Lean Thinking: Overview, Principles, Benefits, & Applications Explained, Lean Thinking – Lean Practice | Planview LeanKit

A modified Fibonacci sequence is a relative estimating number sequence that reflects the inherent uncertainty of the job being estimated. It is based on the original Fibonacci sequence, which is a mathematical series of numbers where each number is the sum of the two preceding ones, starting from 0 and 1. The modified Fibonacci sequence, however, rounds up the larger numbers to avoid questions about why something is 21 instead of 20 or 34 instead of 40. The modified Fibonacci sequence is commonly used in Agile estimation techniques, such as Planning Poker, to assign story points to user stories or other backlog items. The sequence is: 0, 1, 2, 3, 5, 8, 13, 20, 40, 100. References: Modified Fibonacci Sequence - Scaled Agile Framework, Fibonacci Agile Estimation: What Is It and Why Does it Work? - Parabol

During the draft plan review, teams present their preliminary plans for the upcoming PI, including their iteration goals, capacity and load, and risks and impediments1. Iteration goals are a set of SMART objectives that provide a clear vision and alignment for each iteration2. They also help teams communicate their progress and dependencies to other teams and stakeholders during the PI planning event3. References: PI Planning, Iteration Goals, Presenting PI Planning Draft and Final Plan Reviews

A dual operating system is a model of business agility that combines the entrepreneurial network and the hierarchical system. The network is optimized for speed and innovation, while the hierarchy is optimized for efficiency and stability. The dual operating system allows the organization to balance the competing demands of exploration and exploitation, and to respond effectively to fast-changing environments. SAFe implements the network as a set of development value streams and provides the necessary interfaces to the hierarchy to restore the system’s balance. References: Principle #10 – Organize around value - Scaled Agile Framework, Business Agility Flashcards | Quizlet, Balancing the Dual Operating System - Scaled Agile Framework

 Story point size is a relative measure of the effort and complexity involved in implementing a user story. It is not based on the team size, the number of days it will take, or the priority of the story. Rather, it is based on the comparison of the story with other stories of similar or different sizes. Story points help teams estimate how much work they can complete in an iteration, based on their past performance and current capacity. Story points also help teams plan and track their progress at the program level, by aligning the features and capabilities with the stories that implement them. References: Story - Scaled Agile Framework, A Guide to Story Point Estimation - DEV Community, What should be taken into account when estimating Story poin - Madanswer

Spending time “in the zone” means being fully immersed in a task that is challenging, engaging, and enjoyable. This state of flow is associated with higher levels of creativity, innovation, and performance1. According to SAFe, optimizing the time spent in the zone for individuals and teams makes a substantial difference in ART productivity2. The other options are not directly related to the concept of flow, although they may be influenced by it. Reducing queue lengths, refining productive collaboration, and making work in process visible are all aspects of visualizing and limiting WIP, which is another flow accelerator3.

According to SAFe, a SAFe Portfolio is a set of value streams that delivers a continuous flow of valuable solutions to customers within a common funding and governance model. A SAFe portfolio aligns strategy to execution via a collection of Development Value Streams (DVS). Each DVS develops one or more Solutions necessary for the portfolio to accomplish its business mission and vision, operating under a shared governance model1. A DVS is a long-lived series of steps that an organization uses to deliver value to a customer or stakeholder2. A DVS can be internal or external, and it can span multiple ARTs and suppliers3. A DVS is not the same as a functional team, a solution, or a business unit, which are different ways of organizing work, products, or organizational structures. References: Portfolio - Scaled Agile Framework, Development Value Stream - Scaled Agile Framework, Value Stream - Scaled Agile Framework.

Iteration planning for Kanban teams is different from Scrum teams in that Kanban teams do not estimate their velocity, do not commit to service level agreements, and do not plan the Iteration in detail. Instead, Kanban teams use a flow-based process that allows them to pull work items from the backlog as they become available and deliver value continuously. However, Kanban teams still operate within the ART iteration cadence and often publish Iteration goals to align with the ART vision and objectives, as well as to communicate their priorities and dependencies to other teams and stakeholders. References: SAFe Team Kanban, Agile Iteration Planning Effectively

Customer Centricity is a mindset that helps organizations make decisions that are based on a deep understanding of its effect on customers and end-users. It motivates teams to focus on the customer, understand their needs, think and feel like them, build whole product solutions, and know their lifetime value. Customer Centricity is related to Design Thinking, which provides the tools and practices to support creating desirable products that are profitable and sustainable over their lifecycle. References: Customer Centricity - Scaled Agile Framework, Design Thinking - Scaled Agile Framework, What is Customer Centricity in SAFe® 5.0? - Praecipio

n: Product Management is responsible for defining desirable, viable, feasible, and sustainable solutions that meet customer needs and supporting development across the product life cycle. They align the product strategy, vision, and roadmap to the portfolio’s strategic themes and lean budgets. They also create, maintain, and adjust the program backlog, which contains the features and enablers that the Agile Release Train (ART) will implement. They work with customers, teams, and product owners to understand and communicate their needs and participate in solution validation. They also collaborate with system architects and the release train engineer to guide the ART toward successful delivery12. References: Product Management - Scaled Agile Framework, Agile Release Train - Scaled Agile Framework

The Product Owner (PO) is the Agile team member primarily responsible for maximizing the value delivered by the team by ensuring that the team backlog is aligned with customer and stakeholder needs1. The PO has content authority to make decisions at the User Story level during PI Planning, as they are the team’s primary customer advocate and primary link to business and technology strategy1. The PO also works with Product Management and other stakeholders to define the features and enablers that are part of the Program Backlog2. During PI Planning, the PO presents the team backlog, reviews and revises the draft plan, and defines and communicates the team PI objectives2. References: Product Owner, PI Planning

A technical exploration enabler is a type of enabler that supports research, prototyping, and other activities needed to develop an understanding of customer needs, including the exploration of prospective solutions and evaluation of alternatives1. A technical exploration enabler can be demonstrated by showing the knowledge gained by the exploration, such as the results of experiments, the insights from data analysis, the feedback from customers or stakeholders, the lessons learned from failures, or the recommendations for future actions2. Showing the knowledge gained by the exploration helps to validate the assumptions and hypotheses, measure the value and feasibility of the solution, and inform the decision-making process3. The other options are not valid ways to demonstrate a technical exploration enabler, as they either do not reflect the purpose of the exploration, or imply that the exploration is not necessary or valuable. References: Enablers - Scaled Agile Framework, How can a technical exploration enabler be demonstrated?, Principle #4 - Build incrementally with fast, integrated learning cycles - Scaled Agile Framework

= DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps joins development and operations to enable continuous delivery, which means delivering value to customers in the shortest sustainable lead time. Continuous delivery is achieved by creating a Continuous Delivery Pipeline (CDP), which is a high-performance innovation engine that consists of four elements: Continuous Exploration, Continuous Integration, Continuous Deployment, and Release on Demand. DevOps also helps to improve the quality, reliability, and security of the solution by applying practices such as testing, monitoring, and feedback throughout the CDP. References: = DevOps - Scaled Agile Framework, Continuous Delivery Pipeline - Scaled Agile Framework

SAFe recommends running a Retrospective on a cadence during the PI for SAFe Team Kanban Teams. A Retrospective is a team-level event that occurs at the end of each iteration, where the team reflects on how they are working and identifies improvement actions for the next iteration. A Retrospective helps the team pursue perfection by applying the Plan-Do-Check-Adjust (PDCA) cycle1. SAFe Team Kanban Teams also participate in other ART events, such as PI Planning, System Demo, and Inspect and Adapt2. References: 1: Retrospective - Scaled Agile Framework2: SAFe Team Kanban - Scaled Agile Framework

Differentiating business objectives are those that provide competitive differentiation and strategic advantage for the enterprise. They reflect the unique value proposition and vision of the enterprise and guide the portfolio strategy and decision-making. One example of differentiating business objectives is Strategic Themes, which are portfolio-level business objectives that connect a portfolio to the strategy of the enterprise. They are written in Objective and Key Result (OKR) format and influence the vision, budget, and backlogs for the portfolio, large solution, and program levels. They also provide business context and alignment for the agile teams and ARTs in the portfolio. References: Strategic Themes, SAFe 4.5 Reference Guide: Scaled Agile Framework for Lean Enterprises, How to use GOST + SAFe to increase your company’s agility