“If the team is uncertain about how to achieve the sprint goal or if experimentation or prototypes need to be done, then the sprint should be shorter. Uncertainty implies that the work eventually required for the sprint might be significantly different from what was anticipated at the start. If this is the case, it’s better to change direction after two weeks than four.”
In this blog post, Samuli Heljo shares his experience about a Scrum team that transitioned to Kanban. It offers a lot of data about this experience and try to analyze the failures made and to come up with some solutions.
This article documents a team’s move to Agile using Team Foundation Server 2010, starting out with the Microsoft Solutions Framework Agile v5.0 process template and eventually switching to the Microsoft Visual Studio Scrum 1.0 template.
In this blog post, Whitney Johnson shares four simple steps to build trust with your collaborator.
Scrum teams often use user stories for backlog items. Unfortunately, one of the most important aspects of a story – its extremely short length – has been subtly transformed over time and user stories have lost their original essence and potency.
In this article, Bachan Anand explains that beyond the mechanics, the daily Scrum stand-up meeting checks how is the team progressing toward fulfillment of the sprint commitment, identifies concerns immediately and provides an opportunity to discuss corrective action.
In this blog post, Sean McHugh shares six practices to be a better product owner.
Scrum Expert Copyright © 2009-2026 Martinig & Associates