O'Reilly logo
  • sheryl.bulloch thinks this is interesting:

Chapter 15. The Agile Release Train

Today’s development processes typically deliver information asynchronously in large batches. Flow-based processes deliver information in a regular cadence in small batches. Cadence lowers transaction costs and makes small batches more economically feasible.

—Don Reinertsen

The original title for this chapter was to be “The Release” or perhaps “Releasing” or “Release Planning and Execution.” But none of these titles, nor others that I toyed with, communicated the essence of what I intended to communicate. Each of them implied a thing that was ...

From

Cover of Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise

Note

With traditional methodologies, a release was a huge event. That is not the case with agile development. With agile development there should be a continuous flow of releases in small, frequent increments which represents a continuous build of value added to the marketplace. As a Product Manager, it is important to think about releases as a train so that this philosophy can be reiterated to the team throughout the release planning process.