Roles in an agile programme

One of the common criticisms made of agile is the inability to scale to large systems and programmes. It seems worthwhile, therefore, to think about the differences in agile structure between a programme and a project.

Just as in waterfall many programme roles relate directly to those in a project. However the programme level is fundamentally about business outcomes rather than project outputs and therefore focusses on business change implementation and benefit realisation, functions not normally found in projects. At development level though, the responsibility is larger and coordination greater but the roles are basically the same. The Programme Manager, Product Owner and Technical Architect roles are like this, corresponding to Agile Project Manager, Product Owner and Technical Lead.

In addition a programme needs some roles that don’t appear at all in a project, notably Programme Director and Business Change Manager. Again these roles are a result of the increased scope and communication necessary in a programme and also because of the focus on organisational change.

Programme Organisation Chart

Lets look at a typical agile programme organisation.


The people in the technical teams (product development, integration, infrastructure) have Agile project roles. The Agile programme roles are in the Programme Board (Agile Programme Manager, Programme Director, Programme Product Owner, Technical Architect) and Change Implementation workstream (Business Change Manager).

Programme Director

The Programme Director is a senior manager responsible for the overall success of the programme. He/she is the final point of responsibility at the programme level.

The Programme Director is the key manager in ensuring the programme remains aligned to corporate strategy.

Typically the Programme Director is the business sponsor for subordinate projects. They might also be the Programme Product Owner and could be the Product Owner for the Technical workstreams.

MSP actually expects a Senior Responsible Owner (SRO) at the head of a programme although it accepts that some organisations have a Programme Director instead.

Programme Product Owner

The Programme Product Owner is responsible for the entire product being delivered by the programme team. Normally the Programme Product Owner is a different role to the Programme Director but the two roles can be held by the same person. As the size of the programme grows the Programme Director will definitely have to delegate increasing amounts of product responsibility to other people. At some point the two roles split.

MSP doesn’t have the concept of a Programme Product Owner as many programmes are not about building something (although our interest is software development).

Agile Programme Manager

A Programme Manager is responsible for the programme from programme setup (including governance), through the delivery of the capabilities and benefit realisation, to programme closure. A Programme Manager has to do all the normal project tasks (Planning, Monitoring and Control, Change Management, Risk Management) but at the programme level.

In addition the Programme manager must shape the programme team including subordinate projects. They need to form the various teams, manage the interdependencies beween them and ensure the projects deliver as tasked.

Technical Architect

The senior technical person on the programme is usually a Technical Architect. They have overall responsibility for technical quality of the product including how it is structured, organised, and implemented.

Business Change Manager

The Business Change Manager (BCM) is an MSP role. It doesn’t appear in a project (Agile or not). That is because a programme is about business change and a project is about delivery of outputs.

The BCM’s role is to manage the organisation through transformation. The programme might create capability but it is up to the BCM to ensure the organisation adopts the products and whether the organisation achieves the desired benefits.

The nature of the role, including close stakeholder contact, means a BCM is usually from the business. The role can be full or part time, long term or short and are often local champions recruited to support roll out in their area.