Imagine walking a long mountain path with no signposts. The scenery is lovely, but after a few hours you start asking the same worrying question: how far have I come, and how far is left? Now imagine the same path with a small marker stone every kilometre. Nothing about the climb has become easier, yet you walk differently. You can pace yourself, you can feel each stretch finishing, and you can tell early if you have wandered onto the wrong trail. That is the whole idea behind a software project milestones approach, and this plain-language explainer shows how it works for learners and small teams.
The problem: big projects have no marker stones
Software work is invisible. You cannot see a half-built feature the way you can see a half-built wall, so progress is hard to sense. A learner building a first web application might work for weeks and still be unable to say whether they are a third or two-thirds of the way there. A small team might hold a meeting every Monday and still leave without a shared picture of what is finished.
When progress is invisible, two bad things happen. Motivation fades, because effort without visible results feels pointless. And problems hide, because nobody notices that a piece has been “almost done” for a month. Marker stones solve both.
What a milestone really is
A milestone is a small piece of work that is clearly either finished or not finished. That is all. It is not a deadline, not a phase and not a document. “Sign-up page shows a welcome message after the form is submitted” is a milestone. “Work on the sign-up flow” is not, because nobody can say when it is done.
There is one more ingredient, a done marker. This is something you can see when the milestone is finished: a ticked box, a green mark in a list, a card moved to a “finished” column. The marker matters more than people expect. Seeing a piece move from “not yet” to “done” gives a small, real feeling of progress, and that small lift carries you into the next piece, whatever your mood that day.
A short story: the first app
Consider a learner who decides to build a small notes application. At the beginning there is one giant task in their head: “build the app”. Weeks pass, and they feel stuck. A friend suggests drawing a line of marker stones instead.
They write six on a sheet of paper. One: the page opens and shows a title. Two: a note can be typed and appears on the screen. Three: the note stays after the page is refreshed. Four: a note can be deleted. Five: the notes appear in a tidy list. Six: the application is available at a web address anyone can visit.
Each of these takes an evening or two. After each one, the learner draws a tick. Within two weeks there are six ticks, and the application exists. Nothing about the learner’s skill changed overnight; what changed was that every evening ended with something finished.
How to cut a project into stones
You can do this for any project in four moves.
- Say where you want to end up. One sentence, in everyday words.
- List the pieces that must exist. Do not worry about order yet; just write them down.
- Shrink every piece until a day or two of effort would complete it. If a piece feels vague, ask what you would be able to see when it is done, and rewrite it around that.
- Put the pieces in a sensible order. Earlier pieces should make later ones possible.
If some of the words in your list feel unfamiliar, a glossary can help. The beginner glossary of fifty-plus delivery terms on this site is a handy companion for translating jargon into plain meanings before you write your own list.
Notice what the stones did for the learner’s evenings. Before, each session began with the same dull question of what to work on. Afterwards, the answer was always on the page: the next unticked stone. Deciding what to do is a surprisingly heavy part of any long effort, and the list quietly removes it. There was also a small surprise on stone three. Keeping a note after a refresh turned out to be harder than expected, so it was split into two stones, one for saving and one for loading. The learner did not feel behind; they felt the plan was working, because the marks had told them exactly where the difficulty lived.
Reading the stones: what the marks tell you
Once the stones are in place, they do more than cheer you up. They tell you things.
- If stones are passing quickly: your pieces may be too small, or you are on easy ground. Consider merging a few, or the list itself turns into homework.
- If one stone sits for days: it is probably too big or too vague. Cut it into two or three smaller ones.
- If stones keep appearing out of nowhere: the project is growing. That is not a failure, but it is worth deciding on purpose whether the new pieces belong.
- If you keep skipping to a later stone: your order may be wrong, or the early piece is scarier than you admitted. Name the fear and make a smaller first step.
This is the “adjust” part of the idea. A marker does not only celebrate where you have been; it tells you whether the path you planned is still the one you are on.
Marking milestones as a team
The same approach works for small groups, with one extra habit: keep the markers somewhere everyone can see. It can be a shared sheet or a physical wall. When one person moves a card to “finished”, the others see it, and the shared picture builds itself. A team that understands how change lands with people may enjoy a practical guide to handling cultural change in delivery teams, since agreeing on how to mark progress is partly a matter of group habits.
Whoever keeps the list should also keep it kind: no red marks, no counting of who finished most, just a calm record of what has moved. The list works for the group only while it feels safe to be honest on it.
Keep team meetings short by using the markers as the agenda. Ask three questions: what was finished since last time, what is next, and what is stuck? Anything that cannot be answered by pointing at the list probably needs a new stone.
Celebrate at the right size
Small stones deserve small celebrations. A tick is enough. After every few stones, take a short break, take a walk, or tell someone what you finished. After a bigger stretch, mark it properly with a meal or a quiet evening off. The aim is to match the reward to the size of the achievement so that the habit stays warm without becoming a burden.
The same marker stones in everyday life
Nothing about this method is specific to code. A weekend trip, for example, can be a line of stones: dates chosen, route drawn, vehicle arranged, bags packed. If the vehicle is a bike or car borrowed from a private owner, one website built around that arrangement is MotoShare, which lists bikes and cars that owners in the USA offer for rent to people who search and book them. I bring it up purely because renting a vehicle there unfolds in distinct stages, and each stage can take its own tick.
Common stumbling blocks and gentle fixes
- Stones that are really wishes. “Understand databases” is a wish. “Create a table and read one row back” is a stone.
- Too many stones at once. Show only the next few; keep the rest in a collapsed list so the board does not overwhelm you.
- Ticking things that are only started. A tick means finished. If you tick halfway, the marks stop telling the truth.
- Forgetting to look back. Once a week, glance at the whole path and note what you have covered. It is a reliable remedy for the creeping feeling of going nowhere.
Where the walker ends up
Back on the mountain, the walker reaches the last stone, looks back along the line of markers and realises the climb was a hundred small steps rather than one enormous effort. The same is true of any software project. Start with a sentence about where you want to end up, slice the route into stones that take a day or two each, and mark each one as you pass it. The path will be exactly as long as before, but you will always know where you are on it.









