Long Release Cycle | Glossary

Definition:

Common problem in any organization is always missing deadlines. To be more specific, the releases always occur at a later date than planned. Delays can be a real problem, conflicting with your goals. Let’s say our goal was to focus on customers and maximize  our revenue, but the delays causes to lose our customers, and messes up with cash flow. To find out the root cause of the delayed releases or long release cycles, we use cause-effective diagrams.

Long release cycles are highlighted with thicker arrows, and the recurring problems are always highlighted in loops. Initially it may take some time, but spotting these problems will greatly increase the probability of solving the problems effectively and permanently.

Some of the reasons why delayed releases happen:

  • Lack of release automation
  • Lower priority features not removed from the iteration
  • Adding more people to the iteration even though they have nothing to do with the problem

Further Reading:

Book : Lean from the Trenches: Managing large scale projects with Kanban by Henrick Kniberg

Release Cadence | Glossary

Definition:

In Agile, Cadence is the number of days or weeks allocated in a Sprint or Release. In other way round, it is the length of the team’s development cycle. In the present business environment, a wide range of organizations go for a two week cadence. The cadence that a project or organization selects is based on a number of factors that include: criticality, risk and the type of project.

Apart from collaboration, every delivery team needs to do in product management is to choose the release cadence of their product. This is an important aspect, as the release cadence defines how often you release your solution both internally and externally into production (or the marketplace). The teams will release their solutions into production environments or cloud server where end users will use systems. But the commercial software companies, release their solutions directly into marketplace confronting their customers directly.

Further Reading:

Disciplined Agile Delivery by Scott W. Ambler and Mark Lines