Project management basics: from plan to result

What a project is, the life cycle, SMART goals, scope, breaking down work, Gantt charts, responsibility, risks, Waterfall and Agile.

Organising a mahalla celebration, holding a school leavers’ evening, introducing new software at the office, starting a family renovation: all of these are small projects. Many people run them “however it turns out”: a few people, hundreds of messages in a group chat, a last-minute rush and the eternal question “who was supposed to do that?”. Project management is a set of simple techniques that reduce exactly this kind of chaos. In this guide we cover what a project is and how it differs from ordinary work, the five stages of the project life cycle, setting goals with the SMART method, scope and “scope creep”, breaking work down into parts, Gantt charts and milestones, assigning responsibility, communicating with stakeholders, the risk register, the Waterfall and Agile approaches, and closing a project properly. We follow every stage through one example: a summer reading club for children at a mahalla library. At the end you will find common mistakes, a practice exercise and a checklist.

What a project is and how it differs from ordinary work

A project is temporary work carried out within a set period to achieve a specific result. The definition has two key words:

Temporary. A project has a beginning and an end. The leavers’ evening is over, so the project is finished.
Specific result. At the end of a project something is created or changed: an event takes place, a room is renovated, a new course is launched.

Ordinary work (a process) repeats and has no end. A librarian lends and takes back books every day: that is a process. If she organises a six-week club for children over the summer, that is a project. The difference matters because a project is managed differently from a process: everything in it is done for the first time, and without a clear plan the deadline and the result easily “drift”.

Another feature of a project is its constraints. Every project is limited by three things: scope (what we do), time (by when) and resources (who and with what). If one changes, the others change too: if the scope grows, you need more time or more people. This is sometimes called the “project triangle”.

Our example: Dilnoza Yusupova, the librarian at a mahalla library, wants to run a reading club for children during the summer holidays. She is helped by Sardor Aliyev, a volunteer teacher, and Gulchehra opa, a mahalla activist. All figures and dates below are illustrative.

The project life cycle: five stages

Every project, large or small, goes through five stages. The boundaries between them are not always sharp, but knowing them helps you see in advance what needs to be done.

Initiation. Why is this project needed? What result is expected? Who makes the decisions? At this stage the idea becomes a short, one-page document.
Planning. What work has to be done, who does it, by when, and what might get in the way. The stage that takes the most time, but also saves the most.
Execution. The plan is put into action: people work, meetings take place, the result is created.
Monitoring and controlling. Runs alongside execution: is the work going to plan, are there problems, what needs to change.
Closing. The result is handed over, documents are put in order, the team is thanked and lessons are written down.

Many people skip the first and fifth stages: as soon as an idea appears they jump straight into doing, and once it is done they move on to the next thing without writing anything down. As a result, every new project starts from scratch.

Initiation: the goal, SMART and scope

Setting a goal with the SMART method

“Getting children interested in reading” is a good intention, but not a goal. How would you check it? When would it count as achieved? The SMART method sharpens a goal against five criteria:

S (Specific). What we will do and for whom.
M (Measurable). How we will measure the result.
A (Achievable). Whether it can be done with the people and time available.
R (Relevant). Whether this goal genuinely matters to the organisation or team.
T (Time-bound). By when.

Dilnoza’s goal in SMART form: “In July and August, over six weeks, run a reading club twice a week for children aged 9 to 12; at least 15 children should take part, and each participant should read at least three books and give a short talk about them.” The figures are illustrative, but now at the end there is a clear answer to the question “did it work?”.

Scope and scope creep

Scope is what the project includes and, even more importantly, what it does not. For the club, the scope includes the session timetable, the book list, registration and the closing event. It does not include renovating the library, a club for adults or online sessions. Writing such a list down may seem unnecessary, but it is exactly what prevents many arguments later.

Scope creep is when small extra requirements are added as the project goes on and the plan quietly grows. “It would be nice if the children drew pictures too”, “Let’s hold a meeting for parents as well”, “There should be a concert at the end too”: each idea is reasonable on its own, but together they break the deadline and wear the team out.

A simple rule against it: write down every new suggestion and ask three questions. Does it serve the goal? Who will do it and when? What will we give up in exchange? If there is no answer, move the suggestion to an “ideas for the next project” list. That is not “no”, it is “not now”.

Planning: breaking down work, time and responsibility

Breaking work into parts (WBS)

You cannot plan a large piece of work as one whole. The idea behind a Work Breakdown Structure (WBS) is simple: you split the final result into a few large parts and each part into specific small tasks. A task should be small enough for one person to finish in a few days, and for the question “is it done?” to have a clear “yes” or “no” answer.

An illustrative breakdown for the club:

Preparation: draw up the book list, check the books on the shelves, agree the room and the timetable.
Registration: write the announcement, share it in the mahalla group chat and at the school, keep the list.
Sessions: prepare a topic and questions for each week, run the sessions, record attendance.
Closing event: put together the programme, invite parents, prepare certificates of thanks for participants.
Closing the project: count the results, write a short report, hold a lessons meeting.

You can keep such a list in Google Docs or an ordinary notebook. If the whole team maintains it, working in one shared document is convenient: everyone leaves a comment next to their own task. Our article on collaborating in Google Docs explains how this works.

Schedule, dependencies and milestones

Once the task list is ready, each task gets a deadline and its dependencies. A dependency means one task cannot start until another has finished. For example, you cannot write the announcement until the book list is ready, because the announcement says what we will be reading. Not knowing the dependencies is the most common cause of delays.

A Gantt chart makes the schedule visible: tasks on the left, days or weeks along the top, and each task shown as a horizontal bar as long as it lasts. At a glance you can see what runs in parallel and which task is waiting for another. You do not need special software: in Google Sheets it is enough to put the weeks in columns and colour in the relevant cells. For automatic colouring you can use Format → Conditional formatting.

Milestones are the key events in a project; they have no duration. For the club: “Book list approved”, “Registration closed”, “First session held”, “Closing event held”. Milestones are handy for monitoring: when you reach each one, the team pauses and checks against the plan.

When planning, take personal time into account too: volunteers give their time after their main job. Our article on time management covers this in detail.

Resources and responsibility (simplified RACI)

Resources are the people, time, space and equipment a project needs. For the club: a room, tables, books, a whiteboard and volunteers. Find out in advance whether each is available and whom you need to ask.

A RACI chart is used to assign responsibility. The full version has four roles, but a simplified version is enough to start with:

R (Responsible). Actually does the work.
A (Accountable). Answers for the result. Only one person per task.
C (Consulted). Asked for their opinion during the work.
I (Informed). Told about the result.

For example, for the task “Share the announcement”, Gulchehra opa is responsible, Dilnoza is accountable, the school’s deputy head is consulted, and the mahalla chair is informed. The most important rule: every task must have exactly one accountable person. A task that “we will all do together” is usually done by no one.

Stakeholders and the communication plan

Stakeholders are any people or groups who affect the project or are affected by it. In the club example: children, parents, the library management, the school, mahalla activists and volunteers. Each has their own expectations: parents expect safety and a clear timetable, the library management expects the books to come back in good condition, and children expect interesting sessions.

A simple method is to draw up a table: who they are, what matters to them, how they can influence the project, and what, how and how often we tell them. The last columns of this table form the communication plan:

Within the team: a 15-minute meeting once a week and a shared chat.
Parents: a short letter at registration and a reminder in the group chat before each session.
Library management: a short message when milestones are reached.
The school: an announcement at the start and a message about the results at the end.

A communication plan does not mean “everyone should know everything”. Each person should get the information they need at the right time. You can read about writing clearly and briefly in our article on workplace communication, and about team agreements in the one on teamwork.

The risk register: likelihood and impact

A risk is an event that has not happened yet but would affect the project if it did. The aim is not to remove every risk, but to foresee them and have a plan.

A risk register is a simple table: the risk, its likelihood, its impact, preventive measures, what we will do if it happens, and who is responsible. Rating likelihood and impact as “low, medium, high” is enough. Risks where both likelihood and impact are high need attention first.

Illustrative examples for the club:

Too few children sign up. Likelihood medium, impact high. Measure: share the announcement early, both at school and in the mahalla group chat. If it happens: extend registration by a week.
A volunteer falls ill. Likelihood medium, impact medium. Measure: one back-up person for each session. If it happens: Dilnoza runs the session.
The room gets stuffy on hot days. Likelihood high, impact medium. Measure: schedule sessions in the morning.
Not enough copies of the books. Likelihood medium, impact medium. Measure: build the list around the number of copies on the shelf and put children in pairs.

Do not draw up the register once and forget it: at every weekly meeting, set aside two minutes to ask “has any new risk appeared?”.

Execution, monitoring and closing

During execution the main job is to work to the plan and notice changes in good time. Monitoring does not need a complicated system:

A short weekly meeting. Three questions: what was done, what is planned, what is getting in the way.
Task status. Each task is marked “to do”, “in progress” or “done”. This is easy to show on a board or in a spreadsheet.
Checking milestones. When you reach each one, look at the Gantt chart and judge whether you are behind.
Recording changes. If the plan changes, briefly write down what changed, why, and who decided.

If you find you are behind, do not panic. There are three options: reduce the scope, move the deadline or find extra help. The accountable person decides which one, after consulting the stakeholders.

Closing is the most often forgotten stage of a project. It includes comparing the result with the goal (how many children took part, how many books were read), returning the books to their place, thanking volunteers and partners, writing a short report and holding a lessons meeting.

At the lessons learned meeting the team answers three questions: what worked well, what did not go as expected, and what we will do differently next time. For example: “Morning sessions brought in more children”, “We started registration too late”. Write the answers down and put them in the club’s folder for next year. That way the next project starts not from scratch but from experience.

Waterfall and Agile: two approaches

There are two main approaches to managing a project.

Waterfall means the stages are done one after another: first the full plan, then execution, and the result at the end. It suits projects whose requirements are clear in advance and change little: a leavers’ evening, a renovation, an event. Its strength is clarity and a deadline known in advance. Its weakness is that it is hard to adapt halfway through.

Agile splits the work into short cycles; at the end of each one a result is shown and the next step is adjusted based on feedback. It suits work whose requirements are not fully known in advance: building software, trialling a new service, developing a training course. Agile includes some well-known methods:

Scrum splits the work into “sprints” a few weeks long, with clear team roles and regular meetings.
Kanban moves tasks across the columns of a board and limits how many tasks are in progress at once. Read more in our article on the Kanban method.

In practice, many projects use a mixed approach. In the club example, the overall plan and milestones follow the Waterfall style, while the content of the weekly sessions is adjusted Agile-style to the children’s interests.

Common mistakes, a practice exercise and a checklist

Common mistakes

A vague goal. “Hold a good event” cannot be measured. Sharpen it with SMART.
Scope not written down. If nobody says what is out of scope, the scope grows by itself.
“We are all responsible”. Without one accountable person per task, the work stalls.
Dependencies ignored. One delay pushes back the whole plan like a chain reaction.
Risks not thought through. The most damage is done not by the unexpected problem but by the one that could have been foreseen.
A plan made and then forgotten. A plan is a living document; review it every week.
Closing skipped. If lessons are not written down, the mistakes are repeated next time.

Practice exercise: a school leavers’ evening

Imagine you are a member of the school parents’ committee and you have been asked to organise the leavers’ evening. The example is illustrative. Complete the following steps in Google Docs or Google Sheets:

Write a one-page project description: why, for whom, when.
Write the goal in SMART form as a single sentence.
Write the scope as two lists: “in scope” and “out of scope”.
Break the work into 4 to 5 large parts, and each part into 3 to 5 small tasks.
Draw a simple week-by-week Gantt chart in Google Sheets and mark 3 to 4 milestones.
Give each task one accountable person and one person responsible for doing it.
Draw up a stakeholder table and a communication plan.
List at least five risks and rate their likelihood and impact.
Write down in advance the three questions for the lessons meeting once the project is over.

Checklist before starting a project

The goal is written in SMART form.
Scope: it is clear what is in and what is out.
The work is broken into small, checkable tasks.
Every task has a deadline, dependencies and one accountable person.
Milestones are marked.
The stakeholders and communication plan are ready.
The risk register is drawn up and reviewed weekly.
Closing and the lessons meeting are in the calendar.

Project management is not only for large companies. A mahalla celebration, a school evening or a family renovation: in each case these simple techniques save time and nerves and protect relationships. Start with a small project and use a few more techniques each time.

If you would like to learn project management systematically with a teacher, take a look at our association’s free project management programme and our other training programmes. When you are ready, submit an application and our specialists will get in touch.