Technical Program Manager

Role Description

• Objectives
• Deliver onboarding within the agreed scope, timeline, and quality thresholds.
• Establish clear ownership, sequencing, and dependency management across all involved teams.
• Provide transparent reporting regarding progress, risks, and key decisions.
• Achieve production readiness, validating onboarding scenarios and ensuring no critical defects at go-live.
• Scope of Work
  
  

• Convert the onboarding strategy into a detailed execution plan, including milestones, owners, and dependencies.
• Establish a governance model with weekly executive updates and workstream checkpoints.
• Maintain an integrated program plan that drives accountability across teams.
• Workstream Management
• Decompose onboarding scenarios into distinct workstreams, each with defined outputs.
• Track progress against the plan, proactively identifying and resolving any gaps.
• Enforce scope control and manage changes effectively.
• Cross-Functional Coordination
• Align IAM, engineering, security, and partner teams on requirements and sequencing.
• Facilitate decision-making, escalate blockers with clear options and recommendations.
• Ensure timely stakeholder engagement and secure necessary signoffs.
• Migration Execution
• Partner with onboarding/migrating teams to remove tenant-onboarding blockers (e.g., access, dependencies, sequencing, readiness criteria) so teams can continue onboarding to the tenant.
• Coordinate with the Program Lead to prioritize onboarding scenarios, track progress and blockers, and drive resolution paths (including escalation) as needed.
• Maintain visibility into which scenarios are in scope/priority, their current status (not started / in progress / blocked / complete), and the critical path impacts.
• Deliver weekly status reporting that summarizes scenario counts and status, top risks/blockers, aging, and required decisions/escalations.
• Validation & Readiness
• Define and monitor readiness criteria, including test completions, access validation, and security approvals.
• Coordinate User Acceptance Testing and scenario validation with clear acceptance criteria.
• Prepare a go-live readiness report and obtain formal sign-off.
• Deliverables
• Integrated program plan detailing milestones, dependencies, and owners.
• Workstream plans with specific outputs and timelines.
• Migration runbook outlining cutover steps, roles, and rollback plan.
• Weekly status reports featuring KPIs and executive summaries.
• Risk and issue log including mitigation actions and ownership assignments.
• Go-live readiness report and accompanying sign-off documentation.
• Roles & Responsibilities
• Program Lead: Responsible for delivery, governance, and cross-functional coordination. Maintains the integrated program plan, reporting, and manages risks and escalations.
• Partners with onboarding/migrating teams to remove tenant-onboarding blockers and keep onboarding moving. Coordinates with the Program Lead on prioritization and sequencing, drives follow-ups and escalations, and reports scenario-level status, risks, and blockers. This role does not execute every team’s migration tasks;
• migrating teams remain accountable for migrating their own data, configurations, and workloads.
• Client Stakeholders (IAM, Engineering, Security, Platform, Migrating Teams): Provide requirements, constraints, and technical inputs. Execute assigned workstreams, including performing migrations for their owned scenarios, and participate in validation and approvals.
• Program Success Criteria
• Onboarding is delivered within the agreed timeline, with allowable variance.
• No Sev1 or critical defects are present at go-live.
• All readiness criteria are met and formally signed off.
• Risks are actively managed, with no unmitigated critical exposures.