Looking for Jira Project Intake/Epic Workflow Examples and/or Best Practices :)

JA
Contributor
August 2, 2023

Hello,

Looking for best practices, examples, or ideas from other organizations on ways to keep a project intake process and Epic (project) workflow simple and effective. I'll put our process below for context. 

Currently our project intake process is this:

  1. End user submits project proposal via Service Desk
  2. Leadership team reviews and updates status
  3. If project is internal to our department, proposal is moved to an Epic in the appropriate Jira Software project
  4. If project is being requested by someone outside our department, a new Epic is created and then linked back to the Service Desk ticket (project proposal). This is done because only our department has access currently to Jira Software projects so we keep the Service Desk ticket open so that we can communicate back to the end user. 

Once we have an Epic assigned, we may put it in any of the statuses and may or may not work on it immediately. Sometimes they sit in "backlog" status for years. 

I'm wondering how other organizations do this. Would it make sense to keep the project proposals in a queue in Service Desk until the future project lead/Assignee actually has capacity to work the project? And if so, what would the workflow look like at that point? 

I realize this is a lot and it's clear as mud, but looking for any advice/examples for a good/best practice workflow, for both the intake process and Epic workflow. I'll add screenshots for both of ours if that helps it make sense at all. 

Thank you in advance to anyone who can contribute ideas!

Justine

Epic Workflow.jpgProject Proposal Workflow.jpg

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events