Time management
Most students don't fail projects because they lack the hours — a semester has plenty of hours in it. They fail (or just suffer more than they need to) because the hours they do have get eaten by low-value tasks while the important ones get pushed to "later," right up until later stops existing.
Why is this important?
Poor time management doesn't just cause late submissions. It quietly degrades the quality of everything: rushed requirements get skipped over, testing gets cut because there's "no time left," and teammates end up resentful because the workload wasn't visible enough for anyone to notice it was unbalanced until it was too late to fix. Almost every resource elsewhere in this category — breaking projects down, dividing work, running effective meetings — depends on time actually being managed deliberately rather than just hoped for.
Prioritise: urgent vs. important
The Eisenhower Matrix is a simple, durable way to sort your task list. Split tasks along two axes — urgent vs. not urgent, important vs. not important:
- Urgent and important — do these now. A bug blocking a teammate, a deadline tomorrow.
- Important, not urgent — schedule these deliberately. This is where most of the actual valuable work lives — requirement analysis, design, writing tests — and it's exactly the category that gets silently skipped when you're only ever reacting to what's urgent.
- Urgent, not important — delegate if you can, or handle quickly and move on. A lot of messages and small admin tasks live here.
- Neither urgent nor important — the honest answer is usually to drop these entirely.
The uncomfortable truth this matrix exposes: teams that only ever work on what's urgent are, by definition, never spending time on the important-but-not-urgent work until it becomes urgent too — usually at the worst possible moment.
Time blocking
Rather than keeping a to-do list and hoping the day sorts itself out, assign specific blocks of your calendar to specific tasks: "Tuesday 2–4pm: enrolment API." This does two useful things. It forces you to actually estimate how long something will take (a skill most students are bad at until they practise it), and it protects that time from being silently swallowed by whatever feels most urgent in the moment.
Working in focused sessions
Long, unstructured stretches of "study time" are easy to plan and hard to actually use well. A more reliable approach is working in short, focused bursts with real breaks in between — the Overcoming Procrastination resource covers this in more depth, including the Pomodoro Technique, which is one of the simplest and best-studied versions of this idea.
Tips
- Estimate, then track how long tasks actually took. Most people underestimate consistently; a few weeks of tracking will make your future estimates much more honest.
- Protect "important, not urgent" work by scheduling it before your week fills up with meetings and urgent requests, not after.
- Build in buffer time before deadlines, not right up to them. Something will go wrong — a bug, an illness, a merge conflict — and a buffer is the difference between that being a minor annoyance and a crisis.
- Review your week briefly at the end of it: what actually got done, what didn't, and why. This short habit improves your estimates and priorities far more than any planning app on its own.