Scrum SAFe-Practitioner - SAFe Practitioner Exam (6.0)

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

n: The Team Sync is a short meeting (usually 15 minutes or less), typically held about daily, to inspect progress toward the team goals, communicate, and adjust upcoming planned work1. The Team Sync helps the team members align their activities, identify and resolve impediments, and collaborate effectively. The Team Sync is also an opportunity to share information, celebrate achievements, and foster team spirit. The other options are incorrect because:

A. The Team Sync is not the place to identify ART PI risks. Risks are identified and managed at the Program level, using the ROAM board and other tools2.

C. The Team Sync is not the place to identify Iteration goals. Iteration goals are defined and agreed upon during the Iteration Planning event, which happens at the beginning of each Iteration3.

D. The Team Sync is not the place to make announcements to the entire ART. The Team Sync is a team-level event, where only the team members and the Scrum Master participate. Announcements to the entire ART are made during the ART Sync, which is a program-level event that happens weekly or biweekly4. References: 1: Team Sync - Scaled Agile Framework, 2: Program Risks - Scaled Agile Framework, 3: Iteration Planning - Scaled Agile Framework, 4: ART Sync - Scaled Agile Framework

 Culture is the first element of the CALMR approach to DevOps in SAFe. It refers to the shared mindset and values that support successful DevOps adoption. Culture in SAFe is influenced by the Lean-Agile principles and practices that guide the entire framework. Culture in DevOps requires customer-centricity, collaboration, trust, empowerment, learning, and feedback among all the stakeholders involved in the value stream. Culture also fosters a shift-left mentality, where operational and quality concerns are addressed early and often in the development process. Culture is the foundation for the other elements of CALMR: automation, lean flow, measurement, and recovery. References: CALMR - Scaled Agile Framework, The CALMR Approach to DevOps [Complete Guide] - KnowledgeHut

 Business Owners assign business value to team PI Objectives to provide a common language for communicating with business and technology stakeholders, create the near-term focus and vision, enable the ART to assess its performance and the business value achieved, communicate and highlight each team’s contribution to business value, expose dependencies that require coordination, and provide an input to execution considerations. By assigning business value, Business Owners empower teams to make decisions around work that aligns with the business goals and priorities. References: PI Objectives, Business Owners, Your Guide to Writing Great Iteration and PI Objectives, PI Objectives - Easy Agile, Why do business owners assign business value to PI objectives?

Learn more

1blob:https://www.bing.com/08a92a67-4d7c-410c-82a9-cafd0c3ce0c2

scaledagileframework.com2blob:https://www.bing.com/08a92a67-4d7c-410c-82a9-cafd0c3ce0c2

scaledagileframework.com3blob:https://www.bing.com/569f3bf9-d7d0-4a63-9a40-bb3f52b4d112

scaledagile.com4blob:https://www.bing.com/e7b94a1d-0074-4150-a887-6152c0190872

help.easyagile.com5findanyanswer.com

Organize around value is one of the 10 SAFe Lean-Agile Principles that guide the implementation of SAFe in any context. It states that enterprises must align their people, processes, and technology to the full and continuous flow of value that delivers customer and business outcomes. This principle helps enterprises to eliminate silos, reduce handoffs, improve collaboration, and optimize value streams. It also enables faster feedback, shorter lead times, higher quality, and better economics. References: SAFe Lean-Agile Principles, Organize Around Value, Exam Study Guide: SP (6.0) - SAFe Practitioner

 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

The PO’s best course of action is to communicate the status of the Iteration to all stakeholders, including the other teams on the Agile Release Train (ART), the Release Train Engineer (RTE), the System Architect/Engineer, the Product Management, and the Business Owners. This will help to align expectations, manage dependencies, and mitigate risks. The PO should also collaborate with the team and the stakeholders to prioritize the remaining work and identify the most valuable Stories to deliver by the end of the Iteration. The PO should not defer acceptance testing to the next Iteration, as this would violate the Definition of Done and compromise the quality of the system increment. The PO should not have an emergency Iteration Planning meeting, as this would disrupt the cadence and synchronization of the ART and waste time and resources. The PO should not stop the current Iteration and plan a new Iteration with the new knowledge, as this would also disrupt the cadence and synchronization of the ART and create confusion and uncertainty.

 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

Iteration Planning is a key event in the SAFe framework that occurs at the beginning of each Iteration. It is a timeboxed meeting where the Agile team collaborates to plan the work for the upcoming Iteration, based on the team backlog, the Iteration goal, and the team capacity. Iteration Planning enables fast learning cycles by allowing the team to inspect and adapt their work frequently, deliver value incrementally, and respond to changing customer needs and feedback. References: Exam Study Guide: SP (6.0) - SAFe® Practitioner, Planning the Iteration, Executing the Iteration

Refactoring is the process of improving the design and structure of existing code without changing its external behavior. It is a quality practice for software development because it helps to reduce technical debt, improve maintainability, readability, and testability, and enable faster delivery of value. Refactoring is one of the core engineering practices in SAFe, along with Test-First, Continuous Integration, and Pair Work. 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, Built-in Quality