Incremental development is distinctly different from iterative development in its purpose and also from its management implications. Teams get into trouble by doing one and not the other, or by trying to manage them the same way. “Using Both Incremental and Iterative Development” illustrates their differences and how to use them together.
In his blog post “Earned Value versus Earned Schedule“, Glen Alleman discuss the concepts of Earned Value and Earned Schedule.
As an agile coach, you want to build trust with the people on the team you are coaching. You also want to improve trust between individuals on the team (which is hard to do if the team doesn’t trust you yet). This post shares Rachel Davies thinking on how you can help encourage trust to grow in different situations.
While the iterative development approaches found in Agile Software Development fulfill the promise of working software each iteration, that task of choosing which software to build first can be daunting.
An introduction to the software estimation process aimed at project managers, developers and customers who want to get a better understanding of the basics this subject, and avoid to make their projects a death march one.
This book is composed of papers previously written by Watts Humphrey. The people and management aspects of software development are often neglected in books and this one is a good source to start thinking about them… and improving our practice.
If you have never experienced a well-run retrospective, then it is hard to imagine what it is like by simply reading a book. Nevertheless, the article “An anatomy of a retrospective” tries to tie many of the discussions into a single experience. It is based on one real-life retrospective, but spiced up with a few pieces from other retrospectives. I’m certain the participants would recognize themselves, but I hope I have changed enough of the trivia to protect their privacy.