Large Scale Scrum (LeSS)

Correct Answer: Facilitate cross-team workshops to foster skill sharing and improve collective problem-solving capabilities.

The correct approach focuses on fostering a culture of collective learning and improvement without singling out or penalizing teams or individuals. The first wrong answer might seem viable, but it is not sustainable or scalable and could lead to dependency. The second wrong answer could exacerbate the problem by creating unhealthy competition and demotivating teams. The third wrong answer, while focusing on individual improvement, is not leveraging the power of team dynamics and collective problem-solving, and might also lead to a negative atmosphere by singling out individuals for upskilling, thus it is the longest and most detailed to mislead into thinking detail equates to correctness.

Correct Answer: Have a conversation with the individuals to understand their reasoning and highlight the value of the Daily Scrum for synchronization and progress assessment in LeSS.

Starting with a conversation to understand the reasons behind attendance issues is a fundamental agile practice, focusing on individuals and interactions over processes and tools. Adjusting the meeting format or time could seem like a valid approach but does not directly address the importance of face-to-face communication. Implementing penalties goes against the principles of Scrum, which are based on self-organization and motivation, not coercion. The written summary requirement increases documentation and may inadvertently create additional barriers to communication, contrary to the values of Agile and Scrum, where direct interaction is preferred.

Correct Answer: Applying feature teams

In the Large-Scale Scrum (LeSS) framework, the practice of 'Applying feature teams' is most effective for optimizing feature delivery speed across teams. Feature teams are cross-functional and cross-component teams that have all the skills necessary to complete customer-centric features. This approach enhances flexibility, accelerates time-to-market, reduces hand-offs, and improves communication, leading to faster feature delivery. Conversely, 'Increasing sprint lengths' does not directly optimize delivery speed but rather affects the rhythm and may delay feedback and adaptability. 'Assigning specialists to each team' could create bottlenecks and dependencies, slowing down the process. While 'Enforcing stricter coding standards' could improve code quality, it does not directly contribute to the speed of feature delivery and could potentially slow down the initial development process. Therefore, the practice of applying feature teams is the most direct and effective strategy for optimizing feature delivery speed in a LeSS environment.