10/15/2007 by Mark Randolph
Progress smells often point to failings in one of three areas: backlog management, feature definition, and feature completion. This article analyzes what lack of progress means and describes remedies for weaknesses in backlog management. Parts two and three of this smell analysis will address feature definition and completion, respectively.
10/9/2007 by Geir Amsjo
The simplicity of Scrum is both its strength and its weakness. A true understanding of agile principles is necessary for Scrum (or any other agile method) to succeed.
10/8/2007 by Aaron Sanders
Agile estimation gives you the right answer, even if it’s not the one you want to hear.
9/24/2007 by Chris Spagnuolo
Management can see that Scrum works for developing software. What they often have more trouble understanding is that Scrum is a project management process that should govern the entire project, not just the "development part."
9/24/2007 by Andy Brandt
Just because your company is agile doesn't mean your customers are. How do you compete in a market where fixed bids and waterfalls are commonplace?
9/5/2007 by Angela Druckman
The Scrum framework brings a structure to projects that can right many wrongs, but it is not a silver bullet, and it certainly won’t make all problems disappear.
8/18/2007 by Rebecca Traeger
A recommended reading list for anyone interested in learning more about Scrum.
8/15/2007 by John P. Puopolo
Discover why it’s critical for your agile teams to be collocated and how to best position your teams for agile success.
8/13/2007 by Jim York
Customers want it yesterday.
Scrum promises it tomorrow.
So why aren’t we getting it? What is “it” anyway?
8/6/2007 by Guy Beaver
Well-formed, hyper-productive agile teams exhibit certain common traits and have shared best practices. Find out how these teams approach sprint planning.