6/11/2007 by John Hill
For Scrum to work, teams must be truly empowered. Unfortunately, far too many teams are operating at much less than capacity and are failing. Find out how to cure a team that is suffering from a power shortage.
6/4/2007 by Esther Derby
In part one of a two-part follow-up to the highly debated, "Should a ScrumMaster Give Performance Appraisals," Esther Derby makes the case for eliminating performance reviews altogether.
5/29/2007 by Mark Randolph
Our series on Scrum smells continues with a discussion of what to do when developers fail to attend daily Scrums.
5/21/2007 by Bob Schatz
What's the secret ingredient missing from most sprint reviews? The user stories and use cases you probably discarded may be the greatest story never told.
5/18/2007 by Aaron Conoly
A while ago I wrote about my experiences with Scrum and a little helper I like to call “Posty the Post-It note.” Ok, so I don’t actually call it that, but I do use the Post-It extensively when I’m scrumming.
5/7/2007 by Mike Cohn
When scaling Scrum to large projects, the scrum of scrums meeting can be a vital tool for keeping your teams in sync and out of each other's way. Mike Cohn gives some pointers on how to run and coordinate these important Scrum meetings.
4/30/2007 by Benoit Houle
A ScrumMaster can make or break a release. Yet how do you choose a ScrumMaster who has not only the skills but also the attributes to succeed in the role? Find out how one team defines these criteria to help them evaluate potential ScrumMasters.
4/23/2007 by Roman Pichler
Have you ever asked yourself what it takes to be an effective product owner on a Scrum project? This article explains the key responsibilities of the product owner and provides insights into how to perform the role well.
4/13/2007 by Doug Shimp,Dan Rawsthorne PhD PMP
One of the success factors of Scrum as an agile product development framework has been its powerful language. However, as with all models we create to help us understand, we need guides on how to use the tools. We will be pointing out the boundaries where the Scrum language can become confusing—and, in so doing, hopefully make adoption and application easier.
4/2/2007 by Daniel LeFebvre
"I'm taking off a letter grade because this wasn't turned in on the due date." "Don't be late!" Growing up, we quickly understand that being late is a bad thing. So when a project runs behind, we do whatever it takes to turn it around, even if those behaviors do more harm than good. Agile projects need a to discuss releases in a way that removes the guilt and focuses on appropriate action.