I do have some questions concerning a feature development organization. This is how we are organizing the work and I would like to have some feedback or recommendations:
With that organization we do have few problems:
For what we see a level of hierarchy is missing here, as a Story should act the same way as an Epic. An Epic contains Stories and each Story contains Task (unit of work). I don't see how this can be handle at JIRA level and even on thew new JIRA Portfolio as I saw we are stopping once again at the story level...
It requires lot of extra work to make sure our story is finished based on all task related done. It's kind of a show stopper.
What would you recommend to handle that properly ? or what do you think we should change ?
In our implementation, which I assume would work similarly for JIRA Cloud, a Story breaks down into Sub-tasks and Sub-tasks are associated with a Story. To JIRA, a Task is at the same level as a Story in the hierachy but doesn't get broken down into anything smaller like a Story does. We ended up not using Tasks at all - we just have Epic > Story > Sub-task.
Hope that helps,
Hi frank. as suggested you should try with subtask (on agile are called technical task) . The main problem that u can find is about that subtask are not visible in scrum plan as single item, but only "story" and similar issue type are showed.
An alternative way is to use link and some script, but this will be a more complicated solution.
Franck, is that a good thing or a bad thing in your eyes? If I understand what you're saying, JIRA should do exactly what you need.
Sub-tasks are always going to be associated with their Story. If the Story isn't done at the end of a sprint, it and all of its Sub-tasks will be moved to the next sprint or the top of the backlog if a next sprint hasn't been created. When the next sprint is started the Sub-tasks for the Story that has carried over will maintain their proper statuses and be in the proper columns on the board.
I don't think JIRA should do exactly what we need, we are just trying to do the best of it and what we think an agile development should be.
I see 3 problems with the sub-task moving from one sprint to another:
We have exact same problem as above. To add more to the Problem, we would not like the Epics and Stories to be closed ever. The Tasks should be at a lower level then stories.
I have not got a proper solution to manage the Requirements (EPIC, Stories) and Tasks (Tasks, Bugs, Enhancements, CRs etc.) together in JIRA and still need to maintain multiple spreadsheets.
Please suggest if some solution to this problem is available.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs