When to Archive?

[Luke Abel]

Hi all,

I just wanted to get some thoughts from the community on when you choose to Archive an idea?

We organise our roadmap into quarters, and I like the idea of keeping "relatively" recently complete items open but in the "Done" column.

Can anyone share their experience or thoughts?

[Denis Paul]

Hi @Luke Abel 

we are following a similar approach as you proposed. We move implemented ideas to the "impact check" status. This status is filtered out from the main idea board and shows up on a seperate view. This way we can check back and see if we really hit the expected goals. Build, measure, learn!

[Donat Pohla]

Hi Luke,

We had recently thought about this as well.

We decided, we do not want to turn ideas, that are moving to production into delivery tickets, as atlassian suggests. In our opinion to many insights get lost in the scrum board and we want to keep track on them. 

So we decided that we are going to archive ideas that have been built, so our idea backlog shrinks but the insights are not lost.

Kind regards,

Donat

[Jeanette Bonifaz]

Hi @Donat Pohla 

If you do not create delivery tickets, then how do you track the development work?

[Donat Pohla]

Hi @Jeanette Bonifaz 

When we want to push an idea to delivery, we transform all the insights into a user story map in miro. There we use the Jira integration to create the necessairy issues and from there its the scrumban process, where we track the issues in the sprint.