Work in several projects simultaneously

Question

It is interesting which of you can work on several projects on the same day, devoting only a short time to each of them. Or if you can work at the same time, two or three or more projects at a time. I have so many things that I am starting to wonder how can I do this? I was thinking about using multiple workspaces and switching between them, etc. What other approaches do you use?

Answer 1

Quite a lot of research has been done on task planning. Since this is a Stackoverflow, not a business site, I will compare it with the kernels of the operating system;)

You have several tasks that need to be completed, and the goal, of course, must be effective. Efficiency can be measured as high throughput or low latency.

When switching between tasks there will be a costly penalty called context switching. That is, you will have to switch documents, applications, enter the system, etc., and it will take time to get into the zone.

Given several tasks of different sizes. If you randomly arrange them in a sequence (batch), you will have the least number of context switches and, therefore, the highest overall throughput. If you additionally select them in size, from small to large, you will also reduce the delay. Since the client with the smallest projects will be delivered first, you will have more projects that will be implemented at a certain point in time than in the case of the random approach above. The problem, of course, is what to do with large projects when new smaller ones arrive. This can be solved by applying some timestamp. If some projects are more important than others, you will have to attach them accordingly.

If this still does not give you a satisfactory delay, you will have to multitask. This will reduce throughput due to expensive context switches, but you can satisfy your customers by showing them that you are making progress in your projects. The important part is to choose how to allocate time intervals. Per hour, per day, per week? The shorter the time interval, the more context will switch.

Tasks, in turn, can be divided into two different types: tasks with CPU and I / O. I / O interaction can be considered as tasks requiring input from a device / someone else, while binding to a processor requires only your time / capabilities. Organize your week to get started with I / O tasks sooner rather than later. While you wait for their return, you will focus on tasks related to the CPU.

Summarizing. You break down each project into smaller deliveries that are small enough to meet your customers' progress needs. On Monday morning, you plan your week and start with all tasks that require the actions of someone else (statements, etc.). Send these emails and make these phone calls. When this is done, you will focus on the parts that require your concentration.

Or you could hire more people :)

Answer 2

Just do it.

Perform small tasks; do them, move on. Organize priority.

It is so simple; forget tricks, forget tools and other timers. I find the easiest way the most effective.

Answer 3

You are too finely divided, trying to do too many things and, in the end, you are not making any progress. This may make others disappointed with your apparent lack of progress. It’s more efficient to focus on one thing at a time, but you still want to make progress on several projects. When you shift gears, there is a certain shift time. The most effective way to work with multiple projects is to use existing breaks on your day as transition points.

For example, we pretend that you have three breaks per day: morning, lunch, and noon. This gives 4 blocks of 2 hours each. In each of these blocks, make one project your main focus.

Divide your projects into tasks that are as small as possible. This helps you track progress and also gives you a greater sense of accomplishment. Take notes at the task and project level to help yourself remember what you have done / discovered.

Answer 4

Challange keeps track of where you are in each project, and what more you need to do. I use Windows sticky notes to remind myself of my immediate tasks and to keep a daily journal of what I'm doing, about what I finished, about what I need to decide how it was resolved, etc. That way, I can find back and quickly update where I was on the previous task.

Answer 5

I have been in the same situation for the past few weeks: I already had three of my projects, and recently another developer came out, and I had to take one of his projects. At first it seemed to me that I had not made any progress, because I tried to do too many things at once.

Then I realized that I absolutely must prioritize. I discussed with my boss that the project is the most important and focused on it entirely. I don’t even allow myself to make short corrections for other projects (probably, testers do not like me now), because although it takes only five minutes to fix this error, you lose concentration and do not return it for about half an hour.

I have to say that it really helps - last week I did a much more useful job than two weeks before. Oh, and turn off the damned phone if you are lucky enough to sit next to him. Good luck.

Answer 6

Allow yourself time to work on each project and not get caught up in the details. Sometimes it’s good to write messy code. If it compiles and works as expected, send it. You can come back and reorganize smaller parts later. Keep your customers and your boss in the loop.