Articles, Blog Posts, Books and Quotes on Agile Project Management
The Definition of Done (DoD) is a common understanding within the Scrum team on what it takes to make your software ready to be released. In their book “Managing the Unmanageable”, Mickey Mantle and Ron Lichty propose an extensive list of what a Definition of Done should include.
Every business needs effective project management to fulfill its mission and goals, whether a small-town bakery or a tech giant at the forefront of innovation. Seamless project execution and the capacity to pivot quickly in response to market needs have become the foundation of long-term success.
The goal of the book “Lean-Agile Software Development – Achieving Enterprise Agility” by Alan Shalloway, Guy Beaver and James R. Trott, is to propose a vision of Agile software development that goes behind the current practices, more specifically Scrum, to integrate the principles of Lean development.
This article discusses the clarity of requirements for Agile software development and explains how you can use a four-step process for gathering them with the four levels of agile requirements.
Most teams I work with have three distinct roles; BA, Developer, and QA. Most teams I work with have three distinct phases of their work; gather requirements, build, verify. Even on agile teams, these separations exist.
Scrum offers minimal guidelines for Agile project management. In his book “The Scrum Field Guide”, Mitch Lacey provides Scrum practitioners with material that should help them improve their Scrum practices.
In his foreword of the book “Management 3.0” by Jurgen Appelo, Robert C. Martin wrote that he hates management books, but “this book is smart”. I think that this book might be smart because Jurgen is smart.
Scrum Expert Copyright © 2009-2026 Martinig & Associates