What SP-SAFe-Practitioner Questions and Answers feature?

Respect for People is one of the four SAFe Core Values. It means that the enterprise fosters a culture of mutual influence, trust, empowerment, and collaboration among all the people involved in delivering value, including customers, employees, partners, and suppliers. Respect for People also implies that the enterprise values diversity, inclusion, and psychological safety, and that it treats people as the most important asset. Respect for People supports the following practices in SAFe1:

• Turn mistakes into learning moments. Mistakes are inevitable in complex and uncertain environments, and they provide opportunities for learning and improvement. Instead of blaming or punishing people for making mistakes, the enterprise encourages them to share their learnings, experiment with new ideas, and apply the Plan-Do-Check-Adjust (PDCA) cycle.
• Create a trust-based environment. Trust is the foundation of effective collaboration and high performance. The enterprise builds trust by being transparent, honest, supportive, and accountable. It also empowers people to make decisions, take ownership, and self-organize around value delivery.
• Visualize work. Visualization helps people see the flow of value, identify bottlenecks, dependencies, and waste, and collaborate on solutions. The enterprise uses various tools and techniques to visualize work, such as Kanban boards, Cumulative Flow Diagrams, Program Boards, and Value Stream Maps. References: 1: Respect for People and Culture - Scaled Agile Framework

The confidence vote is a measure of the teams’ and ARTs’ belief in their ability to deliver the established PI objectives. It is conducted at the end of the PI planning event, after the teams have presented their plans and identified the risks. Each person votes using their fingers (fist of five) or a digital tool for remote events. The scale is as follows:

• 5: I am confident we can meet or exceed our objectives
• 4: I am confident we can meet our objectives
• 3: I think we can meet our objectives, but I have some concerns
• 2: I doubt we can meet our objectives, and I have major concerns
• 1: I am sure we cannot meet our objectives

The purpose of the confidence vote is to surface any issues or impediments that might prevent the teams from achieving their goals. It also helps to align the expectations of the stakeholders and the teams. If the average vote is below 3, the teams and the ARTs need to revisit their plans and address the root causes of the low confidence. The confidence vote is repeated until the average vote is 3 or higher, or until the timebox expires. References: PI Planning - Scaled Agile Framework, Confidence Vote - Scaled Agile Framework, Confidence Vote in PI Planning: Role and Benefits - Dee Project Manager

Understanding the optimum batch size is crucial for teams to ensure that value flows efficiently through the development pipeline. By optimizing batch sizes, teams can reduce the cycle time and improve the delivery of value to customers, aligning with the Lean-Agile principles of delivering value incrementally and continuously. The reason for the faster speed is obvious. The reduced variability results from the smaller number of items in the batch1.

The image you sent shows a table of assessment results for different categories related to agile project management. The category “Flow” has a score of 86%, which indicates that the team is performing well in terms of delivering value in a continuous and smooth manner. However, there may be some room for improvement in other categories, such as “Team backlog” and “PI Planning”, which have lower scores of 50%. These categories are related to the planning and prioritization of work items, which affect the batch size and the flow of value. The team may benefit from applying some of the practices and tools suggested by SAFe, such as Kanban boards, WIP limits, and PI Objectives, to optimize their batch size and increase their flow efficiency234. References: Visualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengths, Team Flow, Principle #6 – Visualize and limit WIP, reduce batch sizes, and manage queue lengths, Simplicity Factor: Batch Size

A screenshot of a computer Description automatically generated