Job Summary

As Project Manager, you operate in the project governance space for a defined batch of work within Infrastructure & Operations (I&O). You provide the project-level governance needed to coordinate, track, manage, and communicate delivery of a clearly defined scope of work, typically requiring coordination across one or two delivery teams. This role is designed for an environment where much of the work is delivered through long-lived Agile Teams and Agile Release Trains (ARTs), rather than temporary project teams. The Project Manager does not replace or override standing team governance. Instead, the role provides a project management wrapper around a specific batch of work as it flows through the relevant delivery teams, while working within their existing methods, tools, and governance structures. You create and maintain a unified view of project scope, schedule, cost, dependencies, risks, issues, decisions, and readiness, even when the work is delivered through different methods, internal organizations, or external vendors. You ensure the right process is followed, work is routed through the right channels, and stakeholders receive decision-useful information. You support delivery approaches that reduce risk and enable useful work to be delivered in smaller increments wherever practical, rather than assuming that all project value must wait until the end of the project.

Key Responsibilities

 1) Govern the project wrapper for a defined batch of work • Provide project governance for clearly defined work, typically requiring coordination across one or two delivery teams. • Ensure the project is governed through the correct channels and with the appropriate level of discipline. • Function as the primary coordination point for business stakeholders throughout the delivery lifecycle. 2) Create and maintain a unified view of scope, schedule, and cost • Maintain an integrated view of scope, schedule, cost, assumptions, dependencies, and delivery commitments across participating teams. • Partner with the Portfolio Management Team to track budget and cost for non-labor spend and provide visibility of project-related work flowing through long-lived teams. • Actively manage cost and budget for temporary teams organized around the project scope where required. 3) Facilitate intake, framing, and routing • Coordinate project intake and framing through standard governance channels. • Engage Agile Teams, ARTs, Platform Owners, Product Owners, and accountable parties based on how the scope will be delivered. • Do not approve or prioritize intake directly unless explicitly delegated. 4) Coordinate dependencies, risks, issues, and decisions • Maintain an integrated view of project dependencies, risks, issues, decisions, owners, due dates, and escalation paths. • Escalate when progress stalls, ownership is unclear, or decisions exceed team authority. 5) Work effectively with long-lived Agile Teams and ARTs • Work within existing governance, tooling, and delivery methods. • Respect the governance boundaries of Scrum Masters, RTEs, Platform Owners, Product Owners, System Architects, and delivery teams. • Build project-level views around standing structures rather than replacing them. 6) Coordinate readiness, milestones, release, and cutover • Coordinate kickoff meetings, status reviews, milestone, release, cutover, transition, and handoff readiness. • Collaborate with Program Managers on integrated readiness and governance where the project is part of a wider program. • Collaborate with communication teams for deployment communications and stakeholder notifications. 7) Support incremental and iterative delivery • Encourage sequencing that enables earlier validation, feedback, and value delivery where practical. • Coordinate staged releases with accountable owners and delivery teams. 8) Provide reporting and stakeholder visibility • Communicate integrated status across scope, schedule, cost, dependencies, risks, issues, decisions, and readiness. • Support steering forums and governance reviews with a clear view of delivery reality and decisions required. • Support lessons learned and process improvement opportunities. 9) Work across organizational boundaries • Coordinate across I&O, other National Grid teams, external vendors, and delivery partners. • Ensure external dependencies and contributors are represented in project governance and readiness planning

Skill Requirements

Strong experience coordinating work across multiple teams, stakeholders, and delivery methods. • Demonstrated ability to maintain integrated views of scope, schedule, cost, dependencies, risks, and issues. • Experience in environments combining agile, flow-based, operational, and traditional project delivery. • Understanding of how to work with standing Agile Teams and ARTs without disrupting their governance model. • Experience supporting milestone readiness, release readiness, cutover planning, and stakeholder reporting. • Strong written and verbal communication skills for technical and non-technical audiences. • Ability to work effectively in matrixed environments across internal and external teams. • Practical understanding of staged and incremental delivery approaches. Expected Knowledge • Project planning and control • Scope, schedule, cost, risk, issue, and dependency management • Delivery governance and reporting • Agile delivery and flow-based work management • Cross-methodology coordination • Budget and cost visibility • Governance forums, escalation paths, and decision management Assignment Specific Knowledge • Experience supporting enterprise infrastructure, networking, telecommunications or technology organizations • Experience supporting network infrastructure, WAN, LAN, SD-WAN, wireless, DNS, DHCP, IPAM, cloud networking or telecommunications projects preferred. • Experience managing multiple concurrent initiatives and competing priorities • Experience with Jira, ServiceNow and Microsoft Suite • Ability to effectively coordinate cross-functional technical teams

Other Requirements

These generic attributes are required based on the skill responsibility levels above extending up to level 4. Autonomy: Works under general direction and exercises discretion within a defined framework of accountability. Influence: Influences team and cross-team decisions and builds effective relationships with stakeholders and delivery partners. Complexity: Performs a broad range of complex activities across teams, delivery models, or organizational boundaries. Knowledge: Applies practical knowledge of project governance, planning, budgeting, risk, and delivery management. Decision-making: Makes informed decisions within agreed authority and escalates when necessary. Planning: Plans, prioritizes, and coordinates work to meet objectives, timelines, quality, and governance needs. Collaboration: Works effectively across teams and governance bodies to maintain a coherent delivery picture. Problem-solving: Investigates delivery problems, risks, and dependencies and supports timely corrective action. Communication: Communicates clearly with technical and non-technical audiences through concise, accurate reporting. Leadership: Provides day-to-day leadership through coordination, influence, and disciplined governance. Adaptability: Adjusts governance views and plans constructively as priorities and delivery conditions change. Digital Mindset: Uses tools, data, and reporting practices to make delivery status visible and actionable. Security, Privacy & Ethics: Applies appropriate standards and promotes responsible, respectful, and compliant working practices • Role family positioning: Centralized delivery-governance capability focused on batch-based delivery governance across I&O and related delivery contexts. • Primary partners: Scrum Masters, RTEs, Platform Leads, Platform Technical Leads, Platform Owners, Product Owners, System Architects, delivery teams, operational/change/release stakeholders, Finance, and external vendors. • Role boundaries: Owns the project governance space for a defined batch of work. Does not own Agile Team or ART process governance, platform prioritization, story readiness, solution design, or team delivery execution.