EK
Ephrem KutureNetwork Infra PO · Delivery Lead
Selected Case Studies

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

Each case study covers the problem, scope, my accountability, what I decided, execution, constraints and mitigations, outcome, and sanitized evidence.

All screenshots, diagrams, workflows, ticket numbers, dashboards, IPs, vendor names, and infrastructure details are sanitized, anonymized, blurred, or recreated with mock data.

Problem

A live-campus DAS upgrade touches carrier equipment, headend gear, fiber and copper runs, power, rack space, cybersecurity review, and building access. Without one coordinating owner, dependencies surface late and work windows collide with operations.

Scope

  • Six campus buildings in an occupied, operating environment
  • Network infrastructure readiness: rack space, power, fiber/copper pathways, switch connectivity
  • Carrier and integrator scheduling, access, and change windows

My accountability

  • Coordinated network infrastructure delivery (not the carrier's RF design)
  • Structured the workstream in Azure DevOps as features, stories, and tasks with acceptance criteria
  • Tracked dependencies across carrier, integrator, network engineering, facilities, and security
  • Raised and escalated blockers; reported status to leadership

Technical & business decisions — what I decided

  • Sequenced work building-by-building so readiness gates (power, rack, pathway) were confirmed before vendor dispatch
  • Treated access permits and change windows as tracked dependencies, not side conversations
  • Kept carrier-owned scope and internal network scope as separate backlog items to keep accountability clear

Execution

  1. 01Baseline scope and responsibilities with carrier and integrator
  2. 02Break building work into ADO features/stories with readiness acceptance criteria
  3. 03Confirm rack, power/PDU, and fiber/copper readiness per building
  4. 04Schedule access and change windows with facilities and change management
  5. 05Run recurring delivery and risk check-ins; escalate blockers
  6. 06Track post-work verification items to closure

Constraints & mitigations

ConstraintOccupied buildings with limited work windows
MitigationPlanned around approved change windows and access permits
ConstraintMultiple external parties with separate schedules
MitigationSingle tracked dependency list and recurring coordination cadence
ConstraintShared rack space and power
MitigationConfirmed elevations and power capacity before install dates

Outcome

  • Network infrastructure readiness coordinated across all six buildings in scope
  • Clear ownership boundaries between carrier, integrator, and internal teams
  • Leadership visibility through ADO-based status reporting

Lessons learned

"A multi-building DAS program lives or dies on dependency management. My job was to make readiness gates visible early and keep every party working from the same list."