Project Management by Level: A Roadmap
❦
The Bachelor's Student
Goal: learn the essentials, deliver a well-scoped project on time, and work effectively in a team.
| Stage | Key actions |
| Start | Write a one-page charter; agree the scope with the supervisor; form a team agreement if in a team |
| Plan | Build a simple WBS; make a weekly plan; list the top five risks |
| Do | Meet weekly; track tasks on a board; keep a log of decisions |
| Control | Compare progress with plan each week; raise problems early |
| Close | Finish deliverables early; allow time for formatting; reflect on lessons |
Core skills: planning basics, teamwork, communication, and time management.
The Master's Student
Goal: plan and carry out a larger, more independent project, balancing depth with a firm deadline.
| Stage | Key actions |
| Start | Write a charter and a proposal; check feasibility and ethics early |
| Plan | WBS, critical path, buffer, and a risk register; plan data access first |
| Do | Work in cycles; draft as you go; hold regular supervisor meetings |
| Control | Track milestones; manage scope; adjust the plan when needed |
| Close | Plan a three-month finishing period; archive data; prepare for defense if applicable |
Core skills: realistic scoping, risk management, supervisor management, and writing discipline.
The Doctoral Candidate
Goal: lead a multi-year research program, producing original work and a body of outputs, while developing as an independent professional.
| Stage | Key actions |
| Start | Define the question and contribution; choose a supervisory team; plan the first year in detail |
| Plan | Use a stage-gate structure with annual reviews; plan publications and conferences; prepare a data management plan; build a rolling plan, detailed for the next six months and outlined beyond |
| Do | Manage a portfolio of papers, experiments, teaching, and collaboration; supervise junior researchers; maintain reproducibility |
| Control | Review the plan twice a year; record changes; manage supervisor and funder expectations |
| Close | Plan the final year backward from submission; protect writing time; prepare for the examination and for the next career step |
Core skills: long-horizon planning, resilience, collaboration, grant and budget management, leadership, and wellbeing.
Competency Progression
| Competency | Bachelor's | Master's | Doctoral |
| Planning | Follows a plan | Creates and adjusts a plan | Designs a strategic, rolling plan |
| Scope | Accepts a defined scope | Defines and defends scope | Shapes scope across a program |
| Risk | Identifies basic risks | Manages a register | Anticipates and absorbs long-term risk |
| People | Works in a team | Manages a supervisor and partners | Leads a team and network |
| Communication | Reports progress | Presents and writes clearly | Communicates to varied audiences, including funders |
| Governance | Follows rules | Navigates approvals | Understands institutional and funding governance |
Fifteen Common Mistakes
1. Starting without a clear question or scope.
2. Underestimating time and ignoring the planning fallacy.
3. No buffer in the schedule.
4. Leaving ethics or approvals to the last minute.
5. Not talking to the supervisor often enough.
6. Letting scope creep.
7. Not tracking progress against a plan.
8. Ignoring risks until they become issues.
9. Working in isolation.
10. Poor data management and no backups.
11. Leaving writing to the end.
12. Multitasking instead of finishing.
13. Not recording decisions and changes.
14. Neglecting health and rest.
15. Skipping closure and lessons learned.
Three Short Case Examples
Bachelor's capstone. A team of four engineering students designs a low-cost water-quality sensor for a local community group. In week one, they write a team agreement, define success criteria with the client, and build a WBS. A risk review identifies that a key component has a six-week delivery time, so they order it in week two and begin with a substitute for testing. They hold a weekly stand-up and a design review in week six, and they finish with two weeks of buffer for testing and documentation.
Master's thesis. A part-time student plans a mixed-methods study. She builds a WBS, lists ethics approval as the critical dependency, and submits the application in month two, not month four. When recruitment is slow, her risk register already lists a fallback plan: widening recruitment to a second site. She uses a weekly Kanban board and schedules writing blocks, and she submits two weeks before the deadline.
Doctoral program. A candidate funded by a research grant plans a four-year project with annual gates. At the end of year one, a pilot shows that the original method is unreliable. Because the plan had a rolling horizon and the supervisor team had agreed a "plan B" path, the candidate changes the method, documents the change with the funder, and still delivers two papers by year three.
CHAPTER 22