Problem Management Business Process Requirements Item # Business Requirement Owner MoSCoW Priority Ranking (1=Highest 5 = Lowest) PM - 1.0 Proactive Problem Problem Management Manager PM - 1.1 Analysis of Incident and M 1 Problem Data PM - 1.2 M 1 Produce Trending and Analysis Reports PM - 1.3 Determine if Issues Should M 1 be Advanced PM - 2.0 Problem Detection and Problem Logging Manager PM - 2.1 Recording of all identified M 1 problems PM - 2.2 Procedures to identify M 1 Problems PM - 2.3 Ability to create problems M 1 from existing incidents without using trending analysis such as one off major incidents PM - 2.4 Ability to perform trending M 1 analysis on existing incidents for the purpose of identifying problems PM - 2.5 Ability to create a problem M 1 ticket from within a Incident Ticket PM - 2.6 Only a defined set of M 1 personnel (which include the Problem Manager and Problem Coordinators) can create Problem records
Problem Management Business Process Requirements Item # Business Requirement Owner MoSCoW Ranking Priority (1=Highest 5 = Lowest) PM - 1.0 Proactive Problem Management Problem Manager PM - 1.1 Analysis of Incident and Problem Data M 1 PM - 1.2 Produce Trending and Analysis Reports M 1 PM - 1.3 Determine if Issues Should be Advanced M 1 PM - 2.0 Problem Detection and Logging Problem Manager PM - 2.1 Recording of all identified problems M 1 PM - 2.2 Procedures to identify Problems M 1 PM - 2.3 Ability to create problems from existing incidents without using trending analysis such as one off major incidents M 1 PM - 2.4 Ability to perform trending analysis on existing incidents for the purpose of identifying problems M 1 PM - 2.5 Ability to create a problem ticket from within a Incident Ticket M 1 PM - 2.6 Only a defined set of personnel (which include the Problem Manager and Problem Coordinators) can create Problem records M 1
Fermilab%20Problem%20Management%20Requirements%20version%201.0.docx