Best Practice For Non Development Issues in Scrum Project

[Mark Hanfland]

We have several Jira projects which are for Scrum/Agile development. A typical parent issue in our Scrum Jira project would be for a new customer implementation. The customer implementation parent Jira would have many subtasks some of which are for development and some of which are for non development tasks like training.

The non development sub tasks do not fit into sprints and do not work well with the Jira version/release process, time tracking, Greenhopper etc.. so we are considering our alternatives. We discussed splitting the non dev tasks into their own project and then linking the parent jiras. Would like to know if anyone has a strategy for this.

[boardtc]

You may have noticed that when you create a sub tasks there are 2 options you can have a sub tasks or a techincal task, this is one way of doing it.

Another way is to further groom your stories so they become tighter and you have a pure user story and then seperate tasks which have seperate sub tasks. The tasks are not stories as they do not had business value for the end user but the team / product owner have agreed they need to be done.

[John Burns]

In addition to this, we use a different workflow for non-development tasks, one that does not require code commits and review.