Software Program Manager

Position Summary

The Software Program  Manager will work as part of the Channel Partner Software organization to provide cross-functional program leadership for digital/softwareeffortsrelated to ourOEM partner enablement program – an extremelysignificantand high-visibility initiative for the NAM market.

This role will work across the digital teams contributing tothe project, as well as hardware stakeholders whose efforts intersect with the digital experience. The Software Program  Manager willestablishvisibility, drive accountability, surface and manage risks, andfacilitatealignment across contributing teams and stakeholders.

• Develop andmaintainan integrated view of the major initiatives, features, dependencies, milestones, and release activities acrossthe program.
• Coordinate commitments and dependencies across digital teams and relevant hardware andbusinessstakeholders.
• Lead the planning, preparation, facilitation, and follow-up activities associated withPI (Program Increment) planning.
• Coordinate significant efforts and milestones that fall outside formal PI commitments.
• Identify cross-team sequencing, resource, dependency, or timing conflicts andfacilitateresolution or escalation.
• Support release planning and readiness by coordinating required activities, owners, dependencies, decisions, and completion criteria across contributing teams.

• Drive accountability for PI commitments, program milestones, release activities, and other agreed-upon deliverables.
• Follow up with owners to confirm progress, surface blockers, and ensure that commitmentsremainactionable and current.
• Facilitate resolution of cross-functional blockers and elevate unresolved issues through the appropriate governance channels.
• Ensure that decisions, changes, and delays are reflected in program plans and communicated to affected stakeholders.
• Maintain clear ownership and due dates for program-level actions and deliverables.

• Maintain the Confluence program board database as the authoritative view of program-level efforts, milestones, ownership, dependencies, risks, and status.
• Establish andmaintainconsistent standards for how program status, milestones, risks, and dependencies are documented.
• Maintain a program-level decision and action log, including decisions made, responsible owners, next steps, and due dates.

• Proactivelyidentifyrisks to program commitments, releases, milestones, scope, budget, quality, and stakeholder alignment.
• Document and regularly review program risks, assumptions, issues, and dependencies.
• Establish clear ownership, mitigation actions, contingency plans, and escalation paths for significant risks.
• Monitor mitigation activities and ensure that unresolved risks are elevated before they materially affect delivery.

• Proactively communicate program status, milestones, risks, dependencies, decisions, and changes to relevant stakeholders.
• Tailor reporting to the needs of executive, business, product, technical, and operational stakeholders.
• Facilitatealignmentdiscussions, planning sessions, decision-making meetings, and project workshops as needed.

• Define clear objectives, agendas, expected outcomes, andrequiredparticipants for program-level meetings and workshops.
• Capture andmaintainconcise meeting summaries that document key discussion points, decisions, unresolved questions, actions, owners, and due dates.

• Manage and maintain visibility into Project Enable financials in partnership with program leadership and finance stakeholders.
• Identify and communicate financial risks, forecast changes, and funding needs.
• Ensure that financial assumptions, decisions, and ownership are clearly documented.

The Program Manager will coordinate and govern program-level delivery but will not replace the responsibilities of Product Managers, Product Owners, Scrum Masters, Engineering Managers, or technical leads.

The role will not be responsible for:

• Defining product strategy, customer outcomes, or feature prioritization, which remain owned by Product Management.
• Managing detailed Jira stories, tasks, acceptance criteria, or individual team backlogs.
• Making architecture, design, or engineering decisions on behalf of accountable technical owners.
• Directly managing the day-to-day work of contributing team members unless separately assigned as a…