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.
Agilefant is a simple but powerful solution for managing software development projects and related activities. It brings together the perspectives of organizing daily work, long-term product and release planning and project portfolio management.
Practitioner report on applying scrum and kanban techniques to a system engineering team.
“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.
A directory of articles on the scrum agile project management approach: sprints, velocity, backlog, user stories management. http://www.scrumarticles.com/
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.
Scrum Expert Copyright © 2009-2024 Martinig & Associates