HomeMy WebLinkAbout20150818AVU to Staff 92.docAVISTA CORPORATION
RESPONSE TO REQUEST FOR INFORMATION
JURISDICTION: IDAHO DATE PREPARED: 08/14/2015
CASE NO.: AVU-E-15-05/AVU-G-15-01 WITNESS: Jim Kensok
REQUESTER: IPUC RESPONDER: Mark Gustafson
TYPE: Production Request DEPARTMENT: IS/IT
REQUEST NO.: Staff - 092 TELEPHONE: (509) 495-2640
REQUEST:
Page 64 of Mr. Kensok’s testimony states: “Through this process, the efficiency and performance of the new applications is improved, and important technical knowledge is transferred from the application developers to those who will have responsibility for the long-term maintenance of the systems.” Please describe the process used to identify and manage defects, a current list of known or anticipated defects, and the status of any defects.
RESPONSE:
The process used to identify and manage defects is described in Mr. Kensok‘s testimony at (page 64 line 16 through page 65 line 8):
Q. What are the tasks associated with the work of project support?
A. Several integrated technical teams were organized to support new users of the new applications. The support process begins when a user has a question or reports a problem to a group composed of subject matter experts/mentors who can address a range of technical and work process-related questions. This group can in turn rely on two technical support teams representing the Maximo and Customer Care & Billing applications. These support teams answer technical questions as well as identify the source of a reported problem (e.g. a defect in the application, the need for a work process change, or a training issue). These issues are reported to either the project stabilization group, or the team responsible for managing the Post-Go Live applications, where they are ultimately resolved.
The current (as of 8/2/15) list for CC&B and Maximo known defects and their status is provided in Staff_PR_092 Attachment A - Backlog including Status. The term defect as used in this workbook is a condition in a software product or customization which does not meet the original designed software requirement (as stated in the requirement specifications, user story, business process or business use case) or end-user expectations (which may not be specified but are reasonable).
Page 1 of 1