A network infrastructure and structured cabling project supporting IT connectivity inside an active production environment — my first full engagement as Project Manager.
As Project Manager, I owned delivery end-to-end: scope, schedule, stakeholder alignment, and the internal engineering coordination needed to keep the build on track.
Partway through implementation, additional scope requirements were introduced. Absorbing changes without discipline risks schedule slips and rework — the project needed a controlled way to evaluate and incorporate them.
Rather than accepting the change immediately, I assessed its impact, discussed feasibility directly with the internal engineering team, and aligned with stakeholders before incorporating the approved changes into the project plan. That sequence — assess, discuss, align, incorporate — is how I handle scope change on every project since.
The added scope was evaluated, aligned with stakeholders, and delivered as part of the project plan rather than as uncontrolled rework.
Change is inevitable on infrastructure projects — the discipline is in how it's assessed, not whether it's accepted. Talking to engineering before the customer keeps commitments realistic.