Mastering Complex Situations in Scrum

Sometimes it seems like in the 'normal' Scrum world, you're just building small software increments with clearly defined user stories and priorities. But what if the demand isn't clear at all, stakeholders have conflicting interests, or the technology doesn't behave as expected? Then you're dealing with complexity. At Spark Academy we've experienced that it's precisely in this chaos that the true power of Scrum comes to life, provided you approach it consciously.

‍

Complexity and Scrum: a perfect match?

Scrum is designed for complex and uncertain environments. At its core, it's an empirical approach: working in short cycles, inspecting, and adapting based on feedback. This makes it ideally suited for situations where you don't know the best solution beforehand.

‍

Real-world example: An organization wants to 'do something with artificial intelligence' but has no idea what that concretely entails. Through short sprints, small experiments, and close collaboration with the business, the team gradually explores what is and isn't possible. This way, a clearer picture emerges over time.

‍

How to recognize complex situations?

• High uncertainty: Requirements are not (yet) clear, or they change constantly.
• Numerous stakeholders: Each with their own goals and often limited coordination.
• Technical unfamiliarity: New technologies or ecosystems you haven't mastered yet.
• Organizational changes: Mergers, reorganizations, or shifts in power and politics.

In literature, you can refer to the Cynefin model (Dave Snowden) : it distinguishes between simple, complicated, complex, and chaotic situations. Scrum is particularly well-suited for the latter two categories.

‍

Strategies for Mastery

Start small, validate, and learn

• Don't create a huge spec with everything you think you need. Focus on a Minimum Viable Product (MVP) and test if you're on the right track.

‍

Actively involve stakeholders

• Complexity increases when stakeholders don't communicate or understand each other. Ensure frequent demos, reviews, and discussions to bring all perspectives to the table.

‍

Dare to experiment

• In a complex situation, there's no guarantee that something will work. So, experiment deliberately. Keep your sprints short and continuously learn from what succeeds and what doesn't.

‍

Give the team space

• A self-organizing and cross-functional team is crucial. People need diverse expertise and perspectives to tackle unexpected obstacles together.

‍

Protect the focus

• Especially in a complex context, there's a danger of wanting to do everything at once. Keep the sprint backlog manageable and continue to prioritize.

‍

Pitfalls

Rushing towards 'certainty'

• In a complex situation, the truth is constantly shifting. Don't try to nail down everything 100%, but work with what you do know.

‍

Lack of long-term vision

• Scrum is iterative, but without any long-term goal, you'll lose the common thread.

‍

Micromanagement

• If leaders or managers try to micromanage every sprint, they stifle the creativity and flexibility that are precisely what you need in complex projects.

‍