The reason themes don't work for us is that we want to be able to order stories independently from themes, but we would still want to be able to associate them to a a common label. Adding on that would be features to filter the backlog view based on labels. PivotalTracker has something similar implemented if you want to see a reference.

It does print a double number of pages, however the order of stories (left to right, top to bottom) is different on the "story" sheet and the "acceptance criteria" sheet. This makes it quite hard to cut and staple together, since the matching acceptance criteria page is not "under" the matching user story page.

I haven't succeeded in reproducing it, I will update this ticket if it appears again.

I haven't succeeded in reproducing it, I will update this ticket if it appears again.

Just wanted to add that giving a "read-only" view of the backlog is quickly becoming a top request of our scrum team members, since the teams want to get an idea of what the backlog actually is, even if only the PO and SM actually use the product.

Michael.

Actually, it seems to work fine now since the gray box appears right under the dragged story. The one thing I would fix is to make the focus of where the gray box based on where is the mouse pointer, and not necessary the middle of the story div.

Michael.

I t hink that drag and drop is very intuitive. Some of our users were confused when they tried to organize the backlog. It does seem faster then the "move dialog". In our case, the product owner was wanting to combine themes together so he would just order the themes next to each other and drag from one to the other.

Another usage is to split big themes into smaller themes. With drag and drop it is very intiuitive. For us it would feel a bit clunky to go through a dialog.