Free Scaled Agile SP-SAFe-Practitioner Practice Exam with Questions & Answers | Set: 4

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]

 SAFe Team Kanban is a type of SAFe Agile Team that relies on a continually-refined Team Backlog as the primary input to drive value delivery. SAFe Team Kanban is a method that helps teams manage and improve the flow of value across the Continuous Delivery Pipeline. It is based on the principles of Lean and Kanban, which aim to optimize the system, limit work in progress (WIP), implement feedback loops, and empower the team. SAFe Team Kanban uses a visual board to track the flow of work from the Team Backlog to the Done state. The Team Backlog is a subset of the Program Backlog that contains the user stories, enablers, and defects that the team needs to work on. The Team Backlog is constantly refined and prioritized by the Product Owner, who collaborates with the team and other stakeholders to ensure that the most valuable and feasible work items are selected for implementation. References: Team Kanban - Scaled Agile Framework, Team Kanban - Scaled Agile Framework

The Agile Manifesto is a set of values and principles that guide the software development process. One of the values is “responding to change over following a plan”. This means that the team values the customer’s needs and feedback over the plan and process. The team embraces change as an opportunity to deliver better solutions and adapts to changing requirements and priorities. References: The 4 Values and 12 Principles of the Agile Manifesto - Smartsheet, 12 Principles Behind the Agile Manifesto | Agile Alliance

 The balance between emergent design and intentional architecture when building in quality is required for speed of development and maintainability. Emergent design is the practice of defining and evolving the architecture only as necessary to deliver the next increment of functionality, based on the feedback and learning from the previous increments. Intentional architecture is the practice of defining and implementing some upfront design guidelines and standards that enable the integration and evolution of the solution across multiple teams and domains. Both practices are implemented with enablers, which are technical items that support the development and delivery of features and capabilities. The balance between emergent design and intentional architecture allows the teams and the Agile Release Train (ART) to deliver value faster, with higher quality and lower risk, and to maintain and improve the solution over time12. The other options are not accurate descriptions of the balance between emergent design and intentional architecture, as they either do not reflect the benefits of both practices, or use terms that are not relevant to the SAFe context. References: Architectural Runway - Scaled Agile Framework, Built-In Quality - Scaled Agile Framework

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

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,

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.

Precisely specify value by product” is one of the five key principles of Lean Thinking, as defined by James Womack and Daniel Jones in their book “Lean Thinking”. It means that value should be determined by the customer’s needs and preferences for each specific product or service, rather than by the producer’s assumptions or standards. This principle helps to eliminate waste, optimize flow, and increase customer satisfaction. References: Lean-Agile Mindset, Lean Manufacturing, What is Lean?

Customer Centricity is a mindset that focuses on creating positive experiences for the customer through the full set of products and services that the enterprise offers. Customer-centric organizations deliver whole-product solutions designed with a deep understanding of customer needs. This results in greater profits, increased employee engagement, and more satisfied customers in the private sector. Nonprofits and the public sector (governments) can achieve the resiliency, sustainability, and alignment needed to fulfill their mission1. The purpose of Customer Centricity is to understand the customer’s needs and deliver solutions that meet or exceed them. References: 1: Customer Centricity - Scaled Agile Framework

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