How does project prioritization work?
A reflection on time, resources, and choosing what matters when prioritizing projects.
TL;DR Too lazy to read? Click here.
One of the most baffling problems I’ve seen throughout my programming career is people’s ability to avoid prioritization.
People’s most common approach is to switch to autopilot, or “someone chooses for me and I do it”.
Programmers don’t understand that it’s all too easy to post on Twitter about how awful a project’s management is or how bad the company is. But none of them have ever taken responsibility for a project themselves to then criticize with such conviction. It’s not hard to criticize and point fingers; what’s hard is to execute and deliver results. Personally, I don’t usually listen to someone who has no measurable results to show.
You don’t need to be a SCRUM MASTER or hold a project management certificate to understand the basic concepts of prioritization.
There is a rare, finite commodity that we tend to sell for very little money, and that commodity is our Time. Time, Resources, Money, and People are all finite.
Knowing that these things are finite, you need to choose what to do. Of course, if time were infinite, you could put everything off and your nest egg would still be secure. The first thing we usually do when we choose something to work on is plan: like a story, your project needs a beginning, a middle, and an end.
Prioritization works like this: when you have countless kinds of tasks, large, small, complex, and so on… If you’re not careful, or if you don’t say no, you end up putting those tasks off. This leads to starting the easier, smaller tasks first, and only when the project starts taking shape do you realize it’s too late and the main tasks are still on paper. In other words, you spent your time doing what wasn’t important.
I like an example I saw online in which someone needs to fit two kinds of balls into a jar: lots of small balls and 4 large balls. If the person puts the small balls in first, there won’t be room for the large ones, and the balls end up sticking out of the jar. With prioritization, however, when the large balls go in before the small ones, everything fits inside the container.
Now that’s a good example of project management. Good management means making sure that the 1% of the 1% of errors won’t compromise the entire system, or the whole sprint.
Stopping a sprint midway is one example. Knowing that time is finite, would you rather keep going until the sprint is finished and only fix something in the next one, or cancel immediately and save your time?