Articles, Blog Posts, Books and Quotes on Agile Project Management
Agile teams thrive on continuous improvement, and retrospectives are a key practice that enables teams to refine their processes after every sprint. These structured meetings provide a dedicated space for teams to reflect, identify opportunities for improvement, and implement changes that drive efficiency and collaboration.
Agile retrospectives are a cornerstone of continuous improvement, enabling teams to reflect, adapt, and enhance their processes. Whether you call it a Sprint Retrospective, Iteration Retrospective, or Team Retrospective, the goal remains the same-identify what’s working, what’s not, and how to improve.
As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code.
Implementing Agile and Scrum in software development organization means a big change. In her book “The Great ScrumMaster“, the Agile coach Zuzana Šochová recommends an eight steps journey for a successful transformation to the Scrum approach.
One of the key element of Agile Software Development approaches like Scrum is to emphasize delivering quickly business value over having a long-term rigid plan. In his book “Project Myopia”, Allan Kelly discusses the issue of identifying and delivering value.
We all know that there are three roles in Scrum teams : product owner, scrum master, and the development team. Modern software development can sometimes require a high level of specializations that could be beyond the capabilities of the Scrum team members.
Velocity is one a key metrics used by Scrum teams to measure the rate at which an Agile team delivers value to the customer. In his book “Escape Velocity – Better Metrics for Agile Teams”, Doc Norton explains why velocity is not the ideal metric for Scrum teams.