Add a document to outline the steps to create an iteration

[anthonydillon]

I thought I would create a brief document which outlines to steps to create a new iteration.

[nottrobin]

I got confused and thought this was an issue, so I wrote my view of what the steps are. Then I realised this is a PR =)

Anyway, here are the steps as I saw them, are all these covered?

Before the iteration starts

• Create a new milestone in GitHub
• Create a "small tasks" epic
• Populate the "Proposed iteration" area in the backlog spreadsheet with high-level rows describing work for the upcoming iteration
• Create epics for every row
  • Assign them to the appropriate milestone
  • Set their "Pipeline" to "Iteration epics"
• Create and estimate tasks for each epic
  • Assign them to the appropriate milestone
  • Set their "Pipeline" to "Triaged"

At the start of the iteration

• Add a new section to the backlog spreadsheet for the new iteration
• Move everything from "Proposed iteration" to the new iteration section
• Move any uncompleted rows from the old iteration down to the new iteration, if relevant
• Hide the content of the completed iteration
• Check the number of points in the new iteration are achievable, if not, remove or add rows
• Ensure all rows are correctly broken into issues with estimations
• Start work!

[anthonydillon]

@nottrobin thanks, updated the document. Incorporating your versions parts I had missed.

[deadlight]

:+1: All good

[anthonydillon]

@barrymcgee applied all your suggestions. Thanks.

[anthonydillon]

@nottrobin could you have another review.

[deadlight]

I like the updates. Even more approved by me :+1:

[b-m-f]

So, all of this has a pre-setup Spreadsheet as a requirement, right? Could we put a link to (myb RAW github) an empty sheet? Just to have a complete picture of how we do this?

[barrymcgee]

Don't forget to 'Squash and merge' or the git log will be polluted with many duplicated commit messages. 👌🏻

[anthonydillon]

Thanks @b-m-f good idea but will take time to set up. I will follow up with something soon.

[nottrobin]

I didn't get to this in time, but it would be unfair of me to hit @barrymcgee with this - https://github.com/canonical-webteam/practices/pull/165#issuecomment-460544247 - and not mention anything here.

I do think, going forward, it would be nice if guides like this were kept somewhere outside practices. I don't think guides are really "practices". The fact that we have 2 week iterations, that we use ZenHub, even how we name our iterations - they are practices. But a guide on how to create an iteration isn't.

I do think a wiki of some sort would be ideal. I've suggested this repo's wiki, but I'm open to other suggestions.

Anyway, I don't think we need to remove this right now, I just think it's worth thinking about for next time.