Network Infrastructure Product Owner — owning the what, the why, and the priority.
I own the network infrastructure backlog end-to-end. I turn requirements from engineering, facilities, cybersecurity, and business stakeholders into ranked epics, features, and stories that engineering teams can actually deliver.
Backlog Ownership
Own the Azure DevOps backlog for network infrastructure workstreams — grooming, structuring, prioritizing, and keeping it decision-ready.
Epics · Features · Stories
Break enterprise infrastructure requirements into epics, features, user stories, and tasks with clear scope and acceptance criteria.
PI Planning & Objectives
Contribute to PI planning: define PI objectives, sequence dependencies, negotiate scope with engineering, and commit realistic outcomes.
Acceptance Criteria
Write acceptance criteria that engineers, vendors, and QA can use to confirm 'done' — reducing rework and ambiguity.
Stakeholder Alignment
Translate needs from network engineering, facilities, cybersecurity, business, and leadership into ranked, deliverable work.
Roadmap & Product Families
Structure product families and roadmaps that show how tactical work rolls up to strategic infrastructure outcomes.
Voice of the Customer
Represent internal customers — engineers, campus operations, tenants — inside the delivery team.
Prioritization & Trade-offs
Balance risk, urgency, dependencies, vendor timelines, and construction windows against team capacity.