How to manage several projects at the same time in Algeria (2027): all of them “at 90%” for a month, the same people wanted everywhere, hours discovered at invoicing; load plan, time spent, landing, and what we put in place

“There are eight of us, five on projects, and we run eleven at once. In my spreadsheet, all of them have been at 90% for a month. The same people are wanted everywhere, we promise dates we do not keep, and I find out at invoicing that one project ate close to one and a half times the hours sold. How do you manage several projects at the same time? Is there project management software for a company like ours?” Eleven projects are not steered with eleven spreadsheets: they share the same people. What is needed is one common grid, the time really spent, and a landing calculation redone every week.

Symloop13 min read
Running several projects at the same timeLoad plan per person, time spent, work remaining, landing in hours and in date, marginPROJECT MANAGEMENT · ALGERIA · 2027Running several projectsat the same timeLoad plan per person, time spent, work remaining, landing inhours and in date, marginEVERYTHING IS AT 90%for a monthONE SINGLE GRIDeleven projects, five peoplesymloop.com

Short answer. Managing several projects at the same time takes three things a spreadsheet does not give. One common load plan: each person's hours, week by week, all projects together, because projects compete for the same people. The time really spent, entered every day per project. A landing calculation redone every week: at this pace, how many hours at the end, and on what date. With those three, you know in week 3 what you discover today at invoicing, and you know, before promising, whether one more project fits.

This page is for those who run a design office, an installation company, an agency, an integrator, a workshop that makes to order, any company that sells work by the project, and for those who run one from France. The definitions come from public sources: project management, project portfolio management, earned value, critical path, Gantt chart, milestone, work breakdown, scope creep, timesheet, resource levelling. The company of eight, its eleven projects and its hours are a constructed example. The timesheet is used here for project cost: the page covers neither payroll nor labour rules, and quotes no hardware price.

Why “90% done” means nothing

The figure compares six ways to measure progress.

Figure 1 · Six measures of progress. The first two are those of the usual spreadsheet; the next four rest on facts, or on a question asked again every week.

The 90% rule. An old programmers' saying has it that the first 90% of the code takes the first 90% of the time, and the last 10% takes the other 90%. What holds for code holds for a study or an installation: progress estimated by eye climbs fast, then stops at 90%. Spending is not progressing. Hours consumed say what the project has cost, not what it has produced: a project that has eaten 70% of its hours may be halfway. What can be counted. A task is finished or it is not; a milestone is accepted by the client or it is not. Progress is calculated on those facts.

The remaining work. The useful question is not “where are you?” but “how many hours do you still need?”. Asked again every week, task by task, it gives an end date that moves when reality moves. Two natural slopes. Parkinson's law says work stretches to fill all the time available for finishing it; and “student syndrome” is the name for only really getting down to it at the last moment before the deadline. Short tasks, a week at most, leave less room for either. What this page does not cover. Following a building site, with quantity take-offs and progress claims, is detailed in the construction software page.

«The useful question is not “where are you?” but “how many hours do you still need?”.»
01

What project tracking holds

The figure stacks five layers; the third is the only one shared by every project.

Figure 2 · Five layers. The accented layer is the load plan: it is the only one that runs across all projects, because projects share the same people.

Three constraints. Managing a project means leading a team's work so that its goals are met within given constraints; the main ones are scope, time and budget. The project record carries all three: what was sold, for which date, in how many hours. The breakdown. A work breakdown structure splits a project into smaller components; milestones mark specific points on its timeline. The scope. Scope creep is the name for its continuous or uncontrolled growth, usually once the project has started: an extra request is recorded as such, with its hours, before it is done, not after.

Several projects. Project portfolio management is the centralised management of the processes, methods and tools project managers use. For a company of eight, that comes down to one view: all the projects on one grid, with the same people. Gantt and critical path. A Gantt chart is a bar chart that shows a project schedule. The critical path is the longest chain of activities that depend on one another; it sets the shortest possible duration. Useful on one large project; on eleven small ones, the load plan is what rules. What already exists. The quote comes from the quote-to-invoice chain; the client, from the CRM record.

02

The life of a project, from quote to review

The figure follows a project in six steps.

Figure 3 · Six steps. The accented step is planning: the project is placed on the load plan before the date is confirmed to the client, not after.

The quote. It sets the hours sold, the promised date and the invoicing milestones: those are the three figures everything else will be compared with. Kick-off. The scope is written, the team named, the tasks created. Planning. It is the accented step: before the date is confirmed to the client, the project is placed on the load plan. If the people planned are already at 130% in those weeks, the date is wrong before work has begun. Execution. Every day, each person notes their time per project and closes their tasks.

Time spent. A timesheet records the time a person gives to each job; it is used more and more for costing, estimating and tracking projects, and one of its main uses is comparing planned with actual. Under a minute. An entry that takes five minutes will not be made: three or four projects offered, a duration, one gesture, on the phone, including without a network at a client's site, see the offline application. Milestones. An accepted milestone triggers the planned invoice; the due dates feed the cash plan. The review. Hours sold, hours spent, and what to remember for the next quote of the same kind.

03

Eleven projects, five people: the load plan

The figure lays out five people's hours over six weeks, all projects together.

Figure 4 · Five people’s hours over six weeks, all projects together: the team at 168 h for 160 in week 4, one person at 52 h for 32. Constructed example.

What the grid shows. In week 4, the team has 168 h of work for 160 h of capacity: nothing alarming. But one person has 52 for 32, because three study deliverables fall in the same week, while another, with the same skill, has 24. None of the eleven project spreadsheets showed it: each one, taken alone, was reasonable. Capacity. In the example, 32 project hours a week are counted for 40 hours present: the rest goes to meetings, quotes, calls. Planning at 40 h means being late from Sunday.

Levelling. Resource levelling is a technique in which start and finish dates are adjusted to the limits of resources; in practice it is mostly about resolving conflicts and over-allocations in the plan. Here, two levers: give one study to the person who is free, or move one deliverable by two weeks. Doing less at once. Working on several tasks at once wastes time at every switch of context and makes people more prone to errors; hence the idea, in the Kanban method, of limiting work in progress. In the example: two active projects per person rather than five. Accepting a project. The twelfth is placed on the grid before the promise: it says which date can be kept. The day-to-day rota belongs to team scheduling.

«None of the eleven spreadsheets showed it: each one, taken alone, was reasonable.»
04

The landing: what the project will have cost at the end

The figure reads a 400 h project in week 6, then extends it at the same pace.

Figure 5 · A project sold for 400 h, read in week 6: 200 h earned for 290 consumed, landing at 580 h in week 12. Fictitious hours.

Earned value. It is a project management technique that measures performance and progress objectively. Three quantities: the work planned by this date; the work earned, that is each task's progress multiplied by its planned value; the actual cost. In the example, in week 6: 240 h planned, 200 h earned, 290 h consumed. The ratio. The cost performance index is the ratio of earned work to actual cost: 200 ÷ 290, that is 0.69. Each hour spent produces 0.69 hour of what was sold.

The landing. The budget divided by that index gives the estimate at completion: 400 ÷ 0.69, that is 580 h for 400 sold. And at 33 h earned a week, the end falls in week 12, not week 10. Early. The same calculation, in week 3, gave 105 h earned for 140 consumed: the gap could be read seven weeks before the promised date. What to do at 580 h? Reduce the scope, renegotiate, or accept the loss knowingly. Adding people is rarely the answer: Brooks's law, written for software, says that adding people to a late project makes it later still. The margin. Hours spent and purchases give the margin per project, to be tied to the company's profitability.

05

Six weeks, in the example

Six weeks to go from the spreadsheet to shared tracking, one of them a survey.

  • What management receives: a load grid per person and per week, all projects together; time spent per project and per task; a landing in hours and in date for each project; the milestones to invoice; margin per project; a weekly review held on the screen.
  • What the team no longer does: update eleven spreadsheets, announce “90%” for a month, promise a date without looking at the load, discover an overrun at invoicing, ask the same person for three deliverables in the same week.
  • What is measured: load per person against capacity; hours consumed against hours sold; earned work; landing in hours and in date; active projects per person; milestones delivered on the date; margin per project.
  • What Symloop does: the survey with you, project records and tasks, the load plan, time entry on the phone, the landing calculation, milestones and their invoicing, the client area, then the first Sunday review with you.
Figure 6 · Six weeks in the example, survey included. The accented period is the first: reading the spreadsheet and the projects as they are. The last milestone is the first weekly review held on the screen. Indicative durations of a constructed example.

The survey. One week with you: the projects under way, the current spreadsheet, who does what, how you invoice. Taking over what exists. Projects under way are taken over with their hours sold and an honest estimate of the remaining work; the past is not reconstructed. Time entry. It starts early, on the phone, with a reminder at the end of the day. The Sunday review. The last milestone: the first weekly meeting held on the screen, project by project, starting with those whose landing overruns.

What the client sees. A client area can show progress, milestones and documents, without a call or an email. What management sees. Projects overrunning, the load of the coming weeks and the milestones to invoice go up into the dashboard. Off the shelf or custom. Project management software exists, and much of it is very good at tasks. It fits when your way of selling falls within its frame. Custom work is justified when quotes, time, milestone invoicing and margin have to be tied together, or when the work is done on site, without a network. The durations are those of a constructed example.

How do you manage several projects at the same time?
By placing them on one grid: each person's hours, week by week, all projects together. Projects share the same people; that is where delays are born, not inside each project taken alone.
How do you manage a project in a company?
Three figures at the start, hours sold, promised date, milestones; short tasks; time entered every day; and every week, the remaining work and the landing. The rest is a matter of regularity.
Is there project management software suited to a small company?
Yes, there is plenty, often very good at tasks. Check two things: does it show the load per person across all projects, and does it tie time spent to hours sold? If not, it is a task list.
How do you calculate time spent on a project?
By a daily entry, per project and per task, that takes under a minute on the phone. Reconstructed at the end of the month, time is wrong: people remember the big projects, not the interruptions.
How do you know whether a project is late?
By comparing the work earned with the work planned by this date, and recalculating the end date at the current pace. A percentage estimated by eye does not say it: it stays at 90%.
Is a project tracking spreadsheet in Excel enough?
For one or two projects, yes. As soon as several projects share the same people, the spreadsheet no longer shows the common load, and it is only up to date on the day someone fills it in.
How do you avoid one person being on every project?
By seeing their load before assigning: the load plan shows the weeks in which they exceed their capacity. Then two levers: give the work to someone else, or move a deadline. And limit the number of active projects per person.
Can we accept a new project?
The grid answers: you place the project on the planned weeks and look at who goes over. The date that can be kept is the one where the load fits, not the one the client asks for.
How do you know a project's margin?
Hours spent valued at their cost, plus purchases, compared with the price sold. Followed along the way with the landing, it is known before the end, while there is still time to act.
How long does it take to set up project tracking?
Six weeks in this page's example, survey included, up to a first weekly review held on the screen. Projects under way are taken over with their remaining work.
Tell us how many projects you run, with how many people, and how you follow them today: we start with a week of survey

Projects all “at 90%”, the same people wanted everywhere, dates promised without looking at the load, overruns discovered at invoicing, or a company in Algeria that you run from France

Symloop builds the tracking that ties your projects together: load plan, time spent, landing, milestones and margin. Describe your business to us, your team, and the project whose end date you cannot give today.