
A work-in-progress limit is a simple agreement: the team will not have more than a set number of tasks started and unfinished at any moment. That is all it is. No new tool is needed, and no method has to be bought. Yet this small agreement changes how a DevOps engineer experiences the week. This explainer covers what a work-in-progress limit is, how it operates on a board, why it speeds up finished work, and how a learner on the path toward a DevOps role can apply it to their own tasks and study.
The idea in one sentence
You may start something new only when something else has finished. Everything else about the practice follows from that rule. The count of open items has a ceiling; once the ceiling is reached, the team’s attention turns to completing, reviewing, testing or unblocking what is already open.
A concrete picture
Imagine a board with four columns: To Do, In Progress, In Review and Done. A limit of three is placed above In Progress. An engineer finishes the first task and moves it to review. Now there are two in progress, so she can pull another from To Do. But if all three slots are taken and a new request arrives, it waits in To Do. Nobody has to argue about it. The board makes the situation visible.
Many boards also set a limit on the review column. This is useful because review is where work frequently stalls: tasks pile up, authors start more work to fill the time, and the pile grows. A limit on review pushes the team to clear reviews before opening anything new.
Why finishing sooner is the result
Consider a simple analogy. A motorway moves best at a moderate density of cars. Add many more and everything slows, until the road is full and nobody moves quickly. Work behaves similarly. When too many tasks are in motion, each one waits for attention, and the time from start to finish stretches out. Reducing the number in motion lets each item flow through with fewer pauses.
There is a human side as well. Each open task occupies a small part of the mind. Switching among several tasks means recalling where each stood, which takes time and often leads to mistakes. Having fewer tasks open makes the work calmer and the quality more consistent.
What counts as work in progress
Precision helps here. An item is in progress from the moment someone begins it until it meets the team’s definition of done. That definition should include more than writing code or a configuration. It might include review, automated tests, deployment and a confirmation that the change behaves as intended. Items waiting for someone else are still open; they can be marked as blocked, but they should not be forgotten.
- Started and active: someone is working on it right now.
- Blocked: it cannot move until an outside event happens.
- In review: finished by the author, waiting for another person.
- Done: it meets the agreed definition and nothing further is pending.
Choosing the number
There is no universal figure. A common starting point is the number of team members, or slightly fewer. Run with it for a few weeks and watch the signs. If people are often idle, the limit may be too low or there may be a bottleneck elsewhere. If items still wait for long periods, the limit may be too high. The limit is a lever that is meant to be adjusted using what you observe.
How learners can use it
You do not need a team to use the idea. If you are building toward a first role, treat your own tasks as a small board: one course, one lab project and perhaps one piece of reading. Finish each before pulling the next. The career article on progressing from junior to senior DevOps engineer describes how responsibility grows over time, and a habit of finishing is one of the things that makes someone trusted with more. The step-by-step DevOps engineer growth roadmap covering what to learn, build and certify is also easier to follow when you work through it in sequence rather than opening every topic at once.
Misreadings to avoid
It is not a speed target
The limit does not ask anyone to work faster. It asks the team to finish before starting, which usually results in more work reaching users sooner, but the aim is flow, not pressure.
It is not a ban on interruptions
Genuine emergencies still occur. A good policy states what qualifies, allows the limit to be exceeded for those cases, and records each occurrence so the pattern can be reviewed.
It is not only for software
The principle appears in kitchens, offices, hospitals’ administrative desks and homes. People raise it on many kinds of websites. As an incidental example, AskDoctorLive presents itself as a wellness-oriented website that includes a forum and a blog, plus directory pages for hospitals and doctors, which illustrates how widely everyday routines are discussed online. The topic here, though, remains the organisation of engineering work.
Starting tomorrow
- Write down every task you currently have open.
- Agree on a number, and write it above the In Progress column.
- Define done for your team in a short sentence.
- Mark blocked items clearly and name what they are waiting for.
- Review the board weekly and adjust the limit if the evidence points that way.
The strength of the practice lies in how little it demands. A number, a column and the willingness to finish what is open: that is enough to see where work waits, and to start moving it.