Iteration creation

Before the iteration starts

Set up the backlog

Populate the “Proposed iteration” area in the backlog spreadsheet with high-level rows describing work for the upcoming iteration

Move all incomplete epics down from the “Previous iteration” to the “Current iteration” section.

Create epics for every proposed backlog item

Create epics in the appropriate squad’s repo (e.g. canonical-web-and-design/web-squad) and title the epic the same as the title in the backlog. Assign them to the appropriate sprint.

Create and then estimate tasks in the appropriate repo for the work (e.g. canonical-web-and-design/jp.ubuntu.com), once they are broken down, for each epic in the correct sprint. Set their pipeline status to “Next iteration”.

At the start of the iteration

Ensure the points in the previous iteration section are 100% complete. You may now hide the iteration rows.

Pull up the epics that are prioritised from this iteration.

Be sure to check the “sum” cells are set currently.

Hide the content of the completed iteration.

Ensure all rows are correctly broken into issues with estimations.

Check the number of points in the new iteration are achievable, if not, remove or add rows. This will inform the squad how much they take on as small tasks.

Assigning issues to maintenance tasks

Once you have completed your planning and know how many points you can still take on in the iteration, scroll through the Triaged pipeline and choose a number of high, medium and low issues.

A suggested ratio might be 3 high, 2 medium and 1 small.

This allows for a churn of low priority issues to be resolved regularly.

Assign the sprint and the epic

Once you have organised the backlog and you know which epics you are taking on, highlight each epic and move them to the “Iteration epics” pipeline and assign the newly created sprint. You can then show all cards for this epic via the board view. Select each issue and move them to the “Current iteration” pipeline and also assign them to the sprint.

You are now ready to take on your next iteration.


Last updated 5 months ago.