Development sprint

A sprint works when the whole team shares one picture of the real status: what is claimed, what is being built, what is waiting for review and what is already closed. Without that board, two people start the same task, something goes unreviewed, and the daily standup wastes time just working out who is where.

This board is the classic agile flow, four clean columns ready to fill with the sprint's work. It does not impose a methodology, it gives the minimum structure so status is visible without asking. It suits a small team running one or two-week sprints and a developer who wants to organize their own cycle.

Classic agile flow

Each task enters To do and moves right as it gets built, reviewed and closed. These are the columns and their sample tasks.

To do

The work committed for the sprint that has not started yet. The sample cards show how to prep a task before picking it up.

• Sample task: define the scope of what needs doing
• Estimate the effort before starting

In progress

What someone is building right now. It is best if each person keeps few cards here at a time.

• Build the feature

In review

The code is written and waiting for someone else to review it before it is called good.

• Review the code

Done

Finished and deployed, ready to close the sprint with it.

• Deploy and close

How it works in Foco

On import, Foco creates the "Sprint" job as a Kanban board with these four columns. Each task is a card you drag from To do to Done as it progresses: on desktop with drag and drop, and on mobile by switching between each column's tabs.

Assign each card to whoever is building it, and if you run several projects in parallel, Panorama shows tasks from all your jobs at once, each in its job's color, so you do not lose the thread of the sprint among everything else.