Using narrative to explain technical work

As a ScrumMaster one of the tasks I’ve found hardest in the past is helping my team in making a case for technical tasks, and then after they’ve done the work helping them present the results & benefits of technical work to stakeholders. I’ve also sometimes felt like there must be a more engaging way to clearly explain to people outside the team how we’re: constantly trying new things, changing the way we work, and changing the way we deploy code.

Last week I found a really interesting slide deck from Martin Fowler & Thoughtworks on the The Architecture of Morrisons OrderPad amongst the 50 odd tabs I perpetually have open, I think it’s brilliant.

Continue reading “Using narrative to explain technical work”