Leading indicators – easy to understand but hard to master in practice

A comparing product development using a lagging indicator to evaluate progress and one using a leading indicator.
The core of agile development - it should be at the heart of all product development efforts for that matter - is iteratively moving forward. We need to understand the impact of what we are doing without waiting for too long. For this reason, Product teams need to use leading indicators so that they can immediately measure the effectiveness of their product development.

Sprinting to success with Scrum: how to make sure it is done effectively

In its essence, agile product development is a mindset for dealing with an uncertain environment. The best way to do that is to find the path forward one step at a time. This means delivering frequently, observing how users react and interact with the product, and adjusting the approach for the next iteration according to the feedback and observations. Scrum is the manifestation of exactly this approach within a project management method.

The sprint retrospective – why is it needed and what are best practices?

A picture of the word Change, symbolizing that a retrospective means changing how we work.
Along with the refinement, I find the sprint retrospective to be the most important ceremony within the Scrum Framework. It embodies one of the main features of agile product development, iterative improvements. This is, in my view, at the heart of agile product development. Iteratively improving not only applies to the product itself but also to the developmental process, the method of collaboration, and used frameworks.