Articles, Blog Posts, Books and Quotes on Agile Project Management
Pair programming is one of the original practice of eXtreme programming, but it is also one of the least used by Agile software development teams. In his blog post, Alisdair McDiarmid explains how Customer.io uses pair programming with remote teams.
The basic rules of Agile project management frameworks like Scrum are deceptively simple. Drawing from his experience as an Agile coach, Jeff Campbell offers in his book “Actionable Agile Tools” some lightweight practices and tools that could help you to implement successfully an Agile approach.
The retrospective is one of 12 principles outlined in the Agile Manifesto. If this is easy to do this for collocated Scrum teams, how can you achieve good results if you have remote members. In this blog post, Robert Matheson provides a valuable collaborative retrospective technique that can be used for distributed Scrum teams.
Budget-based project management is an alternative to classic estimates that has some following in the Agile community. In their book “Fifty Quick Ideas to Improve your User Stories”, Gojko Adzic and David Evans, discusses how using a budget instead of estimates can help to deliver better projects.
The Product Owner Manual is a short e-book available for free from ScrumSense. It discusses in a practice-oriented way the roles and techniques used by a product owner in Scrum teams, including the story writing principles and how to perform release planning.
As Agile product and project management approaches are adopted by large organizations, they have to coexist with a typical entity of big companies: the Project Management Office (PMO). A recent report from ESI International explores how the PMO staff views the challenges of implementing Agile in their organizations.
Agile requirements are a key success factor for Scrum projects. Many people criticize the minimalist format of user stories, often forgetting that they are mainly a support for a conversation and don’t have the objective to fully document requirements. In this article, Paul Raymond discusses how classical use cases can be use to expand user stories during requirements elicitation in Scrum sprints.
Scrum Expert Copyright © 2009-2026 Martinig & Associates