What is project management? From an idea to accepted work
Learn project management through a maintenance-request pilot: purpose, scope, planning, team decisions, testing and an accepted handover into normal work.
Maintenance requests arrive by phone, email and handwritten notes. The facilities manager wants one request form and a shared queue. Someone is asked to “get it done next month”.
That is a starting idea. It still leaves the team guessing about who uses the form, what counts as urgent and who will support it after launch.
Project management organises temporary work so a team can deliver an agreed result within its constraints. It connects the purpose, people, plan, decisions and acceptance checks. APM's definition emphasises objectives, acceptance criteria and agreed parameters.
Building this new request route is a project. Handling tomorrow's maintenance requests is ongoing operations. The project should leave the operating team able to do that job.
Agree what the project is for
Take a fictional four-week pilot in one office building. The aim is to make routine maintenance requests visible and assign each to a responsible person. Emergency calls retain their existing route.
The facilities manager sponsors the pilot and approves its scope and funding. A project manager coordinates the work. The service desk will own the queue afterwards; IT approves the technical connection and access arrangements.
Before buying a tool, agree what the pilot must deliver: an approved request form, tested routing, appropriate access, trained users and a support arrangement. A budget of €6,000 and four weeks are assumed limits here, not estimates for a real implementation.
The project charter example shows how to record that authority. It prevents enthusiasm for a useful idea from becoming permission to change every maintenance process.
Build a plan people can carry out
The project manager breaks those deliverables into work, checks dependencies and confirms who has time to do it. A scheduled IT task is only credible if the IT owner has accepted the allocation.
The form and routing rules need to agree before testing. Training needs a stable version to demonstrate. Handover needs the support team to see how failed requests are recovered.
A work breakdown structure helps define the deliverables. A RACI matrix clarifies who does and approves the work. Neither supplies time or authority on its own.
Keep a few uncertainties visible: perhaps the existing system cannot send the required notification, or an approver will be away during the pilot. Assign someone to check each assumption before it threatens the finish.
What does the project manager actually do?
Suppose IT discovers that attaching photographs needs an extra security review. The project manager needs a decision: remove attachments from the pilot, allow more time, or fund the review if the right people are available.
| Work in this pilot | Skill it calls for |
|---|---|
| Turn “make requests visible” into testable requirements | Clarifying needs and checking understanding |
| Reconcile routing, access and training dates | Planning dependencies and resources |
| Present the attachment trade-off to the sponsor | Explaining options, consequences and a decision deadline |
| Check a failed notification with the service desk | Listening, investigating and following through |
Communication runs through that work. The familiar claim that managers spend 90% of their time communicating is not a reliable time budget for every project. Here, the sponsor needs a clear choice about attachments, regardless of how many updates the team sends.
The balance of skills changes with the assignment. A construction job needs different technical judgement from this software pilot, alongside planning and people skills.
Deliver, test and hand over
Before launch, send test requests through the whole route. Check ordinary work, missing information, an unavailable assignee and a failed notification. Record what happened and resolve defects against the agreed requirements.
The sponsor decides whether the pilot is acceptable. The service desk accepts the instructions, access and support arrangements it will maintain. Project handover goes into those checks.
After launch, follow whether requests reach the right owner and get resolved. Opening the form is not evidence that maintenance service improved. A named operating owner needs the follow-up date and the records.
Five basics are not five compulsory phases
Purpose, scope, time, cost and quality are five useful things to agree. They are not phases to complete one after another. A lifecycle describes how work progresses from beginning to end; process groups describe management activities that may recur during it.
APM's lifecycle guidance describes linear, iterative and hybrid arrangements. In our pilot, planning and testing may repeat as the team learns. A fixed sequence of seven stages would not make that learning disappear.
For the next small project, write down the result, its acceptance checks, the sponsor and the operating owner first. Then build a feasible plan between them. That gives the team a clearer assignment than a launch date alone.
Sources and example notes
- APM: What is project management?, definition and responsibilities, referencing its Body of Knowledge, eighth edition.
- APM: Project life cycles, approaches and variation.
- PMI conference paper, 2008, the distinction between process groups and lifecycle phases in the edition discussed there.
The maintenance pilot, roles, budget and duration are fictional. The four-stage drawing is an explanation of this pilot, not a professional-body standard.