Explicit Priority for Work Items | Targetprocess - Enterprise Agility Solution

Explicit Priority for Work Items

Solution Overview The solution is designed to visualize the priority of items in a backlog via integer numbers explicitly so that Product Owners, Solution Owners, and Key Stakeholders can easily define the priorities of items in a backlog and other people in

Trusted by Agile teams at show more

Solution Overview

The solution is designed to visualize the priority of items in a backlog via integer numbers explicitly so that Product OwnersSolution Owners, and Key Stakeholders can easily define the priorities of items in a backlog and other people in the organization can understand the priority of each item by just looking at the number.

It enables the Priority Number field for each item (by default for Portfolio Epic and Epic), where you'll see the explicit priority of an item in a backlog. The higher the priority, the lower the number. 

The Priority Number can also affect the entity Rank, when it's changed. See the solution configuration section for the details.

Solution configured to update the Rank

It allows to either set Priority Number manually (which will update an entity Rank and put a Work Item to the appropriate position in a backlog):

... or prioritise the items in a backlog by drag and drop (which will update the Priority Number of a Work Item).

Solution configured NOT to update the Rank

During the initial setup it'll set the Priority Numbers for items based on the RankNow whenever you update the Priority Number for an item, it'll shift the Priority Numbers of other items in a backlog based on their Priority Numbers. The Rank of the items won't be updated.

Prioritisation can be made either within a Portfolio, within all Portfolios or in a specific category (values in a drop-down list custom field) as well as allows to exclude items from prioritization if a specific value is selected in a custom field. For example, suppose you have a Reporter custom field with values Internal and External, and would like to set priority numbers for each value separately, or just update priority for one of the values in the field to reduce the number of items being prioritised. In that case, you can configure the rules to use that field values.

Solution Configuration

Add/Change the Entity type

By default, the solution sets Priority Number values for Portfolio Epics and Epics. If you'd like to use it for another entity type (for example, Feature), do the following:

  • Go to Settings -> Custom Fields
  • Add a new Priority Number non-system custom field of type Number
  • Go to Settings -> Automation Rules
  • Open the following rules one by one:
    • PNC_1_of_7_Priority Solution Pre-Setup
    • PNC_2_of_7_Update Priority Number when Entity State, Rank, Project or Group By Custom Field is updated
    • PNC_3_of_7_Update all entities when Priority Number is updated Manually
    • PNC_4_of_7_Update first page of entities when Priority Number is updated by Rule
    • PNC_5_of_7_Update second page of entities when Priority Number is updated by Rule
    • PNC_6_of_7_Update third page of entities when Priority Number is updated by Rule
    • PNC_7_of_7_Initial Priority Number calculation Main Rule
  • Replace the entity at the trigger section (by default Portfolio Epic and Epic) or add the needed entity type:

Targetprocess Image

  • Click JSON tab
  • Update Parameter Values:
    • Add a new block of values for Feature or replace the entity name at the existing blocks for Portfolio Epic or Epic
  • Click Save button

Targetprocess Image

Apply the solution to only specific set of entities

The are the following parameters that can be changed if needed:

Common property:

  • cfPriorityNumber – it defines the name of a custom field (by default Priority Number), where you store the Priority Number. If you'd like to name it differently, provide the custom field's name here. The field should have the same name for all the entities.

Entity-specific settings (can be set for each entity separately):

  • cfGroup – by default, it's set to null, which means you won't prioritize within custom field values. Set the needed custom field name here to prioritize within a specific category (custom field values). Format: "Custom Field Name", e.g. "To Prioritise"
  • cfValuesToPrioritise – the value in a drop-down custom field which you'd like to make prioritisation for. For example, you have a custom field To Prioritise with the values null or Yes. Then if you set Yes as a cfValuesToPrioritise value, then only the entities with the selected value Yes will be prioritised and all the other entities won't.
  • excludeStates – if you want to exclude some states from prioritization, then add the name of the states. Format: "Entity State Name", e.g. "In Progress"
  • groupByProject – by default, the parameter is set to false, which means prioritization will happen across all the Portfolios (Projects) in the system. Set it to true if you'd like to set Priority Number within each Portfolio separately.
  • excludeFinalState – set it to true, if you want to exclude entities in the Final state from prioritization
  • excludeInitialState  set it to true, if you want to exclude entities in the Initial state from prioritization
  • doPrioritization – set it to true, if you want Priority Number field to update the Rank of entities

To update the rule parameters, please do the following:

  • Go to Settings -> Automation Rules
  • Open the following rules one by one:
    • PNC_1_of_7_Priority Solution Pre-Setup
    • PNC_2_of_7_Update Priority Number when Entity State, Rank, Project or Group By Custom Field is updated
    • PNC_3_of_7_Update all entities when Priority Number is updated Manually
    • PNC_4_of_7_Update first page of entities when Priority Number is updated by Rule
    • PNC_5_of_7_Update second page of entities when Priority Number is updated by Rule
    • PNC_6_of_7_Update third page of entities when Priority Number is updated by Rule
    • PNC_7_of_7_Initial Priority Number calculation Main Rule
  • Click JSON tab
  • Update the parameters mentioned above. Please note that the parameter values should be the same for all the rules
  • Click Save button

Configure Prioritization within a category (Custom Field values)

To perform prioritization within a category (custom field values), you'll need to do an additional configuration. Please note that the only custom fields of type Drop-Down List can be used in the solution.

  • Adjust trigger at the Automation Rule:
    • Go to Settings -> Automation Rules
    • Open the following rule:
      • PNC_2_of_7_Update Priority Number when Entity State, Rank, Project or Group By Custom Field is updated
    • Replace the predefined To Prioritise custom field by the needed Custom Field Name in the rule trigger section
    • Click Save button

 

In all the Automation Rules of the solution:

  • Go to JSON tab:
  • Fill cfGroup parameter with the name of the custom field
  • Fill cfValuesToPrioritise parameter with the needed to prioritise custom field values if needed

Use another name for Priority Number field (optional)

If you'd like to use a different name of the field instead of Priority Number, you'll additionally need to adjust the trigger for this field in all the Automation Rules. To do that:

  • Go to Settings -> Automation Rules
  • Select rules 2-7 one by one
  • Replace the trigger with a new name of a custom field:

Set Priority Number for existing entities

If you already have entities in the system, we need to trigger the initial calculation of Priority Numbers for them. They will be set based on the entities Rank. To do that:

  • Ensure that all the Automation Rules have the requires settings set
  • Go to Settings -> Automation Rules
  • Enable and open the following rule:
    • PNC_1_of_7_Priority Solution Pre-Setup
  • Click Save and trigger now button

--------------------

Version 3.0

Integrations

See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.

Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.

For Transparency above the Team Level 
 
EXPAND 2 INTEGRATIONS

Azure DevOps
Azure DevOps
Add Targetprocess on top of the team level tool: get visibility on Product and Portfolio level.
Atlassian Jira Software
Atlassian Jira Software
Ensure free data flow from Jira to Targetprocess for greater visibility for all team members.

For Continuous Integration and Continuous Delivery 
 
EXPAND 6 INTEGRATIONS

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
GitLab
GitLab
Automatically link branches and merge requests to Targetprocess entities.
GitHub
GitHub
Automatically associate branches and pull requests with Targetprocess entities.
Phabricator
Phabricator
Link code revisions with any Targetprocess entity.
Bitbucket
Bitbucket
Automatically associate branches and pull requests with Targetprocess entities.
Jenkins
Jenkins
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.

For Product Management, ITSM, Sales and Marketing to Stay on the Same Page 
 
EXPAND 5 INTEGRATIONS

Miro
Miro
Centralize unstructured communication on Miro’s online whiteboard inside Targetprocess.
Microsoft Project Server
Microsoft Project Server
Provide visibility into high-level goals and details about implementation for all teams.
Salesforce
Salesforce
Synchronize customer service, sales, the PM office, and development teams.
Zendesk
Zendesk
Allow all team members to collaborate on shared artifacts from customer service tickets.
ServiceNow
ServiceNow
Collaborate on shared work items, consolidate reporting across the entire organization.