Scrum SAFe-Practitioner Dumps Questions Answers

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 team’s initial capacity is calculated by multiplying the number of team members by the number of hours per day they are available for work, and then by the number of days in the iteration. In this case, the team has six members (two testers, three developers, and one Scrum Master/Team Coach), and the Product Owner is split between two teams, so they only count as half a member. Assuming they are available for eight hours per day and the iteration is five days long, the team’s initial capacity is:

Initial capacity=(6+0.5)×8×5=260

However, this is not the final answer, because the team also needs to account for the time spent on non-value-added activities, such as meetings, emails, and other overhead. According to the SAFe for Teams course, a typical team spends about 15% of their time on these activities, so they need to subtract that from their initial capacity. Therefore, the team’s final capacity before calculating for time off is:

Final capacity=260×(1−0.15)=221

To get the answer in terms of story points, the team needs to divide their final capacity by the average number of hours per story point. According to the SAFe for Teams course, a typical team has an average of 5.5 hours per story point, so the team’s capacity in story points is:

Capacity in story points=5.5221​≈40

Therefore, the correct answer is C. 40.

 Empathy maps are a design thinking tool that promotes customer identification by helping teams develop a deep, shared understanding of others. They enable teams to imagine what a specific persona is thinking, feeling, hearing, and seeing as they use the solution. Empathy maps help teams to design with empathy, which is a key behavior of customer centricity. Empathy maps can be used to explore different aspects of the problem and solution space, and to validate assumptions and hypotheses about the customer’s needs and preferences. References: Design Thinking, Customer Centricity