5/28/2008 by Mitch Lacey PMP
We all know the three questions of Scrum: What did you do yesterday? What will you do today? What blocking issues do you have?
We all do our best to answer these questions. So how come so many of our initial demos turn up problems we didn't catch? Maybe it's because, at least at the beginning, we need to add a fourth question to our daily standups.
5/16/2008 by Andy Brandt
Find out how one company maintains a disciplined process without breaking their team spririt.
5/7/2008 by Dave Prior
Dave Prior and Mike Cohn sat down at Scrum Gathering Spring 2008 to talk about managing an agile project in a waterfall environment. They also discussed the challenges facing traditional project managers as they shift toward agile. This transcript of their interview may help answer some of your own questions.
4/4/2008 by Doug Shimp,Samall Hazziez
Well-formed teams don't just happened. They are created and nurtured through specific practices and ideals, both agile and traditional. Find out what a well-formed team looks like and how to move your team in that direction.
3/28/2008 by Geoff Watts
Bugs and support issues don't always wait for a new sprint before rearing their ugly heads. What should a Scrum team do to balance feature development with support activities?
3/18/2008 by Paul Goddard
Paul Goddard explores the parallels between agile development and music composition and performance.
2/25/2008 by Chris Sterling
Deliver the most bang for your investment buck with stories that link features to their users and to their value for those users.
2/13/2008 by Alan Atlas
In the hunt for clues as to how to manage an agile team, the sprint backlog can seem like a major breakthrough. Finally! A list of tasks broken down by person and estimated. What a find! Not so fast, Sherlock. Your search for "who's doing what and when" is leading you down the wrong track.
2/12/2008 by Mike Cohn
How much work should you do in advance of a sprint? Nothing? As little as possible? As much as possible? Find out why doing just enough, just in time might be your best strategy.
2/6/2008 by Henrik Kniberg
Legacy code. It's out there, dragging you down, forcing you to create workarounds just to avoid touching it. Automated testing could help but who has time? And where would you even start? How about a little bit at a time? The Scrum way.