On Driving Value with Sprint Goals | Maarten Dalmijn, Agile Product Management Expert, Consultant & Author
Jun 13, 2023
auto_awesome
Agile consultant Maarten Dalmijn discusses the messy reality of product roadmaps and the importance of sprint goals. They cover the Cynefin Framework, adjusting along the way, and mediating opposing goals. The interplay between product goals, Scrums, and OKRs is explored. Dalmijn also shares personal experiences with implementing sprint goals and finding joy in work.
Scrum should be practiced with flexibility and adaptability, focusing on continuous learning and making changes.
Applying military-inspired approaches to agility can enhance adaptability and decision-making in software development.
The development and execution of product roadmaps can provide valuable insights into team culture and should prioritize flexibility and collaboration.
Deep dives
The importance of separating how Scrum is done in practice and how it should be done
It is crucial to understand the difference between how Scrum is practiced and how it should ideally be done, as this can greatly impact its effectiveness. In many cases, teams become too rigid in their adherence to Scrum practices, leading to less flexibility and adaptability. Embracing the messy and uncertain nature of Scrum and focusing on continuous learning and making changes is key.
The value of applying lessons learned from the military in agile software development
The military offers valuable insights into dealing with uncertainty, complexity, and decision-making in the moment with limited information. Applying these lessons to software development can provide useful strategies for navigating complex and uncertain situations. By incorporating military-inspired approaches to agility, teams can benefit from increased adaptability and improved decision-making.
The connection between product roadmaps and team culture
An effective team culture can be reflected in the development and execution of product roadmaps. The way product roadmaps are created and implemented can provide valuable insights into the team culture within a company. A focus on flexibility and collaboration in roadmapping can lead to better outcomes and a more empowered team.
The dangers of adhering too strictly to plans and goals in Scrum
Adhering too strictly to plans and goals in Scrum can lead to negative outcomes such as rigidity, reduced adaptability, and an emphasis on completing tasks rather than delivering value. It is important to embrace the essence of Scrum, which is continuous learning, embracing change, and prioritizing value delivery over following a set plan.
The significance of having a clear sprint goal
Having a clear sprint goal is essential for providing focus and direction to a Scrum team. The sprint goal serves as the commander's intent, guiding the team's actions and decisions throughout the sprint. It ensures that the team is aligned and working towards a common objective, enabling flexibility, adaptability, and delivering value.
If you want to know what kind of team culture really exists at a company, look very carefully at how product roadmaps are developed and executed. That, says Jenny Herald’s guest on this episode of Dreams With Deadlines, is where you can see the “messy, bloody war” that may or may not be going on behind the scenes.
Agile consultant Maarten Dalmijn, author of a forthcoming book about using sprint goals to deliver better products more efficiently, shares fascinating insights on project management and how to optimize it.
Key things discussed
Why agile software development isn’t about delivering more stuff more quickly.
How three common gaps in understanding, effort and results hobble projects.
What the Cynefin Framework is and how to leverage its domains in managing complexity – along with chaos.
Why less up-front planning and more adjustment along the way enables nimble project management and a quicker path to desired outcomes.
Ways to identify and mediate opposing goals that can mire projects in constraint and micromanagement.
The interplay between product goals, Scrums and OKRs.
Show Notes
[00:03:27] Diving into the “why” behind Maarten’s decision to write his soon-to-be-published book – or any book – at this point in time.
[00:04:30] What Scrum can look like (flexible and supportive of change) versus what people think it should be.
[00:06:48] Why being agile is about more than just shipping more stuff faster. About Maarten’s effort to define what makes a successful Scrum, the outputs that drive desired business and customer outcomes and obstacles commonly encountered.
[00:09:32] Maarten shares in the book a personal story about a childhood exercise on a Dutch island that parallels the journey of discovery that is software development.
[00:13:26] A closer look at the three gaps, a model originated by leadership strategist Stephen Bungay, including:
The Knowledge Gap: What we know is less than we’d like to know.
The Alignment Gap: What we’re likely to do versus what we actually do.
The Effects Gap: The difference between desired results and actual outcomes.
[00:15:51] How to avoid getting lost in “the fog of beforehand,” which can result in overcompensation and analysis paralysis that constrains or slow decision-making.
[00:18:28] Humble Planning: It’s not about planning less. It’s about reducing upfront planning in order to leave room for critical adjustments later in the project life cycle.
[00:20:17] About Dave Snowden’s Cynefin Framework, designed to help manage complexity (and chaos) in times of crisis – a sort of field guide for decision-makers.
[00:21:19] Delineating the domains encompassed by the Cynefin model and how they apply in a software development context:
Confusion
Clear
Complicated
Complex
Chaotic
[00:23:40] Understanding self-imposed friction and how rigid plans can lead to massive breakdowns in desired business outcomes.
[00:27:16] How opposing goals fracture teams and slow – if not defeat – mutually desirable results while team alignment (internally and with partners) supports success.
[00:30:21] Navigating “Roadmap Hell” and how a traditional project management mindset yield binary, inflexible processes that create conflict and self-defeat.
[00:32:45] Want to see how agile a company culture really is? Look at their mindset around road mapping – that’s where business and IT really come together and reveal the turf wars and rigidity!
[00:34:06] Teasing out Part II – the “beating heart” – of Maarten’s book: Sprint Goals:
They depend on a clear understanding of intent, what the team is trying to achieve and why it matters.
It’s key to integrate foundational sprint goals into every Scrum.
OKRs have a role to play in helping to prevent or break the feature factory loop.
[00:36:32] Understanding the interplay between product goals, Scrums and OKRs; how they fit together in multi-faceted ways with multiple protocols.
[00:38:42] About applying North Star Metrics – when and how they work and the constellation of factors that can influence measures and strategic adjustments.
[00:41:42] What happens when companies don’t use sprint goals?
It disempowers teams.
It restricts information, understanding and decision-making ability.
It reduces flexibility.
It leads to technical debt and prioritizing speed over quality.
[00:44:42] Quick-Fire Questions for Maarten:
What is Your Dream with a Deadline? Finishing up his book secure in the knowledge that he has delivered what he intended – and then some!
How do you define a good sprint goal? It includes everything in the acronym FOCUS: Fun, Outcome-oriented, Collaborative, Ultimate and Singular.
What’s the takeaway he most wants for those who read his book? More joy, a sense of empowerment, flexibility, freedom, less effort that yields more results!
Maarten Dalmijn worked with award-winning start-ups, scale-ups and corporations in various roles before taking the leap as an independent Product Management, Agile and Scrum consultant. By blending the world of Product Management and Agile, Maarten helps teams beat the Feature Factory and uncover better ways of delivering value together.