Free Practice Questions for Scrum SAFe-Practitioner Exam

SAFe Team Kanban is a method that enables teams to manage their flow of work using a visual board and a set of policies. It is especially suitable for teams that have unpredictable or interrupt-driven work, such as maintenance, support, or operations teams1. SAFe Team Kanban helps teams to visualize their work, limit their work in progress (WIP), measure and improve their flow, and implement feedback loops2. Team A is a maintenance team that cannot always predictably plan their work. They like to meet daily to review the needs of the system and plan for how they can quickly address those needs during the workday. Therefore, SAFe Team Kanban is the most appropriate SAFe Lean-Agile method for Team A to plan and execute their work. References: Team Kanban - Scaled Agile Framework, SAFe Lean-Agile Principles - Scaled Agile Framework

SAFe Team Kanban is a method that helps teams facilitate the flow of value by visualizing workflow, establishing Work In Process (WIP) limits, measuring throughput, and continuously improving their process1. It is suitable for teams that have a rapid and uneven arrival of work and fast-changing priorities, such as maintenance teams2. The other options are not appropriate for Team A’s context. SAFe Platform Team is organized around developing and supporting platforms that provide services to other teams3. SAFe Enabling Team is organized to assist other groups with specialized capabilities and help them become proficient in new technologies4. SAFe XP Team is an Agile Team method that combines the power of Scrum with Extreme Programming (XP) practices and operates within the ART iteration cadence5.

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 PI Planning event involves everyone in the program, including the Business Owners, Product Management, System Architects, Agile teams, Scrum Masters, Product Owners, Release Train Engineers, and other relevant roles. The PI Planning event also fosters collaboration, communication, and commitment among the participants, 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

 On day two of PI Planning, management presents adjustments based on the previous day’s management review and problem-solving meeting. The management review and problem-solving meeting is a session where the management team reviews the draft plans and objectives from the teams, identifies risks and dependencies, and resolves any issues that may affect the ART’s ability to deliver value. One possible type of adjustment they could make is to adjust the business priorities based on the new information and feedback from the teams. This could involve reprioritizing the features in the program backlog, changing the weight or value of some objectives, or adding or removing some stretch objectives. These adjustments are communicated to the teams during the second planning day, so they can finalize their plans and objectives accordingly. References: PI Planning - Scaled Agile Framework, PI Planning and the Management Review - Part 1 | Ivar Jacobson International

A team’s commitment at the end of PI Planning is based on the PI Objectives that they have defined and negotiated with the Business Owners and other stakeholders. PI Objectives are SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) goals that reflect the expected business and technical outcomes for the upcoming PI. A team does not commit to uncommitted objectives, which are stretch goals that may or may not be achieved depending on the actual capacity and velocity of the team. Uncommitted objectives are not included in the vote of confidence or the business value assessment. References: PI Objectives - Scaled Agile Framework, SAFe® for Teams - Know Your Role on an Agile Team | Scaled Agile, Exam Study Guide: SP (6.0) - SAFe® Practitioner - scaledagile.com

System Demo is a critical event that provides stakeholders an integrated view of the new features delivered by the Agile Release Train (ART) over the past iteration. It offers the ART a fact-based measure of current, system-level progress within the Program Increment (PI). It also enables fast feedback and learning cycles, which help the ART build the right solution and improve quality. The System Demo takes place as close to the end of the iteration as possible, ideally the next day. It requires implementing the scalable engineering practices necessary to support Continuous Integration across the ART12. References: System Demo - Scaled Agile Framework, Sample Test: SAFe® Practitioner - scaledagile.com

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

= According to SAFe, a Feature should be sized to fit into one Program Increment (PI), which is a timebox of 8 to 12 weeks, typically consisting of 4 to 6 iterations1. A Feature is a service provided by the system that fulfills some important stakeholder needs and delivers business value2. A Feature should be small enough to be completed by a single Agile Release Train (ART) within a PI, but large enough to provide significant and measurable value3. A Feature should also be testable, demonstrable, and deployable4. References: = 1: Program Increment - Scaled Agile Framework; 2: Features and Capabilities - Scaled Agile Framework; 3: Right-Sizing Features for SAFe Program Increments - Scaled Agile Framework; 4: Feature - Scaled Agile Framework

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?

During the second team breakout session, the teams finalize their plans and objectives for the upcoming PI. They also review and adjust their load and capacity based on the feedback from the draft plan review. The teams then commit to do everything they can to meet the agreed-to-objectives, which are captured in the SMART format (Specific, Measurable, Achievable, Relevant, and Time-bound). References: PI Planning - Scaled Agile Framework, PI Planning - Scaled Agile Framework

 The Agile Release Train Sync is a weekly meeting that synchronizes the ART stakeholders and provides visibility into the ART’s progress and impediments1. The Scrum Masters represent their Agile teams, provide updates on their status, relay questions, and help address challenges. They safeguard the team’s needs and effectiveness2. The visibility that Scrum Masters provide during the Agile Release Train Sync is mainly into the progress and impediments of their teams, such as the completion of features, stories, and enablers, the resolution of dependencies, the identification of risks and issues, and the demonstration of value3. The other options are not the primary focus of the Scrum Masters’ visibility during the Agile Release Train Sync. References: Agile Release Train - Scaled Agile Framework, PRACTICE TEST: SAFe 4 Practitioner Certification Flashcards - Brainscape, Agile Release Train Sync Meetings: Maximizing Success - Dee Project Manager