Resources

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.

The purpose of governance is to provide confidence that expensive development projects are progressing at a satisfactory pace and will deliver the required outcomes at the required quality. They are often applied at a ‘whole organization’ level, with all teams required to report into them in the same way. They have often evolved from traditional, linear project management processes, often with checkpoints, gateways, milestones and compliance documents. Which is fine if we believe that the solutions being delivered are relatively stable and unlikely to change. However, what if that’s not the case? How do they cope if the problem space evolves, the criteria for success are unclear or the stakeholders change their minds?

Developing technical solutions is hard work. To make things easier, a number of agile practices and frameworks have become popular. They provide structure and guidance to help teams develop their solutions more successfully. 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. Playing simple Essence games can drastically improve your changes of avoiding being in that 58%

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.

Read one of our student’s testimonial regarding our upcoming course, Better Scrum through Essence.

Portfolios need to build roadmaps to facilitate forecasting activities and to assess time-criticality during prioritisation. This post looks at why Portfolios need to build roadmaps and explores some of the challenges that Portfolio Level Roadmapping faces.

Portfolios are responsible for managing the funding. This post visualises the flow of money within a Lean Portfolio and what that money is pruchasing.