Scrum SAFe-Practitioner Actual Questions

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

 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

One of the steps for setting initial velocity is to assess the team’s capacity, which is the amount of time available for the team to work on the backlog items. The team members assess their availability, acknowledging time off and other potential duties that may reduce their capacity, such as meetings, training, support, etc. The team then calculates their capacity by multiplying the number of team members by the number of hours per day by the number of days in the Iteration. The team’s capacity is used as an input for estimating the initial velocity, which is the amount of work the team can complete in an Iteration. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Capacity Allocation, Velocity

An ART event is a meeting or ceremony that involves all the teams in an Agile Release Train (ART) and helps them align, collaborate, and deliver value. An example of an ART event is the Innovation and Planning (IP) Iteration, which is a two-week period at the end of each Program Increment (PI) that provides time for innovation, planning, and improvement activities. During the IP Iteration, teams can explore new ideas, work on technical debt, conduct hackathons, prepare for the next PI Planning, and conduct the Inspect and Adapt workshop. References: Agile Release Train, Scaled Agile: ART Events Overview, Innovation and Planning Iteration