Rapid Board Story Card with Sub-Tasks across sprints

[Gavin Bunney]

The way we have our story cards setup in Jira/Greenhopper is to have a Story Card, with 3 sub-tasks: one for UX, one for Dev and one for Test. This allows us to estimate at the sub-task level, but wrap them up together at the feature/story card level.

As part of this breakdown, our UX story cards are worked on 1 sprint prior to the development and test sprints.

Is it possible to use the Rapid board, to put these UX sub-tasks in say Sprint 5, but have the Dev/Test and Story Card in Sprint 6?

[sclowes · Accepted solution]

This is possible but you'd need to be a bit careful. The parent story would need to be included in each sprint as well.

The most obvious way is to have two boards, one for the UX sprints and one for the rest. The UX board would have a filter like "project = x and (issuetype != sub-task or component = UX)" while the main board will include everything ("projext = x"). The UX board would only ever see stories and UX subtasks. You could drag stories in to sprints on the UX board and complete the UX subtasks (but not complete the stories because there would be other incomplete sub tasks). There's no easy way to filter to just stories that have UX subtasks though.

In the GreenHopper team achieve the pre-work necessary for UX by workflow. Items that need UX go from Open to Design Backlog status. This status is mapped to a UX rapid board which can be Kanban or have full Sprints executed. The last column of this board is a status of Design Complete. The design complete status is then mapped back to the first column in the main board so that the stories can be picked up again when the sprint begins.

Thanks,
Shaun

[Gavin Bunney]

Thanks Shaun,

We also have status' on the main story card to move it from Pending -> Analysis -> Awaiting Dev -> etc. Looks like two boards is the way to go!

Cheers,

Gavin