Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Managing multiple Workstreams with different aspects of Dev Ops in Jira

Travis Kvanvig
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2023

I'm brand new to Jira and asked to setup our Enterprise Applications  (Internal IT) department with multiple systems of Enhancements migrating from multiple Smart Sheets to Jira. 


I've not used Jira before, especially not from scratch.  

Looking for Best practices to create a back log for Discovery, Estimating, and Ready for Admin back log (workflow). 

 

And then a back log for all items that are "Ready for Sprint Assignment" that the change manager has their own list of prioritized changes to assign to the next sprint.  

Is this one Kanban board?  Or can I do 2 Kanban boards - one for my team of analysts to track the discovery work being done, and a second one (under the same Jira "Project" of Enterprise Applications Deliver (which is not a project that has an end, it's more of the Jira term for a Project).  

The work stream for Business Analysis, wouldn't operate in sprints, it needs to be a kanban board to track what's in progress, percent complete, and estimated completion date of wrapping up requirements. (Usually for higher visibility initiatives or things that require  'white glove' approaches). 

Thoughts on how to configure these dissparate, yet dependent work streams?  Dependent in that Once the prioritized Discovery is complete, it should move to ready for admin back log for dev.

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events