Abstract
A major reason enterprises transition to Lean-Agile software development is the need to plan releases predictably and accurately. Release planning is the process of transforming a product vision into a product backlog. The release plan is the visible and estimated product backlog itself, overlaid with the measured velocity of the delivery organization. It provides visual controls and a road map with predictable release points. Lean-Agile says the release plan must be driven by the needs of the business. We prioritize to maximize value to the business. We sometimes call this approach “business-driven software development.” To understand how to do this, we must understand some fundamental concepts about process. Therefore, the chapter begins with a conversation about the issues that underlie process—predictability, level of definition, and requirements for feedback.
Cite
CITATION STYLE
Shalloway, Alan and Beaver, Guy and Trott, J. R. (2009). Lean-Agile Release Planning. In Lean-Agile Software Development: Achieving Enterprise Agility (1st ed., Vol. 204, p. 22). Addison-Wesley Professional.
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.