Skip to content
Module Library
Production & Pipelines
Task Boards and Sprints

Task Boards and Sprints

PROD-203 10 min

Before this:Scope and the Vertical Slice

Standards (2)
  • 16.7 Collaboration Software
    Contribute to multi-phase projects by managing shared tasks through professional project management software technology, collaboration platforms, shared drives, and version-controlled files.
  • 2.8 Meeting Deadlines
    Coordinate with cross-functional teams to plan, execute, and evaluate projects, ensuring tasks are completed on schedule and deliverables meet expectations.

What you’ll be able to do

  • Write a task so someone else could pick it up without asking questions
  • Estimate how long a task will actually take
  • Understand what a sprint is and why work gets organized into them
  • Read a task list as a temperature check on how a project is actually going
🎥 Video lesson embedding point (captions & transcript available).

Read

Why write tasks down at all

If it’s not written down, it isn’t happening, as far as anyone else on the team can tell. Work you’re quietly doing in your head doesn’t help your teammates plan, and it doesn’t help you either, three weeks from now, when you’re trying to remember what you’d already figured out.

A task list’s whole value is that anyone, including you, can look at it and know the true state of things without having to ask.

Writing a useful task

A task like “fix the level” tells nobody anything. A useful task has:

  • A specific, actionable description. Not “fix the level,” but “fix collision on the north bridge so the player doesn’t fall through.”
  • Who it’s assigned to.
  • What “done” looks like. One line describing the finished state, so there’s no ambiguity about whether it’s actually complete.
  • Status. Not started, in progress, or done.

The test: could someone who wasn’t there when it was written pick it up and know exactly what to do?

Estimating

Nobody estimates perfectly, and that’s fine. What matters is estimating consistently enough to plan around. A useful habit: if a task feels bigger than something you could finish in one sitting, break it into smaller pieces. “Build the level” isn’t an estimate. “Greybox the first room” is something you can actually put a number on.

When something takes longer than you thought, that’s information for next time, not a failure this time.

Sprints

A sprint is a fixed block of time, commonly one to two weeks, where you commit to a specific, limited set of tasks and focus on finishing those before adding anything new. At the end, you check what actually got done against what you planned.

The discipline isn’t really the time limit. It’s naming a small, specific set of work and protecting it from new additions mid-sprint. New ideas don’t disappear, they go on the list for later instead of derailing what you already committed to.

Reading your own list as a signal

A list where almost everything sits at “not started” and nothing moves to “done” is telling you something real: you’re planning faster than you’re finishing. That’s worth noticing on your own list before it becomes a surprise at a review.

Quick Check

⚡ Quick Check

A task reads: "Make the level better." What's the main problem, and how would you fix it?

  • A. It’s not assigned to anyone, that’s the only issue
  • B. It isn’t specific enough to know what “done” looks like or for someone else to pick it up
  • C. Nothing is wrong, general tasks give room for creativity
  • D. It should already be marked done since level work is ongoing
Show answer
B. A vague task can't be estimated and can't be confirmed finished. The fix is a specific description and a one-line definition of what "done" means.

Terms

  • Task
  • Sprint
  • Estimate
  • Status

Next

Project Planning and MilestonesMeetings, Standups, and Notes