Articles, Blog Posts, Books and Quotes on Agile Project Management
As Scrum is the most popular framework adopted by organizations adopting an Agile approach for project management, many companies are trying to find financial facts that justify its adoption. This article discusses the topic of evaluating the return on investment (ROI) of using Scrum and Agile project management approaches. It suggests some hints about mistakes to avoid and on how to get meaningful results from this activity.
If you asked software developers about Agile, there are chances that a majority will discuss it with words like “Scrum”, “sprints” or “retrospectives”. However Agile is not just a collection of techniques and practices, but it is more a state of mind or a culture. This is the topic of this book written by Pollyanna Pixton, Paul Gibson and Niel Nickolaisen.
As Agile project management is being widely adopted, the questions of if and how it could scale is a main topic of discussion. In this blog post, Gilt explain how it scales Agile with teams, ingredients, initiatives and KPIs.
The sprint retrospective in an important moment in the Scrum approach where the team think about its software development process and tries to improve it. As on of the three Scrum roles, the product owner has to play its part in this activity. In this blog post, Roman Pichler explains how product owner can play an active role during the retrospective meetings.
“You can’t manage what you don’t measure” is an adage that is popular in project management. However, metrics programs are not easy to implement and have their dark sides. In their book “The Agile Culture: Leading through Trust and Ownership”, Pollyanna Pixton, Paul Gibson and Niel Nickolaisen provides some advice about implementing metrics, the Agile way.
User eXperience (UX) includes the practical, affective and valuable aspects of human-computer interaction and product ownership. This article from Anindya Sengupta tries to answer common questions about UX and Scrum. It explores the challenges faced by a team working with a separate UX team in Scrum. It also gives recommendations for UX teams that are part of a Scrum team.
At the end of each sprint, the Scrum team take some time to think about what could be improved in its Agile process. In this blog post, Natalie Warnert discusses how you could also use the retrospective meeting to look at story sizes after the sprint and determine if they were correctly sized as far as story points are concerned.
Scrum Expert Copyright © 2009-2026 Martinig & Associates