Detailed evidence of how I think, build, and deliver.

A live-campus 5G/DAS upgrade touches carrier equipment, headend gear, fiber runs, antenna placement, power, cybersecurity, and facility access. Without disciplined delivery ownership, this kind of program slips, cuts over poorly, and creates outages.

• Owned the delivery plan, milestones, and dependencies
• Structured epics, features, and stories in Azure DevOps
• Coordinated carrier, integrator, and internal engineering teams
• Aligned facilities, security, and construction on access and downtime windows
• Ran risk, dependency, and cutover reviews
• Reported delivery status to leadership via dashboards

1. 01Baseline scope with carrier and integrator
2. 02Break work into ADO epics/features/stories with acceptance criteria
3. 03Sequence dependencies against construction and facility windows
4. 04Run weekly delivery and risk reviews
5. 05Plan and rehearse cutover windows
6. 06Track post-cutover stabilization

• Predictable, well-coordinated 5G/DAS delivery
• Reduced cutover risk through structured planning
• Clear visibility for engineering, vendors, and executives
• Fewer surprises for facilities and end users

"A 5G/DAS program lives or dies on dependency management. The delivery lead's job is to make dependencies visible early and negotiate them relentlessly."