Articles, Blog Posts, Books and Quotes on Agile Project Management
Technical debt is one of this great new metaphor that is applied to software development and more specially to agile project management approaches like Scrum. As its financial counterpart, technical debt is not necessary a bad thing as long as you are able to manage it wisely. In this article, Don Reinertsen will help you to put some numbers on the costs and benefits of your technical debt.
In his book Agile Reflections, Robert Galen has aggregated multiple articles that he wrote about transitioning to Agile for the online publication PM Times. The book is based on his experience as in Agile coach helping companies in different phases of their transition to Agile software development.
Scaling and implementing an Agile approach in large projects is one of the hot topic in the Agile community, a natural consequences of the adoption of Agile by larger corporation. In this blog post, Ritika Nanwani shares some of her observations as a member of a large Scrum project.
Sprint retrospectives are the most discussed form of retrospectives in Scrum. You can however the same self-analysis and continuous improvement technique to other items of Agile project management. In this article, Madhavi Ledalla discusses release retrospectives.
Agile and Scrum short iterations should provide software development organization with quicker feedback cycles and help them shifting from building the product right to building the right product. In their book “The Lean Mindset”, Mary and Tom Poppendieck provides an original perspective on this issue.
The first value of the Agile Manifesto is to prefer “Individuals and interactions over processes and tools”. But how can you know if your individuals and your teams like your current Agile approach. In his article, Henrik Kniberg present a simple tool to assess the health of your Scrum teams.
The product backlog might be the more important item for a Scrum team as it represents the business value that the project should deliver to its customers. Putting a priority on the features and user stories is however not always easy for the product owners, especially if they are dealing with multiple stakeholders. In this article, Samantha Laing shares a technique that can help to improve the results of this activity.