Priorities in Project Management Systems

By Adrian Smith11 Sep 2017500 words2 mins to read

So today I got access to a customer's new JIRA task management system. Unsurprisingly, every task has a field priority, from highest, high, low etc. It's understandable that tasks might be sorted by urgency, to communicate that the most urgent stuff should be done first. But these aren't good names. I have had the following experience at various previous customers:

I try to find priorities with objective names, so that different team members can agree on which priority a particular task belongs to.

Having an ordered list of objective priorities allows one to state and discuss the philosophy of the organization, for example are bugs more important than features? Security holes more important than data loss?

Here are the priorities I use, from most urgent to least urgent:

  1. Security issues on the live system
  2. Data loss issues on the live system
  3. Stability issues on the live system (for example the whole system goes down sometimes)
  4. Bugs on the live system (for example, in a certain situation you get an error)
  5. Things that have been promised
  6. Things that are important for the customer
  7. Bugs, not on any live system
  8. Most important next steps
  9. All other things

That is to say, I would prefer to lose the user's data than allow someone else to have access to it. And I would prefer the system to be down, than the user to lose their data. And I would prefer users see an error in a particular situation, than the whole system go down and every user see an error.

This article was written by Adrian Smith on 11 Sep 2017

Follow me: Facebook | Twitter | Email

More on: Project Management