Here's a rhetorical question: Do you want to get more done? The answer is yes, of course. We're all racing to embrace digital, and digital capabilities are the only hope for many companies' survival. To maximize output, you need to do fewer things at a time. Embrace this mantra:
Stop Starting and Start Finishing
Don't confuse activity with delivery. It's a mistake to kick off the next project before you've completed any of the items already in the hopper. Get something done before you move on.
I recommend setting a work in process (WIP) limit for your project portfolio. Count how many projects you have in flight, and set the new limit 10–20 percent below that. For example, if you have 17 projects underway, set your WIP limit at 14 or 15. If you have 100 in-flight projects, then dropping all the way down to 80 may make sense. Use your best judgment here—as long as you end up with fewer in-flight projects, you're going to increase your throughput.
Don't start a new project until you fall below your WIP limit. When a project completes, assign the newly available resources to the highest-ranked project possible. Putting more resources on your top-ranked projects will reduce their duration and get you to value sooner. Starting a new project does the opposite; it moves resources to your lowest-ranked and, therefore, least-important project.
The principle of establishing a WIP limit comes from Lean, and the Agile community has adopted it. If you want to explore these concepts more deeply, read up on Lean13, Little's Law35, and Kanban36.
Of course, simply limiting the number of projects you're working on doesn't help a lot unless you know how to prioritize them. The next chapter examines a technique for doing precisely that.
https://kanbantool.com/kanban-guide/kanban-history.