Estimation & Velocity

Know when you'll deliver

Assign ticket points or estimated hours to feature tickets, track your team's velocity, and see exactly when work will be done - on the board and the timeline.

Two estimation modes

Choose Ticket Points (0-3) for relative sizing, or Estimated Hours for time-based planning.

Automatic velocity

Todo4you calculates your team's average throughput per week from the last 3 weeks of completed work.

Week projections

The In Progress column shows week separators so you can see which tickets land in which week.

Timeline integration

Gantt bars extend to projected completion weeks and show estimation badges at a glance.

Getting started

Enable estimation in two clicks

Estimation is a per-project setting. Turn it on, pick a mode, and your board is ready.

1

Open project settings

Navigate to your project and click the cog icon in the toolbar, or open Settings from the sidebar.

2

Choose an estimation mode

Under Estimation Mode, select one of the two options:

Ticket Points (0-3) - a simple relative scale. 0 means trivial, 3 means heavy. Great for teams that prefer abstract sizing.

Estimated Hours - enter a decimal number of hours. Better for teams that bill by the hour or want concrete time estimates.

3

Start estimating

An estimation field now appears on every feature ticket - in the ticket modal, the full ticket page, and as a badge on the card itself. Bug and release tickets are not estimated.

Project Settings
Estimation Mode Enable ticket points or estimated hours on feature tickets
Ticket Points (0-3)
What you'll see on ticket cards:
2TP 1TP 3TP 0TP
Or with Estimated Hours:
4h 1.5h 8h 0.5h
Board view

Velocity and week projections on the board

Once your team starts completing estimated tickets, Todo4you automatically calculates velocity and projects when in-progress work will be done.

Velocity badge

A badge at the top of the In Progress column shows the average points (or hours) your team completes per week - calculated from the last 3 weeks of feature tickets moved to Done.

Example: if your team completed 6 TP over the past 3 weeks, your velocity is 2 TP/wk

Week separators

The In Progress column automatically inserts week separators between ticket cards. These show exactly which tickets fit in the current week and which will spill into next week - based on velocity and the estimation on each card.

Tickets are walked top to bottom. When the running total crosses a week's worth of velocity, a separator is inserted.

Estimation badges

Every feature ticket card shows a small badge with its estimation value - 2TP or 4h - so you can see the weight of each ticket at a glance without opening it.

In Progress column
In Progress 2 TP/wk
TODO-5Fix login timeout 1TP
TODO-8Add password reset 1TP
Week 11 (10-03 - 16-03)
TODO-12Dashboard redesign 3TP
Week 12 (17-03 - 23-03)
TODO-14Export to CSV 2TP
Timeline view

Projected completion on the timeline

The timeline page uses the same velocity data to project when in-progress tickets will actually be done - and shows it directly on the gantt chart.

Velocity stats bar

At the top of the timeline, a stats bar shows your team's velocity, the total remaining work (across all non-done feature tickets), and a projected completion date.

If your team has 8 TP remaining at 2 TP/wk, the projection shows "~4 weeks".

Projected gantt bars

In-progress tickets without a deadline normally end at "today" on the timeline. With estimation enabled, their bars extend to the Sunday of the week they're projected to complete - using the same velocity-based algorithm as the board's week separators.

Tickets with a deadline keep their user-set end date.

Estimation in bar labels

Each gantt bar shows the estimation value in its label - for example TODO-5: Fix login [1TP] or TODO-8: Reset flow [4h].

Timeline
Velocity: 2 TP/wk Remaining: 8 TP Projected: ~4 weeks (29-03)
TODO-5: Fix login [1TP]
Done
TODO-8: Password reset [1TP]
Wk 10
TODO-12: Redesign [3TP]
Wk 11
TODO-14: CSV export [2TP]
Wk 12
Under the hood

How velocity is calculated

Velocity updates automatically every time you load the board or timeline. No configuration needed.

1

Look back 3 weeks

Todo4you finds all feature tickets that were moved to Done in the last 3 weeks.

2

Sum up the work

It adds up the ticket points (or estimated hours) of those completed tickets. Bug and release tickets are excluded - only features count toward velocity.

3

Divide by 3

The total is divided by 3 to get the average per week. This smooths out spikes and gives a reliable number.

4

Project the future

Velocity is used to project week boundaries. In the In Progress column, it inserts separators after every "week's worth" of work. On the timeline, it extends gantt bars for in-progress tickets to their projected completion week.

Choosing a mode

Ticket Points vs. Estimated Hours

Ticket Points

Best for: teams that want quick, relative sizing without debating exact hours.

Scale: 0 (trivial), 1 (small), 2 (medium), 3 (heavy).

Badge: 2TP

Velocity unit: TP/wk

Estimated Hours

Best for: teams that bill by the hour or need concrete time estimates for planning.

Scale: any decimal number (0.5, 2, 8, 40 - whatever fits).

Badge: 4h

Velocity unit: h/wk

You can switch between modes at any time in project settings. Existing values are preserved - if you switch from Ticket Points to Estimated Hours, your ticket point values stay on the tickets and you can add hour estimates alongside them.

Start estimating today

Create a free account, enable estimation on your project, and see your team's velocity within a week.

Get started free

Coming soon

Our native apps for iOS, macOS and Android are in development and will be available on the App Store and Google Play soon.