Project Management for Devs: The 5 Things That Actually Matter

Most project management advice is written for managers. Here’s the version for people who ship code.

1. Define “done” before you start
   Half of all scope creep comes from nobody agreeing on what finished looks like. Write one sentence: “This is done when ___.” Put it at the top of the ticket.

2. Break work into pieces you can finish in a day
   If a task takes a week, you won’t know it’s off track until Thursday. If it takes a day, you’ll know by tomorrow. Small tasks make progress visible and problems cheap.

3. Timebox the unknowns
   Don’t estimate research, spikes, or “figuring it out.” Give them a fixed budget (two hours, one afternoon) and decide at the end whether to keep going. The goal is information, not completion.

4. Communicate slips early, not at the deadline
   Nobody is upset by “this will take two more days” on Tuesday. Everyone is upset by it on Friday. The moment you suspect a delay, say so.

5. Keep one source of truth
   One board. One place for status. If someone has to ask you where things stand, the system has already failed.