Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

AGENDA

  1. Discuss issues (if any) from the last release
  2. Ricardo to update on his discussion with Russell about getting more resources
  3. Review the current work stream
  4. Discuss any new work to be added to the work stream
  5. Discuss prioritization of work stream
  6. Discuss Action Items for next release(s)

ROLL CALL

Name

Representing

Attended

Alternate Attendee

Adusumilli, Hari

ServiceNow QA

(tick)


Boeher, Cheryl

Problem Process

(tick)

 

Chavira, Ricardo

Service Catalog/Request Process

(tick)

 

Ortale, Dorothy

Knowledge Process

(tick)


Kovacs, Mark

Incident Process

(tick)


Smith, Rick

Metrics/CSI Process

(tick)

 

Tiseo, Lou

Change Process

(tick)

 

Turnbull, Chloe

ServiceNow BA

(tick)

 

Valdes, Julio

Configuration Management Process

(tick)


West, William

ServiceNow DEV

(error)

 

Costantino, Christine

START Replacement Project Manager

(tick)


Nichols, Tim

CMDB Project Manager

(tick)

 

MEETING NOTES

DISCUSSION

  1. YaleSecure wireless was having issues and Cheryl, Mark and Julio needed to leave to handle support for the issues for a portion of the meeting.
  2. Release went as planned this weekend.  Have heard no feedback or fallout from the release.
  3. START Replacement go-live  is now going to be sequenced with the IAM updates.  This may delay the release of START replacement until sometime between September and December.
    1. START replacement will depend on the IAM structure for some of its request fulfillment and approvals
    2. Client Accounts would be negatively impacted if the START Replacement goes live before the IAM integration.  They have automated workflow currently available in START that would not be available in ServiceNow until the IAM integration.
  4. Lou Tiseo brought up concerns about the ITSM team not following the Change process with the weekly releases.  Discussion to continue with Bill, Lou, Ricardo and Chloe offline.
  5. The group would like to nail down the process of how enhancements are requested (and defects are logged) and how they make it from a request to release.  We can discuss this process at one of our upcoming meetings.
  6. Ricardo met with Russell Sharp regarding the need for more resources.
    1. Russell has agreed that we can use more resources and perhaps a restructuring of our current team to ensure we have a technical lead with enough time allocation to perform their duties and enough technical resources.  Russell has also agreed that we are also in need of more BA resources to assist with requirements gathering.
    2. Ricardo will take the list of enhancements/defects and break the work into chunks (e.g. defect fixes, service request form creation/changes)

PRIORITIZED ITEMS AFTER MEETING

Priority

Item #

Description

Process Owner
Review

Process Owner
Approved (Date)

Dev Team
Review

Final Approval
(Date)

In Development

In Test

Scheduled Release
Date

1

R-X

CMDB Release 4 & 5 Work

 

 

 

 

X

 

8/2/2013 (R4); 8/16/2013 (R5)

2

R-X

START Replacement

 

 

 

 

X

 

9/27/2013

3

R-821

Change - Update Change process and update ServiceNow to reflect those process changes.  This will be done as part of the CMDB project.

X

 

 

 

 

 

 

4

D-564

Incident Customer Satisfaction Survey tasks not being created when a respondent indicates on the survey they wish to be contacted for follow up

 

7/19/2013

 

 

X

 

 

5

R-630

Knowledge - Define a process for letting support teams know when there is new KB article that may be of interest to them.

X

 

 

 

 

 

 

6

R-897

New Service Request:  ServiceNow Enhancement Proposal.  Requested by the ITSM team.

 

5/6/2013

 

5/6/2013

X

 

7/26/2013

7

D-556

Users can save/resolve/close tickets without filling out all of the required fields

 

7/15/2013


 

X

 

 

8

R-926

New Service Request:  IAM - Attribute Release Form

 

7/15/2013


 

X

 

 

9

R-938

New Service Request:  Software Library Addition or Change

 

7/15/2013


 

X

 

 

10

R-901

Allow Request forms to be visible and fill-able by persons outside Yale

X

 

 

 

 

 

 

11

R-813

Allow clients to request assistance online via chat

 

5/31/2013


 

X

 

 

12

R-767

Implement New Ticket Feature in the DEV or TEST instance

 

5/31/2013

X

 

 

 

 

13

R-896

Determine a way to let Len Peters and Leadership know when a P1 Incident has been created (this replaces the old E-795)

X

 

 

 

 

 

 

14

R-902

Cheryl Boeher needs ability to edit Problems after they are closed

X

 

 

 

 

 

 

15

R-X

Make changes to client facing new Incident form


7/22/2013

X

 

 

 

 

CURRENT RESOURCE ALLOCATION

  • Chloe: 100% on RTS; work on START Replacement or CMDB as needed
  • Hari: 50% on START Replacement; 25% on CMDB; 25% on RTS (100% allocation to Service Management, can be adjusted between projects and RTS work as needed)
  • Bill:  90% on CMDB; 10% on RTS
  • Dave: 100% on START Replacement

OUTSTANDING ACTION ITEMS

  1. Bill to add the following modules to the ServiceNow application in the CMDB:  Incident, Problem, Change, Request, Knowledge, Configuration (from 5/29)
  2. Hari to make estimate on length of time it will take to do testing for open items on the list.  Use "Level of Effort - TEST" column in HPQC. See Chloe with questions. (from 6/24)
  3. All Process Owners review their items on the defect/enhancement list for items that can be removed (from 7/1)
  4. Chloe to set up a meeting with Bill, Lou and Ricardo to discuss ServiceNow Release process and how it interacts with Change Management
  5. Chloe to add an agenda item to one of our upcoming meetings to discuss the enhancement/defect logging process and how an item makes it from request to release
  6. DONE - Chloe to update HPQC and the Excel spreadsheet with today's updates.
    1. https://yale.box.com/s/00ndty4qhdlwdpz15rvy

.

  • No labels