Articles, Blog Posts, Books and Quotes on Agile Project Management
Upfront Modeling is fine, documents describing the intended architecture are fine, and so forth. But the architecture, and our learning about it, can improve. Speculative software architecture should be made concrete and not of concrete.
In this blog post, Joseph Little proposes a set of suggestions and questions that should help you to think on how you should make decisions about distributed scrum.
This article presents the mechanisms that Visual Studio provides to support the team enacting an Agile process, primarily with Team Foundation Server (TFS). TFS captures backlogs, workflow, status and metrics of Scrum projects. This guides the users to the next appropriate actions. TFS also helps ensure the “done-ness” of work so that the team cannot accrue technical debt without warning and visibility.
In this blog post, Gary Reynolds shares ten issues that prevent Scrum stand-up meetings to reach their goal. He also offers advice on what ScrumMasters can do to ensure they either don’t occur at all or are eradicated over as short a time as possible.
The Dialogue Sheet is a new technique for team retrospectives in Scrum Projects. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.
This article presents the changes needed to create collaborative agile teams. It explains that you need to modify in your traditional project management team both the process, the way people get work done, and how people work together.
This article explains that it is important to end doomed projects before they become “too big to fail”. This article isn’t about the personal benefits of failure, but is rather about Agile software development. It’s about how failure, recognizing it and doing something about it, is a critical element of any Agile initiative.
Scrum Expert Copyright © 2009-2025 Martinig & Associates