Articles, Blog Posts, Books and Quotes on Agile Project Management
It’s obvious, but warrants mention: What we do in the future is likely to be different from what we’re doing today. The implications for user stories should be obvious: User stories are temporary. Saving them for posterity doesn’t serve the primary purpose of user stories, and doing anything that makes them less temporary can turn user stories from benefit to detriment.
“The Quest for High Performance” by Tom Reynolds. One of the best ways to ensure that a team grows to be high performing is to get them off to the right start. Read this article to learn two team start-up activities that focus on process and help ensure everyone is on the same page from the beginning.
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.
Scrum Expert Copyright © 2009-2023 Martinig & Associates