Loading Profile...
Support for multiple iteration backlogs
It would be nice to have multiple backlogs. Often I want to plan out the next few iterations. While obviously iterations aren't set in stone until they begin, it's helpful for other parts of the business to have some idea what might be coming down the pipeline.
I’m happy
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
-
Inappropriate?Tracker does this for you. It figures out how many stories can fit in iterations based on your current calculated velocity. If you want to put harder milestones into your backlog, you can drop in a release marker story and give it a deadline. The idea behind a single backlog is that there is only one timeline in reality. You work on one thing, then you work on the next thing. If you had multiple backlogs, wouldn't you just have to put them in chronological order anyway? Wouldn't that be equivalent to how Tracker handles things now, but harder to manage?1 Comment
Add a comment
This is one of the best points
-
From the developers pint of view this is true. however one of the advantages of agile methodologies is that they can provide increased visibility. We have given access to this tool to people outside our software team. Their needs are to glance at the website and quickly have a sense of what's coming down the pipeline and when.
When 3x5 cards are placed on a wall you can physically space out different iterations so the can see what is happening say this month, and what is currently planned (but not set until the sprint starts) say 2-3 months out. We can put in markers so they can scroll through the backlog but it's not as visually clear.
What I'm recommending is simply a different visual display, on in which the backlog, while still one backlog can be visually divided. The current iteration and icebox are distinct visual panels on the website. I'd recommend the ability to use the markers (or some other means) to divide each set of stories into a new visual panel and provide some additional information (e.g. projected start date, information about the purpose of a release). This would allow people outside development to quickly visually get a sense of what happens when. It would still be one backlog, but their interest is less about scrolling through the backlog and more seeing the big picture and drilling down in an area in which they have interest.
