Does anyone have recommendation on creating a new Jira issue type to support a professional services SOW estimation activity?
Currently we use an EPIC to represent a large chunk of work billable to a client. We are now considering a shift to use EPIC type to represent a portion of the work order and would like to be able to group multiple EPICs together so we can clearly see which are associated with the same work order. From a backlog grooming standpoint, having multiple EPICs in flight simultaneously may be cumbersome to manage/track.
Soliciting any feedback to help put us on a track for success managing multiple client initiatives using one Jira project.
Decisions
- We use one Jira Project to manage all work for a client
- We have two stream of working being introduced to each client project 1) production support issues 2) planned work
- We use Epic to represent a single billable effort.
- we use stories associated with each EPIC to represent portions of the overall deliverable.
Opportunities
- we are not using components
- we are not using releases; are considering using this going forward to reflect a single billable effort to support more autonomous reporting on work order progress and resource allocation/time spent vs estimated.
- We have considered using custom field for issue(s) to tie multiple issues together.
