Forums

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

Add larger picture detail for Infrastructure/Ops management

Cameron Rake
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!
September 17, 2018

I'm a big picture thinker and Story/Epic terminology and workflow don't fully capture the small to large concepts which are needed to run many teams within a company, all working on various portions of the business goals as well as our operations related projects:

 

For instance I would expect the project flow to be something like this:

SITE: Company: (Healthcare)

1: Business Objective: (Save 15% in annual costs)

2: Functional Area/Department: (IT/OPS)

3: Epic: (Be more efficient - save x$M in 2019)

4: Project1: (Automate PC Builds - save 120hrs a week.)

5: Story1: (Build SCCM environment)

6: Task1: (Create Architecture, Build VMs)

7: Sub-Task: (Document existing network, Free up storage for VMx)

 

While the task flow would be normal agile process (Backlog, In Work, Done).

Is there any way to modify JIRA's Project, Epic, Story, Task, SubTask?  Adding 3 extra functions to the process flow, would really help roll-up our daily efforts and provide connectedness to company objectives, allowing for better reporting to the executive level, all while being able to better align with other Departments needs/goals.

0 answers

Suggest an answer

Log in or Sign up to answer