Home » Currently Reading:

AKC15: Work Request History and Open Backlog

Description:

Provides a brief history of the requested application changes and enhancements completed during the last 6 to 12 months and a list of the change requests (work requests) either already “in process” or waiting in the priority queue (backlog) for assignment. Provides a list of all enhancements implemented within the last 6 months. This contains the what, who, when, where and why of all recently implemented enhancement requests. If there is an application failure or other type of production problem, a support analyst will look to what has changed recently. This again helps to identify possible problem areas based on recent changes to the application and reduces the fix time.

Provides understanding of recent changes so that, if there are problems, recently modified programs and/or jobs can be examined in order to minimize problem investigation time.

Provides information such as:

  • Number assigned to the Request
  • Date the Request was received
  • Date the Request was completed
  • Estimated Hours for the Request
  • Actual Hours in which the Request was completed
  • A brief Description of what the Request is intended to accomplish

How is it used?

Provides a list of all enhancements implemented within the last 6 months. This contains the what, who, when, where and why of all recently implemented enhancement requests. If there is an application failure or other type of production problem, one of the first places a support analyst will look is what has changed recently. This again helps to identify possible problem areas based on recent changes to the application. Reduces time to fix.

Why is it important?

(1) Provides understanding of recent changes so that, if there are problems, recently modified programs and/or jobs can be examined in order to minimize problem investigation time.
(2) Provides information such as:

  • Number assigned to the Request
  • Date the Request was received
  • Date the Request was completed
  • Estimated Hours for the Request
  • Actual Hours in which the Request was completed
  • A brief Description of what the Request is intended to accomplish

Our Sponsors

IT Support Services Comments

  • Bob Anderson: Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the ...
  • Bob Anderson: Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Compute...
  • Bob Anderson: Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you...
  • Bob Anderson: Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on...
  • Bob Anderson: Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, an...

ITIL V3 Application Support Q & A

If you have any question on the blog content or have some specific question on how ITSM & ITIL can dramatically improve performance and reduce the cost of your Application Support service "Ask Bob"
Question :
Answer :
Gunter, there are many possible SLA components and metrics that can be defined for any application software support. First I would recommend that you read this article which I had published in Computer World on "How to create Meaningful IT Support SLA's"  use this link...
Question :
Answer :
Daniel, from a certain point of view you are correct. CMMI- DEV deals primarily with software development best practices, the old CMM Level-5 dealt a great deal with defects. However, as you know the folks who developed the original CMM  were not really initially inter...
Question :
Answer :
Amiet, I would put it under the "Incident" process and track dates, number of occurrences, how much lost time, cause (who did it). You will need data for management if the practice has to stop. If you want to be "proactive" in stopping this practice" you must capture bu...
Question :
Answer :
Mark, it is doubtful that you can fix the problem, it is mainly a management issue. The best you can do is to gather statistics on the backlog of enhancements, the number and severity of incidents, and how many technical support calls from users you get and the average...
Question :
Answer :
Amit, first of all why is the customer powering down the equipment? This should be brought to the attention of management and a very strong note sent to whoever is doing this.  If they are doing it on their own without any instruction to do so and it affects other user...