Willy's Reflections - Visual Studio ALM Rangers

| Willy-Peter Schaub | Visual Studio ALM Rangers | In search of IT simplicity, quality and tranquility |

Getting your priorities right … P0, P1, P2, …

Getting your priorities right … P0, P1, P2, …

  • Comments 4

Since I have started working at Microsoft I have had to absorb and remember a forest of acronyms and when it comes to assigning priorities to work items, issues or bugs, we encounter the P? acronym. BugHere is a short summary of the priorities we deal with:

P0 Do not do anything else, this is a blocker.
You can think of the Lancaster bomber flying over the English channel with 4 engines on fire … getting the fires out is a P0 priority.
P1 Must be fixed.
P2 Should be fixed, time and resource permitting.
P3 Might get fixed.
P4 Noted … this is one step away from the black hole.

What priorities are you using? I would be interested to see how others are managing their priorities within Team Foundation Server (TFS) and other ALM environments.

  • MoSCoW:

    M - Must have

    S - Should have

    C - Could have

    W - Wish list

  • P0 - Dead in the water, system is down or is corrupting data

    P1 - Critical issue for which there is no work around and a certain process cannot continue, but other areas of the system are still functioning

    p2 - Bug, but there is a reasonable workaround and will be addressed in next service pack

    P3 - Minor bug (typo, harmless, or otherwise) that will be fixed when time is available (i.e. almost never)

  • p0 Due in 30 minutes with a conversation

    p1 due in 30 minutes

    p2 due EOD

    p3 just do it tomorrow or the day after

    p5 ill ask you a question EOD to return to p3 status

  • p0 Due in 30 minutes with a conversation

    p1 due in 30 minutes

    p2 due EOD

    p3 just do it tomorrow or the day after

    p5 I don’t have time right now but ill take a look and email you a suggestion

Page 1 of 1 (4 items)
Leave a Comment
  • Please add 6 and 1 and type the answer here:
  • Post