In this episode, Peter Maddison and David Sharrock discuss when not to use Scrum, the popular agile framework for software development. They explore scenarios where Scrum may not be the best fit, such as when an organization is resistant to change, lacks collaborative work, or operates in a highly complex environment with many dependencies and high failure costs. The conversation highlights the importance of understanding the problem, organizational context, and underlying assumptions before adopting any framework.This week's takeaways:Assess the organization's readiness and openness to change before adopting Scrum, especially if past attempts have failed or if it is seen as a quick fix.Scrum thrives in collaborative environments; if the work is highly individualistic, Scrum may not be suitable.A cautious approach is required in complex and high-risk environments, potentially adapting Scrum or considering other frameworks.Tune in to gain a nuanced understanding of how to navigate agile frameworks in complex environments and make informed decisions for your teams.

Ver todos los episodios