The core idea
Define the output and acceptance checks, divide the work, identify dependencies, assign owners and review progress against evidence. When a change arrives, reconsider scope, time and resources together rather than silently absorbing it.
1. Define what the project will deliver
A deliverable is a result that someone can inspect: a checked timetable, an information sheet or a completed event record. 'Improve awareness' is an aim, but it does not by itself specify what the team will make. State the intended users, the output, the deadline and the acceptance checks. For a bilingual sheet, these might include accurate dates, equivalent meanings, readable text and an approved contact route. Write what is outside the current scope so that a useful suggestion does not silently become a promised task. Identify the person who can approve the result. Completion is not merely the moment the writer stops typing; it is the point at which the agreed checks and handover are satisfied.
Sources: IIT Madras NPTEL: Project Planning and Control, time-management overview ↗ · IIT Kharagpur NPTEL: Project Management course outline ↗
2. Break the result into manageable tasks
Work breakdown means dividing the project into parts small enough to assign, estimate and check. Use an action and an output: 'confirm the dates from the organiser' is clearer than 'information'. For each task, name one person responsible for coordinating completion, even when several people contribute. Also name the reviewer where checking is separate. Avoid treating 'everyone' as an owner, because each person may assume somebody else is acting. Include work that is easy to forget: collecting permission, checking a translation, exporting a readable file, testing a link and handing over the final version. The list should cover the agreed output without becoming a catalogue of every keystroke. A useful task ends with evidence that the next person can use.
Sources: IIT Madras NPTEL: Project Planning and Control, time-management overview ↗ · IIT Kanpur NPTEL: Introduction to Effective Communication ↗
3. Separate effort from elapsed time
Effort is the amount of work, often expressed in person-hours. Elapsed time is how long the sequence takes from start to finish. A dependency means that one task needs an earlier result: translation may need an agreed draft, and publication may need review. Two people can sometimes work in parallel, but adding people does not remove every dependency. Estimate each task, record the assumptions and check when the people or equipment are actually available. A six-hour task done by one learner for two hours each evening spans three evenings. Leave room for checking and plausible rework instead of treating every estimate as certain. When the plan does not fit, change scope, timing or resources explicitly; do not make the arithmetic appear to fit by hiding necessary work.
Effort and elapsed time answer different questions
| Task | Hours | Must wait for |
|---|---|---|
| A · Confirm content | 2 | Start |
| B · Write draft | 4 | A |
| C · Translate | 3 | B |
| D · Prepare layout template | 2 | B |
| E · Combine and check | 1 | Both C and D |
| F · Correct and release | 1 | E |
Effort: 2 + 4 + 3 + 2 + 1 + 1 = 13 person-hours
Elapsed sequence: A → B → (C and D in parallel) → E → F
2 + 4 + max(3, 2) + 1 + 1 = 11 hours
Sources: IIT Madras NPTEL: Project Planning and Control, time-management overview ↗ · IIT Kharagpur NPTEL: Project Management course outline ↗ · IIT Madras NPTEL: estimating activity duration ↗
4. Monitor outputs and prepare for uncertainty
Use a short task board with states such as not started, in progress, awaiting review and accepted. Define the states so that 'done' does not mean different things to different people. Ask what evidence moved a task to the next state. A draft that exists but has not been checked should not appear as an approved deliverable. Keep a small risk record: what might happen, its effect, an early sign and a response. If the only reviewer may be unavailable, arrange a review slot or an authorised alternative early. Distinguish a risk from an issue that has already occurred. At a brief check-in, focus on decisions and blocked dependencies rather than asking everybody to perform a long recital of activity.
Sources: IIT Kharagpur NPTEL: Project Management course outline ↗ · NCERT: Employability Skills, Class XII ↗ · IIT Madras NPTEL: estimating activity duration ↗
5. Worked plan: a bilingual information sheet
Consider an invented project with these estimates: confirm content, two hours; write the draft, four hours after confirmation; translate, three hours after the draft; prepare a layout template, two hours after the draft; assemble and review the sheet, one hour after both translation and the template; correct and release, one hour after review. Total effort is 2 + 4 + 3 + 2 + 1 + 1 = 13 person-hours. If separate suitable people can translate and prepare the template at the same time, the shortest sequence under these assumptions is 2 + 4 + 3 + 1 + 1 = 11 hours. The parallel branch takes three hours because both tasks must finish. Having two people available for eight hours gives sixteen person-hours of capacity, but it does not make this eleven-hour sequence fit into eight hours. The team must change the plan rather than confuse capacity with duration.
Sources: IIT Madras NPTEL: Project Planning and Control, time-management overview ↗ · IIT Kharagpur NPTEL: Project Management course outline ↗ · IIT Madras NPTEL: estimating activity duration ↗
6. Worked decision: a useful request arrives late
The same team is asked to add a second audience version shortly before delivery. It estimates three extra hours of drafting and checking, but only two hours remain before the agreed handover. Automatically accepting the request would threaten the existing checks. The coordinator records the requested change and presents options: deliver the approved scope on time and add the version later, move the handover, or remove another agreed item with the approver's consent. Merely assigning a new person may not solve the problem if that person still needs the final source text and reviewer. The approver chooses the first option. The team records the new version as a separate follow-up deliverable, including its owner and review date. The request is respected without silently changing what 'complete' means.
Sources: IIT Kharagpur NPTEL: Project Management course outline ↗ · IIT Kanpur NPTEL: Introduction to Effective Communication ↗
7. Hand over, close and improve the next plan
At the end, compare the result with the acceptance checks and obtain the agreed approval. Hand over the authoritative files, instructions and any remaining limitations. Record which version is final and who maintains it; remove confusion created by draft copies. Then hold a short review of the process. Compare estimates with actual effort, identify one helpful practice and one change for next time. Avoid blaming a person for a dependency the plan never recognised. Equally, do not hide an unfinished requirement by calling it a lesson learned. Close or explicitly transfer outstanding work. The practical value of a small project is both its output and the team's improved ability to plan, explain decisions and cooperate on the next one.
Sources: IIT Kharagpur NPTEL: Project Management course outline ↗ · NCERT: Employability Skills, Class XII ↗
PUT IT INTO PRACTICE
Practice: calculate and review a small plan
- Use five tasks: confirm facts, two hours; draft, three hours after confirmation; translate, two hours after drafting; prepare a layout template, one hour after drafting; assemble and check, one hour after both branches. Write the dependencies.
- Calculate total effort: 2 + 3 + 2 + 1 + 1 = 9 person-hours. Explain that this adds all tasks, including both parallel branches.
- With separate people for translation and the layout template, calculate the shortest sequence: 2 + 3 + 2 + 1 = 8 hours, before adding waiting or rework.
- Name an acceptance check and one risk response. For example, verify equivalent dates in both languages and book the reviewer early; a task is not accepted merely because a file exists.
Check your understanding
Is 'raise awareness' a complete deliverable definition?
No. Specify what will be produced, for whom, by when and how it will be checked.
Why assign one coordinating owner to a shared task?
So responsibility for bringing the task to completion is clear even when several people contribute.
Why is the example's effort thirteen hours but sequence eleven?
Translation and layout can overlap with separate suitable people, but the review waits for both.
Can sixteen person-hours of capacity guarantee completion in eight elapsed hours?
No. The eleven-hour dependency sequence still constrains this example.
What should happen when scope changes?
Reassess work, timing, resources and approval, then record the agreed change.
Does a retrospective replace unfinished work?
No. Complete it or explicitly transfer it; learning from the process is a separate responsibility.