Forums

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

Reporting on issue decisions

Stu
Contributor
January 28, 2018

I run a PMO for an Innovation group that has about 40-50 projects in flight.  We have only just started using Jira so there is room to re-design my JIra.  We engage customers that may want to co-innovate with us.  One item I would like to achieve is to provide some high-level reporting on the depth of business engagement with all these projects.

In my Jira setup, we use the issue type 'Decision' as I want capture decisions during the project and confirm the level of engagement with the customer for example...

  1. Does the customer have an innovation challenge worth working on?
  2. Does the customer want to co-innovate with us?
  3. Does this customer want to do a design thinking workshop?
  4. Does the customer want to co-innovate with us and build a PoC?

These questions are generally asked in chronological order during the project.

I would like to provide summary reporting for my PMO, it could be done using a board, that shows the level of engagement achieved with all my projects.  My thought would be to report on the decision results for all these decisions per project.


My questions are:

Is the above approach a good one to achieve my overall objective of reporting on business engagement?  Is there a better approach?

I'm not structuring my 'Decision' issues in any special way, should I? any suggestions?

Is there a way to provide a Program board, that would show all the levels of engagement per project (results from my questions) ?

Many thanks for your help :)

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events