Product backlog refinement, sometimes known as product backlog grooming, is not a defined ceremony within the Scrum framework. Instead, it is detailed as an activity, and Scrum teams are encouraged to commit approximately 10 percent of their sprint time in carrying out this activity.

Good agile teams are disciplined about their documentation but are also deliberate about how much they do and when. In this article, we find a duo struggling to explain that while they won’t be fully documenting everything up front, they will actually be more fully documenting the entire project from beginning to end.

The last Agile Manifesto principle states that “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.” For Scrum teams, the sprint retrospective is therefore a key meeting for continuous improvement. The results are however not always satisfying. In his book “Essential Scrum“, Kenneth Rubin discusses the most common issues in sprint retrospectives that he has noticed in his Agile coaching experience.

A kaizen board is a simple yet powerful visual tool to add to your Agile tool kit. Based on Agile principles, the tool facilitates effective Agile retrospectives and prevents some of the more common sprint retrospective pathologies.

An Agile coach can ascertain a great deal about a Scrum team in 15 minutes. Observing a team's Daily Scrum can give us insight into the health of the Scrum process. A team's Daily Scrum is like the pulse of a human being. There is no chance that anyone could produce an exceptional performance with an unhealthy heart pulse, and neither could a Scrum team.

If delivering business value should be the main goal of a software development project, not all the developers’ activities are contributing to this objective. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein discusses how you should deal with bugs and the technical aspects of your software project.

The idea of self-organizing teams has been called the secret sauce of agile software development. This paper is an attempt to systemize how to think about and how to develop healthy self-organization.

Even if Agile was initially considered as an anarchic approach due to practices like self-organization, the reality is that it requires a lot of discipline. Metrics is an important tool to assess the continuous improvement efforts of Scrum teams. However, setting a good metric program is not obvious.

Often teams struggle with picking the right-sized user story. The story either ends up being too small and hence of no value to the user, or it ends up being too huge and doesn't get completed in the planned sprint.

Scrumban is a management framework that emerges when teams employ Scrum as their chosen way of working and use the Kanban Method as a lens through which to view, understand and continuously improve how they work. This article explains what Scrumban is and how the framework can improve your projects.