Articles, Blog Posts, Books and Quotes on Agile Project Management
A prevailing belief among Agile and Scrum proponents is that “a great deal of explicit risk management becomes unnecessary when a software development project uses an agile approach.” In my experience, this is a false and dangerous assumption. Project risk is a hungry leopard ready to devour the unprepared. Fleet-footed agilists and die-hard waterfallists alike.
Agile and Scrum project teams can adopt many different structures. In her blog post, Elizabeth Harrin gives a good summary of five structures that could be used by Agile teams based on a presentation made by Catherine Powell at the Oredev conference.
Technical debt a metaphor that refers to the eventual consequences of poor or evolving software architecture and software development within a codebase. The technical debt can be defined of as work that needs to be done to adapt a software to the best practices. In this blog post, Bastian Buch explains the step used in his organisation to reduce technical debt in an Agile way.
The main goal of a sprint review in Scrum is to receive feedback on the product that the team has built in the last sprint. How do you do when the product is created by many different teams and there multiple stakeholders who are involved in the Scrum project? In this article, Stephan Kraus explains how to scale the sprint review in Scrum using the fair concept.
In Scrum the estimation effort and accuracy depend on the team. In this article, Jingjie Wang discusses the situation where the Scrum team tends to underestimate its capacity to deliver so to be sure that the product owner and the scrummaster are always happy at the end of each sprint because everything promised is deliver.
Collaborative risk management brings many benefits to Scrum teams, notably by generating wiser decisions and creating a collective ownership of issues. In his blog, Mike Griffiths describes some collaborative games that can be use project risk management.
Positive sprint reviews increase customer confidence in the team and the team’s confidence in itself. If the review goes badly, the trust will degrade, just as we saw in the story. At the same time, don’t forget that the main purpose of the sprint review is not a round of applause for a job well done. The real goal of a sprint review is to stop and ascertain whether the project is on the right track.
Scrum Expert Copyright © 2009-2026 Martinig & Associates