Where to store the product backlog and the release plan

Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn

In my present team we have tried many formats for the product backlog and the best one so far is – PowerPoint!

We started out with Excel. Excel documents are nice because they are easy to distribute and almost everybody has the ability to read and edit them. You can sort the backlog by rearranging lines with cut and paste, but it’s a bit complicated. If you’re not careful you may lose lines/stories. Another drawback is that the the product backlog easily becomes really large. A 200 lines Excel document is a small one, but a product backlog with 200 user stories is huge, especially considering that we do about 15 stories per sprint.

Next we tried out Trac. Trac is a ticket system much like Jira. We liked the idea of having the product backlog in the ticket system where user stories/tickets never get lost, are versioned, accessible via a web interface and can have attachments.

Unfortunately it’s a pain to prioritize in a ticket system if you want an absolute priority order and not just categories like High, Medium, Low etc. You have to add a numeric filed with a priority number and sort the list according to that. Sooner or later you will end up having to manually renumber several stories just to be able to squeeze in some new stories between existing ones.

By now you probably understand that rearranging and prioritizing the product backlog is really important in our team. Our stake holders work very close to the market changing the priorities of upcoming user stories as market windows open and close.

It was with some excitement we tried out ScrumWorks. In ScrumWorks you can rearrange the product backlog using drag and drop. There is a fat client and a web interface and it doesn’t cost any money to get started. We tried the basic and the pro versions. However, there was no success for us. Perhaps it was the need for a fat client to be installed (and in this organization people usually are not permitted to install software on their own machines) or that people needed to learn a new application (Excel and Trac were already known and in use). As it turned out nobody used the application, for whatever reason.

So far, none of the applications we tried out had a natural limit for the number of user stories you pour into the product backlog, which in all cases lead to a very large backlog. That’s a bad thing since it’s only waste to have items in the backlog that won’t be implemented for the next two years, especially in a fast moving business. Unfortunately we didn’t quite have the discipline to keep the backlog small, so we needed something that would help us in this area as well.

Finally, our business analyst Magnus Almkvist came up with the idea to use PowerPoint – one slide per user story. At first it sounded strange, but it actually works really well.

A PowerPoint slide reminds a lot of the original index card that you read an learn about on all Scrum and PO courses. Whatever you write has to fit on a limited space and it’s easy to rearrange the order in the backlog in the slide sorter view in PowerPoint using drag & drop. Color is used to mark user stories that belong to the same epic/theme and different layouts (backdrop/font color) are used to indicate the readiness of a user story (approved, implemented).

The printouts (6 slides per page) are posted on a wall in the corridor where everybody that works with our team can see them. The wall is updated at least once per week, but the original PowerPoint file is stored in Subversion on the intranet and is available for reading to anyone who want the electronic version. We also have a link from our wiki to make the backlog really easy to find.

In our backlog grooming sessions (once or twice per week) where out PO team meets with the stake holders to prioritize, add to and remove from the product backlog, the printouts are put on a big conference table (no chairs). The user stores are arranged in the order all can agree on and as things are moved around, removed or added scissors are used and new stories are written on pieces of paper. This hands-on way of working is greatly appreciated.

At the end of the session, the original PowerPoint file is updated to document what’s on the conference table.

A PowerPoint file with 200 slides is huge, so there is a natural desire to keep the number of slides/stories to reasonable number. Also, the wall where the stories are posted and the conference table used in the grooming sessions make natural boundaries for the size of the backlog.

The release planning is illustrated in the product backlog by inserting head line slides with titles like ”Sprint 23”, ”Sprint 24” etc. The slides following ”Sprint 23” contain the user stories planned for that sprint, until the next head line slide. Normally we plan three sprints ahead and after that we have a head line slide ”Bad hair day” (referring to the fact that the last part of the backlog in not groomed very well).

On our wall where we post the user stories, each forthcoming sprint is represented by a column of user stories. This makes it very easy to see when a particular user story is planned to be released.

What about attachments and additional documents?

Well, you can paste almost anything into a PowerPoint slide – and we do. Sure it turns out really tiny because we have a limited space for additional info), but in MS Office all information from the original document is preserved when you paste into another document, so usually you can see all the details by double clicking on the pasted item and zooming.

So far, this scheme with PowerPoint has worked really well for us. It’s a nice mix of working with physical items (the wall and the conference table) and being able to share with people in other locations (wiki link to Subversion) and finally we have one indisputable original with versioning thanks to the version control system.

We haven’t let go of Trac completely though. We don’t use Trac for the product backlog, but for the sprint backlog. When the sprint starts each user story in the sprint becomes a ticket in Trac. We like the traceability we get when we check in code in Subversion with reference to a Trac ticket. We can see exactly what code changes each user story caused. And of course we use Track for bug reports and team wiki as well.

8 Comments

  • 1
    2011-05-31 - 09:09 | Permalink

    Excellent post! And the conclusion on PowerPoint was a surprise.

  • 2
    Matthias Lübken
    2011-06-01 - 09:49 | Permalink

    Nice Idea. Have you experimented with Google Docs? Are there any particular features you were missing?

  • 3
    2011-06-02 - 12:45 | Permalink

    At this particular client GoogleDocs was not an option (company policy), but I see no reason why you wouldn’t be able to do the same thing with Presentation.

    Internally at Crisp we use Google Drawings as distributed Kanban boards and that works really nice when the team is distributed (most of us are at clients all day).

    However, if possible, nothing beats working with physical artifacts like user story cards (printed slides) and sticky notes (on Kanban/Scrum boards) in my opinion.

  • 4
    Pascal
    2011-06-01 - 02:08 | Permalink

    Very interesting concept. I’ll will check it out.

  • 5
    2011-06-07 - 04:30 | Permalink

    Where do you keep the details of the story i.e the scenarios?
    In the Wiki? Executable specs in source control? Concordion?

  • 6
    2011-06-07 - 11:56 | Permalink

    Documents describing work flows, GUIs and other details are actually pasted as miniatures into the PowerPoint slide describing the user story. A document pasted into a slide can be expanded by clicking on it. We can also just paste a link to our document archive if the additional info is stored there.

    These “attached” documents are printed in full size for the sprint planning.

  • 7
    Jamie Morgan
    2014-07-11 - 21:04 | Permalink

    Can you post a sample Powerpoint?

    • 8
      2014-11-04 - 01:50 | Permalink

      Sorry, it was a long time ago and I don’t have any samples left, but each slide was essentially a traditional story card with room for an estimate and additional documentation.

  • Leave a Reply

    Your email address will not be published. Required fields are marked *