Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. 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) - ServiceNow has provided information back to Bill to help resolve this issue.
  2. Lou would like to know the level of effort for opening up the related record fields in Change to be update-able at any point while the Change is open.  Bill will provide the LOE for this.
  3. Mark has asked Ricardo to please look at R-797 (email replies don't get appended to the ticket for other modules other than Incident) as the main module affected from the customer stand point is Request.  This does affect other modules as well but mostly Request from a customer stand point.
  4. Adriene would like to remind everyone to go through their list of enhancements and review them for anything that should not be done and removed from the list.  She wants to reduce our demand from this list by 10%.
    1. Put in Ade's questions from last week again for reminder.When reviewing the list Process Owners should ask themselves if this enhancement would add value to more than just one unit.  Will this help to improve the process?  Will the enhancement move ITSM forward?

PRIORITIZED ITEMS AFTER MEETING

...

  1. Bill to provide the level of effort for opening up the related records fields in change to be update-able at any point as long as the Change is till open. (from 8/26)
  2. 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)
  3. Bill to add the following modules to the ServiceNow application in the CMDB:  Incident, Problem, Change, Request, Knowledge, Configuration (from 5/29)
    1. This can't be done until the application inventory is integrated with ServiceNow.  RITM0053604 is in the INF SN App queue for this to be completed after the application inventory is integrated.
  4. Bill to provide an estimate of development time on R-756.  If the level of effort is low it may move higher up the list (from 8/19)Bill to provide an estimate of dates DEV work can be completed on each item on the list that is currently in the DEV pipeline.  He will not need to provide info on items still in the requirements gathering phasethe items on this list that have TBD in the Development Complete Target column. (from 8/1926)
  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 (from 7/22)
    1. Will add this to an upcoming meeting
  6. Tim to come up with a plan to retire the affected components that are in the CI field (from 7/29)
  7. DONE - Chloe to update HPQC and the Excel spreadsheet with today's updates.
    1. https://yale.box.com/s/00ndty4qhdlwdpz15rvy