The Delivery Manager Daily

I've reflected over the last three years to determine that no matter the framework, methodology or approach, it's always to try & tackle the real issues which are often left to just be...well...issues. There are often far too many people involved in a project, causing any mechanism you use for scale or communication to groan at the seams. Hybrid working just compounds this further. Let's tackle the problems, rather than adding something over the top to superficially 'improve' things. You can read my thoughts here https://www.mariosblog.co.uk/agile-sucks-balls-hybrid-aint-working-youve-way-too-many-people-on-your-project/

In this episode I talk about the Scrumble. If you use Nexus, buried deep within the Scrum user guide & in Ken Schwabers blog post form 2015 which is an interesting read in it's own right, the Scrumble is a way of pausing delivery in your project, when things are going wrong. Is it just a retro? Does it truly handle problems in projects or is it just a holiday for the Scrum teams? Let's find out. As always, thanks for listening, join in the conversation on Twitter @dm_daily - thanks for listening

I think its important to reflect on when things don't go to plan. No ones perfect, especially not me. So when recently one of my projects went wrong (thankfully a rare occasion nowadays) I wanted to reflect. As always get me on Twitter @mariodc or @dm_daily or check out the blog mariosblog.co.uk