Cycles, Cycles, Cycles

This content is syndicated from Jim Highsmith by Jim Highsmith. To view the original post in full, click here.

One of the problems in integrating Agile delivery or continuous delivery into enterprises is the differences in cycles. Companies have tended to run on annual budgeting cycles, longer strategic planning cycles, with some, although not always close coordination between the two. Product management tends to run on product cycles—that depending on the product type can be months to years (for airplanes for example). Projects tend to run in phases (traditional projects) or releases and iterations (Agile). Project Management Offices, reflecting upper management desires, run monthly, quarterly, and annual cycles.

There are several potential problems with all these cycles:

  • the cycles don’t coordinate well

  • Everyone wants everyone else to conform to their cycles

  • Finance, particularly for public companies, seem to drive everyone else’s cycles

  • Different kinds of projects and business initiatives need different cycles

Project cycles have always clashed with financial cycles, as projects just don’t naturally finish in December. The cost side of projects has traditionally been reported on a calendar basis, but the value side has often not started until the project has completed. Incompatible cycles have plagued developers and accountants alike, as for example, bi-weekly payrolls don’t match up nicely with monthly financial reporting.

Most cycle mis-matches are time related, but there are other types. For example, Agile cycles delivery partial results in 2-week iterations. By partial results I mean—working software, but only part of the application; architectural pieces, but not an entire architecture; requirements, but only details for the stories done during the iteration. However, many company governance cycles are built around completed results—a complete requirements document, a complete test plan, a completed data base design. Governance systems built around this latter model—make Agile projects difficult to “govern” in these organizations because of this cycle mismatch.

In my prior life, as a waterfall methodologist (yes, I admit it) in the 1980s, I used something called the Warnier-Orr methodology that included a bracket-style diagram called the Warnier-Orr diagram. Part of the methodology for resolving cycle conflicts was to determine the “lowest common denominator.” In a payroll system, for example, that needed to generate by-weekly paychecks and monthly financial statements, the lowest common denominator would be days. While this is a simple example, it’s amazing how many systems kept data at the wrong level of detail and then couldn’t generate all the required information for different cycles.

Many Agile organizations are using the 3-tier model for development shown in the graphic—Iteration (2 weeks), Release (3-6 months), and Roadmap (6-18 months) with corresponding differences in the granularity of the deliverables (stories, features, capabilities). What if the entire enterprise used this “Short-Horizon” model to actually run the business? What if everyone synchronized using 2-week iterations? What if everyone focused on 2-week delivery of partially completed products, documents, business initiatives, plans, and other business artifacts? I was talking with a client recently who was having cycle meshing problems—their product management group wasn’t syncing up very well with their Agile delivery teams. In other companies Devops initiatives are attempting to sync operations and release management more closely to delivery team releases.

When companies get serious about Enterprise Agility, one area that will require major change is moving from financial cycles being the driver to focus on  a product-driven (deliverables) “Short-horizon” model (that does deliver the required financial information but is not driven by that financial cycles) that is more adaptable to changing conditions.

Leave a Reply

Your email address will not be published. Required fields are marked *

eleven − 1 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”



To explore how we can help you, please get in touch