David Laribee

The Evolving Concurrent Releases Toolkit

True flow in software at any kind of scale requires concurrent releases (AKA release-per-feature).

Achieving this level of maturity requires more-sophisticated product design and implementation practices. For one: work-in-progress may confuse users. Without the batch blanket you’ll need to hide or eliminate unfinished software from production builds. On the complex end of the spectrum, when your throughput increases you have to cope with constraints outside the development organization such as sales force, marketing and customer education.

Starting with a brief economic argument for concurrent releases, we’ll dive into solutions both product and technical. Areas covered include: user experience, multi-dimensional Kanban boards, composite architectures, distributed version control and continuous deployment.