Rank option only effects Global Rank and not Business Rank

[Marcel Plomp]

To collect issues from users in the business we set up a project with Agile boards. These boards are ordered by the field "Business Rank", (ASC) so it is possible for the Business Process Managers to order the issues according to the "business value".

At the same time these issues show up on a development board which is using the Global Rank field for ordering.

Users from the business do not have access to that development board as it also contains specific technical issues in another "development project".

So basically Project A is only on board A for the business, Board B for development has issues from projaect A and B.

If now a BPM uses the menu options "Rank to top" or "Rank to bottom" this only has an effect on the Global Rank and not the Business Rank.

How can this be prrevented from happening?

[Alexander Bondarev]

Hi, @Marcel Plomp (inactive) !

If we talk strictly about technical implementation in Jira - everything is logical, if on the business board you prioritize one attribute ("Business Rank"), and the development team prioritizes according to another attribute ("Global Rank"), then changes on the business side will not affect the priority for the development team in any way.

In fact, this is not a question of Jira, you should "configure" your internal development processes, planning and grooming of backlogs.

In our company, we have spent a lot of time and energy in order to develop our own model for prioritizing IT tasks based on the "priority" and "severity" of the task.
That is, to determine the "priority", the business customer fills in 2 additional attributes, for the "severity" it fills in 3 additional attributes. It is important that they are ONE(global) for each business customer, because we work in one company and bring benefits again to one company!

Further, on general grooming, tasks are selected based on a combination of "priority" and "severity" (we have a numerical value from 1 to 10).

And after that, the development team creates task IN THEIR PROJECT (a business task lives in a separate business project and moves in its own process), which it prioritizes and plans, for example, in sprints (agile teams) or releases (teams working on releases).

Good luck! It is really interesting theme!

[Marcel Plomp]

Hi @Alexander Bondarev ,

Thank you for your answer.....and I totally agree on your observation that we should "configure" the internal development process. We are working on that and prioritization by the business is part simply of it as well.

Currently we are stuck with an "old setup" so we first focussed on improving the existing "development proces" (workflow in JIRA) for the development teams. This is now finalized.
Next step will be the integration of the "Business proces" and related issues.

It might that we end up with different settings for the Business projects and Development projects.
(A few years ago we only had 1 big project to which everyone had access.... which was not not a succes obviously  (lol)  )

I thought about having customers to fill in "priority" and "severity" too, in order to define the importance for the business.. How did you facilitate this? Using calculated fields with the JSU add-on perhaps?

Regards,

Marcel.

[Alexander Bondarev]

It looks like our way))) 

Glad to hear it! 

We have about 45 business-team and 75 it-teams. Our task were:

- create and document new process

- create simple and clear workflow to business

- update all it-team's workflows - try to take into account the peculiarities of each it-team and put them on the "common processes"

- create single prioritization model

- teach everyone (the hardest one)

Yes, we create 5 extra fields(like I told in the first message), then using SIL-scripts(Power Scripts - Jira Workflow Automation) calculate "priority" and "severity" values, and then calculate the "order of the execution".

If you already have JSU - it's ok, the similar one app(the same idea with different "language" and realization). 

[Marcel Plomp]

Sounds like a plan.....which is already executed for at least 65% in our company.

• Simplified business workflow ? Done !
• Create and document new process? Done ! (Both for business and IT Development teams)
• Update all Team Workflows? Work in progress.... Difficult but doable.
  • We developed a standard. Some teams will adapt that.
  • Others have minor differentiations within the standard or do only need a sub-set....but manage to stay within the General Development Framework.
• Create single Prioritization model? That is what this is all about. Just started....
• Teach everyone? Hard to do.... I agree. But in the end we will get there. Baby steps, baby steps..... 

I will see what JSU can do for us..

Thanks for the input.