ICT Project Management Fundamentals for RTPM Candidates
Scope, Stakeholders, and the Project Lifecycle
An ICT project is a temporary effort with a defined start and finish, producing a unique deliverable such as a structured cabling system, a data center fit-out, or a wireless deployment. Understand the difference between a project and ongoing operations: moves, adds, and changes are operational work, while a new building cabling build is a project. Know the lifecycle phases - initiation, planning, execution, monitoring and control, and closure - and what deliverable closes each one. Initiation produces the charter and stakeholder register; planning produces the scope baseline, schedule, budget, and risk register; closure produces as-built documentation, acceptance sign-off, and lessons learned.
Candidates must be comfortable with the RACI model (responsible, accountable, consult, inform), the triple constraint of scope, schedule, and cost balanced against quality, and the role of the project manager as integrator rather than technical designer. Recognize the difference between a project sponsor, who authorizes and funds the work, and a champion, who advocates for it.
Traps to watch: Questions often blur the project manager with the RCDD designer. The PM manages scope, schedule, cost, risk, and communication; technical design authority stays with the qualified designer. Another trap is confusing a change request with a defect: a defect is nonconformance to the agreed baseline, while a change alters the baseline. Also watch for questions asking who approves scope changes - normally the sponsor or change control board, not the PM alone.
Rule of thumb: No baseline, no change control. If scope, schedule, or cost has not been formally baselined and approved, you cannot measure variance or process a change against it. Always confirm the approved baseline before answering any question about variance, earned value, or change requests.
Worked example: A client asks the PM to add 40 additional outlets mid-installation. The PM does not simply instruct the crew. The PM documents the request, assesses impact on schedule and cost, routes it to the change control board, and only after approval updates the baseline and issues the work authorization.