Everything You Want to Know About Agile | Book Series

Overview:

It is a step-by-step guide for decision-makers to address and overcome the hurdles in Agile adoption within their organizations.’ The book is written specifically to address the challenges of implementing Agile within the unique structures, constraints and culture of your organization. It describes Agile methodologies in clear business language specifically written for business professionals, providing you with the information that you need to: Assess whether Agile is right for your department Select the Agile methodologies and practices that are best suited to your work Successfully implement these approaches in your department, and Monitor and measure the outcomes. Most importantly, this book gives you a range of strategies for aligning Agile work within the reporting, budgeting, staffing and governance constraints of your organization, which is arguably the biggest challenge.

This book will show you how to comprehensively address the issues that IT departments face when they try to implement Agile approaches within the constraints of their traditional organizations, including existing project frameworks,budgeting structures, contracts and corporate reporting. It is an essential resource for IT departments that want to deliver successful Agile results, even in the most challenging environments.

Authors:

L. Cooke

Published In:

2016

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