Technology Programme Manager

Programme Reporting Line:

Programme Director

Reports:

Matrix management of Technology PMs (Tech PM's have dual report to Business PM's)

Overview

1. Drive the delivery of all technology components, internally and externally, focussing on integration of operating model and timeliness of availability to support test phases then live implementation.
2. Ensure Architectural direction set by the Design Authority is adhered to for all technology component delivery.
3. Scope includes all technology delivery, internally and externally, spanning FO, MO, BO, Data ecosystem integration with core Delta and Retail TA integration where relevant.

Responsibilities

Business Direction

• o Content and business outcome driven by each business project but refined and aligned for coherence across the programme by this role, acting as an integration stakeholder at programme level.

Approach

• o Provide a future state oriented cultural overlay with technology staff to ensure focus on future state operating model an d avoidance of historical pitfalls.
• o Ensure suitable and consistent delivery approach (both technology and general management), where applicable including application of relevant internal standards for SDLC where these are compatible with achievement of programme objectives
• o Drive agile IT delivery process within a waterfall programme context
• o Component readiness for testing, especially integration testing phases
• o Ensure component testing for all technology deliverables is completed to standards and is completed in a timely fashion suitable for entry to integration testing.

Planning and dependency management

• o Ensure technology plans are coherent across the programme
• o Surface technology inter-dependencies and ensure these are delivered to across all technology component delivery. Intervene and escalate where this is not the case i.e. Where project delivery is at odds with programme outcomes and escalate where otherwise
• o Ensure an integrated plan for environment utilisation for development purposes and input to test environment planning.

Architecture

• o Adherence to business architecture stipulations, challenging both projects and Architecture decision-making where business outcome / delivery timeline are not optimised.
• o Architectural accountability to programme for internally developed components with externally developed components driven only at an integration level.
• o Take part in Design Authority as part of responsibility to drive coherence across architecture, ensuring all technology deliverables are coherent with agreed Business Architecture
• o Drive component integration at a business functionality level

Progress

• o Facilitate business PMs in understanding the current state and challenges of all technology delivery
• o Provide progress evidence of technology plan and delivery coherence across the projects, especially when aligning to integration test phases.
• o Drive visibility of vendor technology component delivery through appropriate trackers, issue transparency and escalation

Role Integration

• o Provide a key face off Interface to Test Manager to provide a clear view of inbound components for integration and user testing

Resource

• o Help identify technology resource constraints between projects. Data is expected to be a pinch-point.
• o Help identify any other conflict points between projects