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.
They say there are three important characteristics of real estate: location, location and location. The same is true for scrum teams. Where scrum team’s members are located has a profound effect upon success and productivity. Agile advocates recommend collocation of a software development team and proximity to the customer.
This article “Scrum Roles – an Unsolvable Puzzle?” discusses the different roles in Scrum projects and how you can relate them to traditional project management roles.
Scrum Expert Copyright © 2009-2024 Martinig & Associates