The UK government's digital transformation agenda is ambitious. GDS's vision of government as a platform, the Integrated Review's commitments on data and AI capability, and the relentless pressure to deliver more with constrained budgets all point in the same direction: departments need skilled digital, data and technology professionals, and they need them quickly.
The problem is that demand for DDaT talent — spanning software engineers, data engineers, product managers, user researchers, delivery managers and security architects — consistently outstrips supply. Traditional hiring is slow, expensive and often produces mismatched candidates. Reliance on large system integrators locks departments into multi-year contracts at premium day rates with limited knowledge transfer.
DDaT agile team allocation has emerged as a third way: a flexible model that gives departments access to pre-vetted, multi-disciplinary digital teams on an on-demand basis, aligned to the GDS Agile Delivery Framework and the DDaT Profession Capability Framework.
What Is DDaT Agile Team Allocation?
DDaT agile team allocation involves deploying assembled, cross-functional teams to government programmes rather than sourcing individual contractors or placing permanent staff. A typical allocated team might include:
- Delivery Manager — responsible for running the agile ceremonies, managing dependencies and reporting progress
- Product Manager — owns the product vision, manages the backlog and prioritises features with stakeholders
- Software Engineers — full-stack, front-end or specialist (cloud, DevSecOps) depending on the programme's technical stack
- Data Engineer — designs and implements data pipelines, APIs and storage solutions
- User Researcher and Content Designer — conducts discovery, usability testing and produces GDS-compliant service patterns
- Security Architect — ensures compliance with NCSC Cyber Essentials Plus, HMG Security Policy Framework and any applicable OFFICIAL SENSITIVE controls
The composition varies by programme phase and complexity, but the defining characteristic is that team members have worked together before. They have established norms, known each other's working styles, and refined their ceremonies. This dramatically reduces the ramp-up time compared to assembling a team from scratch.
Why the Traditional Model Is Failing
Traditional resourcing approaches for digital programmes carry well-documented risks that have been highlighted in multiple National Audit Office and Parliamentary Accounts Committee reports.
Dependency on large system integrators. When a single supplier holds the majority of the technical knowledge about a critical system, departments are exposed to lock-in and price escalation at contract renewal. Exit costs are high; knowledge transfer is slow. The 2023 NAO report on government's approach to technology found that departments consistently underestimated the total cost of ownership of bespoke outsourced systems.
Slow permanent recruitment cycles. Civil Service recruitment, even under the streamlined processes introduced by the Cabinet Office, typically takes three to six months from role advertisement to starting date. For digital programmes with tight spending review timelines, this pace is untenable.
Contractor proliferation without capability transfer. Day-rate contractors provide skills on demand but, in the absence of structured knowledge transfer, leave little behind when they depart. The department is renting capability, not building it.
Team assembly lag. Even when individual resources are secured, assembling them into a functioning team takes time. Research on team dynamics consistently shows that newly formed teams go through a settling period — Tuckman's forming, storming, norming, performing — that can consume weeks or months before they reach sustainable velocity.
The Case for Pre-Assembled Teams
Pre-assembled DDaT teams circumvent the assembly lag problem because the team has already formed. Ceremonies are established. Tooling preferences are known. Communication patterns are mature.
Beyond speed, pre-assembled teams offer other advantages for government clients:
Aligned to the service standard. Agile teams operating in the DDaT framework are oriented around the GDS Service Standard from day one. Discovery, Alpha, Beta and Live phases are understood not as abstract theory but as lived practice. Team members have received service assessments before and know how to prepare.
Accountability at team level. When outcomes are allocated to a team rather than individual contractors, accountability is clearer. The delivery manager carries responsibility for velocity and quality; the product manager owns backlog prioritisation and stakeholder alignment. There is a named point of contact for the client at each layer.
Flexible scaling. Programmes move through phases with different resource requirements. Discovery is typically smaller than Beta. Scaling a pre-assembled team model up or down is operationally simpler than varying a large contractor workforce.
Knowledge retention. Because the team is drawn from a single supplier organisation rather than a collection of independents, knowledge is retained within the supplier's institutional memory even when individuals rotate off an engagement. Successor team members can be briefed by predecessors on institutional context.
DDaT Within the Crown Commercial Service Framework
A significant practical advantage of the DDaT agile team model is its alignment with Crown Commercial Service (CCS) frameworks, particularly G-Cloud and the Digital Outcomes and Specialists (DOS) framework — now continued under successor frameworks.
These frameworks allow departments to procure digital teams through a compliant route without full OJEU-equivalent procurement, dramatically reducing the time from identification of need to team deployment. MITC holds CCS Supplier status and operates within these frameworks, allowing clients to engage through established routes without the overhead of bespoke procurement exercises.
What Good Looks Like: The MITC Approach
Our DDaT team allocation model is built on three principles.
Capability alignment. Before allocating a team, we conduct a brief needs assessment to understand the programme's phase, technical stack, security classification and stakeholder environment. This allows us to assemble a team whose skills precisely match the requirement rather than deploying a generic resource pool.
Governance integration. Government programmes operate within governance structures — programme boards, risk registers, investment committees. Our teams integrate with these structures from day one, providing the reporting artefacts and escalation paths that senior responsible owners need.
Explicit knowledge transfer. We treat knowledge transfer not as an end-of-engagement activity but as a continuous obligation. Our delivery managers maintain living documentation of architectural decisions, integration points and operational runbooks. At agreed milestones, we run structured handover sessions with permanent civil servants to embed capability within the department.
Getting Started
For departments exploring DDaT agile team allocation, we recommend beginning with a scoped piece of discovery or a time-boxed Alpha for a lower-risk workstream. This allows both parties to establish working norms, test the model and build the confidence needed to extend the engagement to larger programme phases.
MITC's teams have delivered across HMRC, DWP, the Cabinet Office and the Office for National Statistics, working within OFFICIAL and OFFICIAL SENSITIVE classifications. We are experienced navigating the approvals, security clearances and governance requirements that characterise central government programmes.
To discuss your programme's DDaT resourcing needs, contact us at info@mayfairitconsultancy.com.