Reviewed on 9 October 2026. Project management is the discipline of getting a defined outcome delivered within agreed limits of time, cost and quality, while keeping the people involved aligned. This guide covers the fundamentals every beginner should know: the project lifecycle, the core documents, how predictive and agile approaches differ, what the main standards say, and how to track progress with earned value. It ends with a worked example you can rebuild in a spreadsheet.
What makes something a project
A project is temporary work with a defined start, a defined end and a specific result. Running payroll every month is operations. Moving payroll to a new software system by 31 March is a project. That distinction matters because projects need things operations don't: an agreed scope, a plan, a sponsor, and an explicit point at which the work is accepted and closed.
Keep preparing
Continue with Sarkari Resume Templates₹299 — coaching के एक महीने से काफ़ी सस्ता / far cheaper than a month of coachingThe lifecycle in five stages
Most projects, whatever method they use, move through the same broad stages:
| Stage | Key question | Typical output |
|---|---|---|
| Initiation | Why are we doing this, and is it worth it? | Project charter or brief, with a named sponsor |
| Planning | What exactly will we deliver, and how? | Scope statement, work breakdown, schedule, budget, risk register |
| Execution | Are we building the agreed thing? | Deliverables, status reports |
| Monitoring and control | Are we on track, and what has changed? | Progress measures, change requests, updated risks |
| Closure | Is it accepted, and what did we learn? | Sign-off, handover, lessons-learned note |
Monitoring runs alongside execution rather than after it. Agile teams cycle through planning, building and review repeatedly in short iterations, but someone still has to initiate the work and formally close it.
Six documents worth knowing
- Charter or brief: the purpose, sponsor, high-level scope, constraints and success criteria.
- Scope statement: what is in, what is out, and how each deliverable will be accepted.
- Work breakdown structure (WBS): the deliverables broken into manageable pieces of work.
- Schedule: tasks, durations, dependencies and milestones.
- Risk and issue log: what might go wrong, its likelihood and impact, the owner and the response.
- Change log: every requested change, its effect on time and cost, and the decision taken.
On a small project these can each be a single page. What matters is that they exist and are kept up to date.
Predictive and agile approaches
| Predictive (often called waterfall) | Agile | |
|---|---|---|
| Scope | Defined in detail early | Expected to evolve; prioritised continuously |
| Delivery | Mostly at the end, or in large phases | In small increments, at regular intervals |
| Change | Controlled through formal change requests | Expected, and absorbed into the backlog |
| Fits best when | Requirements are stable and changes are costly (for example construction) | Requirements are uncertain and feedback is cheap (for example software) |
The Manifesto for Agile Software Development states four value pairs, such as valuing "responding to change over following a plan". Scrum is one widely used agile framework. The 2020 Scrum Guide defines Sprints as fixed-length events of one month or less, and the Daily Scrum as a 15-minute event for the Developers. Many real projects are hybrids: fixed milestones for contracts and approvals, with agile iterations inside them.
What the main standards say
The Project Management Institute (PMI) publishes the PMBOK® Guide. PMI's page lists the Eighth Edition with a publication date of November 2025. It describes six core principles and seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk. PMI says the edition reintroduces process guidance "in an evolved, non-prescriptive way". If you're studying for a PMI certification, check which edition and exam content outline your exam is based on before buying materials.
PRINCE2 is another recognised, process-based method with its own certification scheme. Different employers use different vocabularies, so learn the underlying ideas, not just one set of terms.
Worked example: tracking progress with earned value
Earned value management compares three numbers: what you planned to have done, what you have actually done, and what it has cost. The project below is illustrative.
A team is building an internal reporting dashboard. The approved budget at completion (BAC) is ₹20,00,000, spread evenly over 10 weeks. At the end of week 4:
- Planned value (PV): 4 of 10 weeks' work was planned, so 40% × ₹20,00,000 = ₹8,00,000.
- Earned value (EV): 35% of the work is actually complete, so 35% × ₹20,00,000 = ₹7,00,000.
- Actual cost (AC): the team has spent ₹7,50,000.
| Measure | Formula | Result | What it tells you |
|---|---|---|---|
| Schedule variance (SV) | EV − PV | −₹1,00,000 | Behind schedule |
| Cost variance (CV) | EV − AC | −₹50,000 | Over budget for the work done |
| Schedule performance index (SPI) | EV ÷ PV | 0.875 | About 87.5% of the planned progress |
| Cost performance index (CPI) | EV ÷ AC | about 0.933 | About ₹0.93 of value earned per ₹1 spent |
| Estimate at completion (EAC) | BAC ÷ CPI | about ₹21,42,857 | Forecast total cost if cost performance stays the same |
Checking the last line: ₹20,00,000 ÷ (7,00,000 ÷ 7,50,000) = ₹20,00,000 × 750 ÷ 700 ≈ ₹21,42,857. This forecast assumes current cost efficiency continues. If the overrun came from a one-off cost, the forecast will be too pessimistic, so explain the cause alongside the number.
An index below 1.0 isn't a verdict; it's a prompt to ask why. Is a task harder than estimated? Is a dependency late? Has scope grown without a change request? The answers should go into your risk and change logs.
Fundamentals checklist for your first project
- A one-page charter with a named sponsor and success criteria
- A scope statement with explicit exclusions and acceptance criteria for each deliverable
- A work breakdown with an owner for every task
- A schedule that shows the dependencies, not just dates
- A risk log reviewed at least every two weeks
- A change log; no scope change without a recorded decision
- A weekly status note covering progress, risks, decisions needed and next steps
- A closure note covering acceptance, handover and three lessons learned
Building these skills for a job search
Freshers can show project management fundamentals through college fests, research projects or internships. Describe the scope you managed, the schedule you kept, a risk you handled and how the result was accepted. For a worked exercise on scope, dependencies and acceptance, see our project management skills guide. Certifications can help later, but evidence that you've actually run something, with documents to show for it, counts for more at the start.