The priority codes are used to indicate the importance of features and guide team members when a requirement is in danger of missing a target milestone.

Pri 1

  • This requirement/feature must happen in the targeted milestone!
  • A specific meeting must be called to address any P1 item that is in danger of missing its target milestone.
  • Serious consideration will be put into moving a milestone back if there is no alternative to a P1 item otherwise missing the milestone.

Pri 2

  • This requirement/feature is of significant value to the targeted milestone.
  • P2 items that appear to be behind schedule should be discussed during weekly meetings.
  • A milestone will not be pushed back for a P2 item, but there will often be a need for some alternative compensatory action.

Pri 3

  • This requirement/feature is nice to have for the targeted milestone, but it may end up being a P1 by the time of the last milestone.
  • P3 items not on track for their targeted milestone will be discussed at triage meetings approaching milestone.
  • If a P3 is dropped from a milestone, it will be reprioritized for the next milestone. Unless it becomes a P4, it is still expected to be included in the currently developed version at some point.
  • P3 items should be given a concurrent priority number for the next milestone to indicate whether support for the item is wavering for just the current milestone or for the entire product version.

Pri 4

  • This requirement/feature is not expected to be part of any milestone. It is under serious consideration for being cut from the currently developed version of the product.
  • P4 items require no discussion to be dropped from any milestone.
  • Some minimal discussion should be had before officially cutting a P4 item from the entire version.

Pri X

  • This requirement/feature has been cut from the currently developed version of the product.