PMO Process Optimization Analyst

Position :

PMO Process Optimization Analyst Location :

Plano Tx Duration :

1 Year Role overview This is a process optimization and continuous improvement role embedded within the BYTE global delivery program. The PMO Process Optimization Analyst is responsible for identifying inefficiencies in the deployment lifecycle, defining and tracking KPIs that measure delivery performance, and systematically reducing the time and effort required to deploy solutions across new markets. This person works across delivery, engineering, and product teams - not as an administrator, but as a coordinator, process architect who makes every new market launch faster and smarter than the one before it. What this role is about Every new market deployment tends to rediscover the same problems and ask for the same things. This role exists to stop that. They facilitate identification of robust code modules and specific areas where configurations are needed and help Delivery Leads (DLs) explain this difference to each new market. The PMO Process Optimization Analyst will study how we deploy today, find what slows us down, and build the processes, playbooks, and reuse frameworks that progressively reduce implementation time. This is a facilitator and builder role, wherein you are building the process and baseline for how the BYTE program scales. Key responsibilities Process analysis and bottleneck identification: Map the end-to-end SDLC (Software development life cycle) for BYTE market deployments. Identify recurring bottlenecks, handoff failures, rework cycles, and delays. Document root causes and propose targeted fixes. ◦ Maintain a living bottleneck and improvement backlog with owners and timelines ◦ Run periodic process retrospectives across delivery teams Code and solution reuse facilitation: Work closely with engineering and delivery teams to identify configuration, code snippets, integrations, and solutions that have been deployed in prior markets and can be reused or adapted for new ones. ◦ Build and maintain a reuse catalog or knowledge base that delivery teams can access at the start of every new market engagement ◦ This person will not write code but must have enough prior development experience to recognize what is reusable and facilitate those conversations with engineers KPI definition and metrics ownership: Define and establish the delivery performance metrics for the program. This includes deployment cycle time, requirements churn, defect escape rates, UAT vs. SIT issue ratios, and any other indicators that reveal how efficiently we are delivering, specifically focused on go-live activities. ◦ Stand up dashboards or reporting mechanisms to make these metrics visible to leadership ◦ Track trends over time and flag regressions early SDLC best practices research and adoption: Actively research what other programs and organizations are doing to reduce implementation time. Bring back relevant practices, evaluate fit, and drive adoption where applicable.

Playbook and template ownership:

Maintain and improve the standard delivery playbooks, kickoff and discovery templates, onboarding kits, and process documentation. Ensure these are living assets that evolve based on lessons learned across markets.

Tooling efficiency:

Ensure Jira, Confluence, and related tools are configured and used in ways that support process efficiency. Identify gaps where tooling is adding friction instead of reducing it.

Lightweight delivery support:

In a limited capacity, support delivery leads with coordination and reporting tasks where process governance is at stake. This is not the primary function of the role.