I work on a team that consists of several different groups - researchers, analysts, database analysts, and developer (me). We load data for our project several times a year, following a consistent (and long) process that involves many handoffs from one group to the next.
We currently use JIRA to track our process development - i.e., improvements, bugs, change requests, etc. - though we don't really use an Agile methodology (since I'm the only developer, I would say we use a 'nothing' methodology, but Waterfall is probably closer than anything).
We would like to begin using JIRA to track our progress through the process itself. So for example, we might have the following steps:
- Pull data from database (DB Analyst)
- Create initial data product (Developer)
- Run analysis (Analyst)
- Check data product (Researcher)
- Check analysis (Researcher)
- Package analysis results for deliver (Developer)
- Upload analysis results to database (DB Analyst)
These happen more or less sequentially, one leading to the next, and typically need the same steps every time period.
My current plan is to create a single task, effectively a Story (though I don't think it's properly a Story, if I understand Stories properly). Then, create Subtasks to that Story/Task for each of the above tasks. I'm not sure if the tasks should start out assigned to their eventual do-ers, or if they should start out assigned to the project owner (we don't really have a PM, but that would be the PM in an ideal setup) and get assigned out when they're ready to be worked. I'm also considering setting them up where each subtask is a "blocker" to the next subtask, though it doesn't look like that's necessarily a good idea based on the UI; it still shows as Open, though at least it has links in the related section to the blocker/blocks tasks.
Is there a 'best practice' way to do this? Is this not really doable in JIRA? It does sound like Kanban might be closer to what we're doing here, but honestly I don't think I could get a major shift like that accomplished in a meaningful way. Is this something I'd need to get a JIRA add-on to make more doable? (I think we use mostly stock Jira, with some custom templates but not a whole lot.)