Publications

If you try find a definitive description of ‘The Spotify Model’ you will most likely end up frustrated. There are some old videos and blog posts, and lots of internet articles claiming that it isn’t a ‘proper’ framework and that even Spotify doesn’t use it. Yet, it is reported as the fourth most popular scaled agile framework according to the 15th State of Agile Report and there are thousands of companies claiming to be using it.  So, what is it? And if you want to adopt it, where do you start?

Epics have a lifecycle, they don’t magically appear fully formed. There is work to be done to progressively elaborate a business case and if the Epic is approved then there is further work to progress the Epic through implementation. In this post we’ll explore the Portfolio Kanban that visualises the lifecycle of an Epic and look at some of the decisions that influence the Epic’s progress through its lifecycle. In subsequent posts we’ll look at the processes that can inform those decisions.  

Epics have a lifecycle, they don’t magically appear fully formed. There is work to be done to progressively elaborate a business case and if the Epic is approved then there is further work to progress the Epic through implementation. This post explores the Lifecycle of an Epic and the states it progresses through in that Lifecycle.

Serious games are games that do not have entertainment, enjoyment or fun as their primary purpose. There are many examples of serious games in the video game industry, but any game that has a serious purpose can be a serious game. For instance; card games, team games, sorting games or timed activities. The book and website Gamestorming describes dozens of ‘games’ that are played in person and address business problems in creative, engaging and most importantly, effective ways. Some examples you may recognize are SWOT Analysis, Brainwriting, World Café and Affinity Mapping.

This article explores the synergy of Scrum and Essence, a domain model of software engineering processes, intending to become a common ground for software development methods, bringing clarity into the composition of methods from individual practices.

What do we mean by Quality? The word Quality is commonly used in software development, but it isn’t always clear what is meant by it. Teams create Definitions of Done, configure thresholds in their CI/CD pipeline, write performance tests and agree service level agreements, but are these sufficient for the level of Quality the customer expects?

This post is an exploration of whether you should be estimating Expense or Effort. Both are required from different processes within the Scaled Agile Framework and there is a route to convert between the two, but which should be the principal estimate and which the derivation?

In a flow based environment where teams pull work towards them an Epic can't dictate to the teams, which makes Epic roadmapping a challenge. This post explores the challenges of Epic Roadmaps and process through which they can be generated.

Developing technical solutions is hard work. To make things easier, a number of practices and frameworks have become popular. They provide structure and guidance to help teams develop their solutions more successfully. I’m thinking of things like Scrum, the Kanban Method, User Stories and Test Driven Development. However, doing these things well is also hard work. Despite in depth training, books, conferences and certificates, people still struggle to apply these practices well. Jeff Sutherland, co-founder of Scrum estimates that 58% of Scrum implementations fail...

Portfolios need to build roadmaps to facilitate forecasting activities and to assess time-criticality during prioritisation. This post covers some practical facilitation techniques for Roadmapping activities.