Naar de inhoud springen

Draft · not indexed. Part of what this page describes is not generally available yet.

Peak One · Template

A sprint fits the time the team has. Not the time the backlog would like.

The template puts the sprint backlog next to available capacity. In the demo you pull tasks into the sprint and see when it is full.

Status: BetaTemplates exist for boards and workflows; project templates with a timeline are still being built.

Plan a sprint

Sample data · nothing is saved
  • 5 P
  • 3 P
  • 8 P
  • 2 P
  • 5 P

0/13 points

Fits the velocity. Sprints with burndown are beta in Peak One.

Interactive demo with invented sample data. No account, nothing is saved or sent.

How the template is built

  1. Sprint goal

    One sentence on what is different after the sprint. It helps when something new arrives mid-sprint.

  2. Capacity first

    Working days per person minus absences and fixed meetings. Only then do you fill the sprint.

  3. Backlog in order

    The most important task is on top. Pull from the top until capacity is reached.

  4. Estimates

    In hours or points, as long as it is consistent. Split big tasks before the sprint.

  5. Definition of done

    When is a task really finished? Tested, accepted, shipped. The same for everyone.

An example

Two-week sprint at Studio Kiel

Example: Three developers have 48 hours between them because one is off for two days. The top of the backlog adds up to 61 hours. In the demo Ben moves the two lowest tasks to the next sprint.

Example, invented

Honest limits

  • Sprints are beta

    Sprints with burndown exist in Peak One in Board V2, part of Work V2, not yet in the app catalog. Load and absences from Peak Plan are available.

  • As a Peak One project, in beta

    Templates for boards and workflows exist in Peak One as a beta. Project templates with a timeline are still being built, so today you carry part of the structure over by hand.

  • The demo saves nothing

    The template on this page runs in your browser with invented sample data. Nothing is saved and nothing is sent.

Frequently asked questions

How long should a sprint be?

Usually one to two weeks. Shorter makes planning hard, longer delays feedback.

What happens to unfinished tasks?

They go back to the backlog and are prioritised again, not carried over to the next sprint automatically.

Is the template only for software?

No. Marketing and agency teams work in sprints too when they deliver in a fixed rhythm.

Plan with honest capacity.

A sprint that fits the time gets finished. Try where the limit is.

Try the sprint