Send us a text

In this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the nuances of product backlogs in agile environments. They discuss the tension between emergent backlogs and fixed feature sets, the importance of backlog management, and various prioritization techniques, including "buy a feature" and impact-effort matrices.

This week's takeaways:

• Separate tactical (near-term) and strategic backlogs to reduce psychological pressure and maintain focus - avoid creating extensive long-term backlogs that will likely become irrelevant.
• Stakeholder prioritization must be balanced with technical constraints and team capabilities - product owners should communicate changes in delivery order transparently to maintain trust.
• Regular backlog refinement should include archiving rejected items instead of deleting them, helping teams avoid repeatedly addressing the same requests while keeping the active backlog manageable.

Ready to scale your agile practices? Tune in to more episodes on your favorite platform.

Send us a text

Join Peter Maddison and David Sharrock in this thought-provoking episode of Definitely Maybe Agile as they explore the evolution of leadership decision-making in modern organizations. They dive deep into how traditional leadership models are being challenged by today's business environment and discuss the crucial shift from control-based to collaborative decision-making approaches.

This week´s takeaways:

• Executive decision-making challenges often stem from two distinct factors: emotional intelligence issues (dealing with unprepared stakeholders) and critical thinking problems (legitimate exploration of complex issues).
• The traditional "highest paid person's opinion" (HiPPO) approach to decision-making is becoming increasingly dangerous in today's rapidly changing business environment, where the speed of market changes demands faster and more distributed decision-making processes.
• Modern leadership requires a fundamental shift from centralized control to distributed authority, with leaders focusing on creating frameworks that enable lower-level decision-making while maintaining visibility of outcomes.

🎧 Want to Transform Your Leadership Approach? Subscribe to Definitely Maybe Agile on your favorite podcast platform

Send us a text

In this episode of Definitely Maybe Agile, Peter Maddison and David Sharrock explore the evolving complexities of calculating the total cost of ownership (TCO) in modern software development and delivery.

This week´s takeaways:

• TCO fundamentals remain unchanged, but the environment for calculating and applying TCO has become more complex.
• Organizations must distinguish between strategic proprietary development and commoditized solutions, using tools like Wardley mapping to identify where to invest versus reduce costs.
• Understanding and defining system boundaries is crucial for accurate TCO calculation - using approaches like value chain mapping, value stream mapping, or domain-driven design helps identify hidden costs and dependencies.

Subscribe to Definitely Maybe Agile on your favourite platform and join Peter and David as they unpack the challenges of digital transformation at scale.