The Four Principles of Forming Effective Governance of a Release Train

I’ve been working with a number of government agencies as they look to Agile methodologies to help them implement their digital transformation strategies. Governance is key to these implementations as the governance framework needs to describe the functional lines of responsibility and accountability.
It is important to recognise that, because a Release train is a construct, the governance framework is explicitly designed to support the outcomes of that construct. As such, it is independent of the organisational hierarchy and therefore must also contextualise these new  Agile roles and the responsibilities of all those involved in the Release Train.
Team members need to know what decisions are within their domain and which need to be escalated.  In our Release Trains, we want to optimise for fast, decentralised decision making as any decision that must be escalated to a higher level introduces delay (waste) and inhibits flow however within the government agencies we also needed to acknowledge that some decisions are strategic, critical and far reaching across the enterprise and therefore need to be centralised.

Decentralised Decision Making

Decentralised decisions tend to be those decisions that need to happen frequently, are often time-critical (e.g. acceptance of a Sprint Goal at the end of Sprint Planning or acceptance of User Stories as “Done” in Sprint Review), and do not have significant economies of scale. The responsibility for these team-level decisions typically resides with the Product Owner (for decisions regarding the team’s work, scope and quality) or with the Scrum Master (for decisions regarding execution of work aligned with the Scrum process).

Centralised Decision Making

Strategic decisions, those that are infrequent, long lasting and have significant economies of scale, are made at a higher level of management. In the Release Train, the responsibility for these decisions typically resides with the Product Manager (for decisions regarding the scope and boundary of the work for the Agile Release Train and its quality) and Release Train Engineer (for decisions regarding execution of work across the Agile Release Train), with the ultimate level of accountability residing with the Program Director and then the Portfolio Executive.

Four Principles for Effective Governance

  • A single point of responsibility for the success of the Train – This provides clarity of leadership, management and timeliness of decision-making during the product increment.
  • Service delivery is focused on business value – Placing the delivery of business value at the heart of the product increment.
  • Separation of delivery ownership and product ownership – To focus on delivery of business outcomes and prevent decision-making forums, such as the Release Management Group (RMG), from becoming just a status report meeting focused on technical issues.
  • Separation of project governance and organisational structures – To reduce the number of project decision layers, since the project decision path does not follow the organisational line of command.

To achieve its goals, this Release Train is comprised of the following three structures:

Activity Role Description
Directing Release Management Group Accountable for the direction and management of the Train within the constraints set out by the Program’s mandate.
Managing Release Train Engineer and Product Manager Responsible for the day-to-day management of the Train within the constraints set out by the RMG, typically encompassing time, cost, quality, scope, risk and benefits.
Delivering Scrum Team/s Responsible for delivering the products to an appropriate quality within a specified timescale and cost.
Responsible for planning and producing products.

 

About the author

Related Posts:

Setting up a New Agile Team

When setting up new agile teams we have found that starting small with the basics and adding patterns as they start to develop capability has helped us get new teams up and running within 2-3 days and acheive a baseline of agile capability within 3 months

READ MORE

Product Management versus Project Management

Gartner reports that 85% of executives are now turning to agile product management over projects. Why is this shift occurring and what do you need to know about product management to optimise your strategic investments for greater market share, better ability to pivot, or get your products to market faster?

READ MORE

Big Upfront Planning is Out. Pivoting to Respond to Change is In

With uncertainty at an all time high, the response of many organisations in those early days was to batten down the hatches and the impact may be felt for many months to come. To survive through this, big up front planning will be out and pivoting to respond to change will be the new normal.  

READ MORE

Remote PI Planning – Insights into what worked and what didn’t

Running remote PI planning for the first time 100% virtual was a bit daunting a few weeks ago when the reality set in that with the current crisis, this was now our reality. We prepared, thought through worse case scenarios and had back up plans and felt eerily calm as the day began. It was a great success and here are our tips.

READ MORE

Strategies for successfully leading remote agile teams

Leading remote agile teams was always going to be tricky. Implementing these 6 strategies can help leaders reduce team stress, address concerns about work progress, increase productivity for the  teams, and restore and maintain healthy communication channels.

READ MORE

Copyright © Zen Ex Machina® and ™ (2020). All rights reserved. ABN 93 153 194 220

search previous next tag category expand menu location phone mail time cart zoom edit close