2013-11-11 - Process Owners Operational

AGENDA

  1. Discuss issues (if any) from the last release
  2. Review the current work stream
  3. Discuss any new work to be added to the work stream
  4. Discuss prioritization of work stream
  5. Discuss open Action Items

ROLL CALL

Name

Representing

Attended

Alternate Attendee

Adusumilli, Hari

ServiceNow QA

(tick)

 

Boeher, Cheryl

Problem Process

(error)

None

Chavira, Ricardo

Service Catalog/Request Process

(tick)

 

Ortale, Dorothy

Knowledge Process

(error)

None

Kovacs, Mark

Incident Process

(tick)

 

Smith, Rick

Metrics/CSI Process

(error)

None

Tiseo, Lou

Change Process

(error)None

Turnbull, Chloe

ServiceNow Team Lead

(tick)

 

Valdes, Julio

Configuration Management Process

(error)Tim Nichols

West, William

ServiceNow DEV

(tick)

 

Costantino, Christine

START Replacement Project Manager

(tick)

 

Nichols, Tim

CMDB Project Manager

(tick)

 

Radcliffe, Adriene

ITSM Director

(error)

N/A

Sonson, Soren

Request Process

(tick)

 

MEETING NOTES

DISCUSSION

  1. No issues reported from this weekend's release.
  2. Staffing updates
    1. Fred Roos, a developer from Fruition, started today.  He will be on site and sitting with Bill and David.
    2. Casey Watts will be working with our team a couple of days a week.
  3. Project Updates
    1. CMDB
      1. Development is being done on Release 6 and 7.  Specifically application attributes and maintaining the application inventory through the CMDB instead of Quickbase.
      2. UAT for maintaining the applications will be done by some of the business support teams like Arun or Joyce Lush.  Depending on how this training goes it will dictate mass training needs.
    2. START
      1. Releasing the Ethernet form into Production.  It will be hidden until go live.
      2. The Training instance should be updated weekly now and the START forms that are hidden in Production should be showing in TRAIN so that training can be developed.
      3. Pagers (add, change, delete) is completed.  UAT for this is happening tomorrow.  This could potentially be released on Friday, depending on UAT.
      4. Development of the START forms should be completed by mid-Janaury.
      5. March 21 is scheduled go live for START forms.
      6. Training users will happen in March.
  4. John Pagliuca is asking for a status update on R-765.
    1. This was moved up to the top of the RTS list a few weeks ago at our last process owner's meeting and John would like a status update and an ETA on when this will be available for him to test.
    2. Bill will review the requirements and let Chloe know if he has any questions or concerns and begin development work on this after his review.
  5. Going forward we should be providing metrics on how items are affecting the business to assist with prioritizing items.
  6. Mark, Ricardo and Soren have provided feedback on the items on the defect/enhancement spreadsheet for Incident and Request.  We still need input for any items on the list for Change, Problem, Metrics and Knowledge.  Also everyone should take a look at the items flagged as 'General System' as they span multiple processes and may affect yours.
  7. D-556:  This could be a month of development to complete this for all modules.  We should start with specific complaints or reports. Defect needs to be refined a bit.



RTS PRIORITIES AND STAFFING PERCENTAGES

Business Analysis:  Dave Rich 100% (after transition from testing to John Schmidt)

Development::  Bill West 50%

Testing: John Schmidt 50%

Priority

Item #

Description

BA Level of EffortBA - % CompleteDEV Level of EffortDEV - % CompleteTEST Level of EffortTEST - % Complete

Process Owner
Approval Date

Scheduled Release
Date

1R-765Re-Work the DSP Contracts to accurately reflect who is supported to the DSP Teams and who is supported by FAS-ITHoursCompleted 9/16/2013    9/16/2013 
2

R-821

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

Weeks50%    

 

 

3

R-813

Allow clients to request assistance online via chat

HoursCompleted 5/31/2013    

5/31/2013

 

4

R-630

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

Hours0%    

 

 

5

D-556

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

Hours50%    

7/15/2013

 

6

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)

DaysCompleted 8/14/2013    

8/14/2013

 

7

R-901

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

Days100%    

9/9/2013

 

8

R-767

Implement New Ticket Feature in the DEV or TEST instance

Weeks100%    

5/31/2013

 

9R-1094Notification for Knowledge Records that are about to expireHours50%      

10

R-978

Problem Process redesign

Weeks0%    

 

 



CMDB PRIORITIES AND STAFFING PERCENTAGES

Business Analysis:  David Logie 10% (through 11/30)

Development::  Bill West 50%

Testing: Hari 25%

Priority

Item #

Description

BA Level of EffortBA - % CompleteDEV Level of EffortDEV - % CompleteTEST Level of EffortTEST - % Complete

Process Owner
Approval Date

Scheduled Release
Date

1R-XCMDB Release 5, 6 and 7????????



START REPLACEMENT PRIORITIES AND STAFFING PERCENTAGES

Development::  David Backeberg 100%, Fruition Consultants

Testing: Hari Adusumilli 50%

Priority

Item #

Description

BA Level of EffortBA - % CompleteDEV Level of EffortDEV - % CompleteTEST Level of EffortTEST - % Complete

Scheduled Release
Date

1R-XSTART Replacement Forms/WorkflowMonths100%Months90%Months60%3/21/2014



OUTSTANDING ACTION ITEMS

  1. Process Owners to review their list of enhancements in their area and see what they can remove so that we can reduce the amount of work in the bucket (aka the demand) (from 8/19)
  2. 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 (from 7/22)
    1. Will add this to an upcoming meeting
  3. Tim to come up with a plan to retire the affected components that are in the CI field (from 7/29)
  4. Bill to review the requirements for R-765 and let Chloe know if he has any questions or concerns and begin development work on this after his review. (from 11/11)
  5. DONE - Chloe to update HPQC and the Excel spreadsheet with today's updates.
    1. https://yale.box.com/s/00ndty4qhdlwdpz15rvy