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

Version 1 Next »

General Info

Regularly scheduled for 2pm weekdays. Subject to change: email william.west@yale.edu to get added to the meeting invite.

Call-In Info

  1. Dial (203) 436-5777 or (855) 925-3266.
  2. Enter Meeting ID 68840 and #.
  3. Speak you name, then enter #.

Work Priority/Sequence

From: 2013-04-29 - Process Owners Operational
E-810 - Metrics - Grant table access for Mirror42 so they can proceed with a proof of concept.
STATUS: I believe these requirements are complete and signed off by everyone
E-821 - Change - Update Change process and update ServiceNow to reflect those process changes. This will be done as part of the CMDB project.
STATUS: Requirements/process work to start up again soon.
E-798 - Incident - Implement customer satisfaction survey for Incident module
STATUS: Requirements have been approved by Jim and committee and Chloe. Awaiting acceptance of requirements from Bill and Hari.
E-715 - General System - Implement the 'Client (Unified)' field to include REQ, RITM and SCTASKS
STATUS: Requirements approved by everyone I believe
E-630 - Knowledge - Define a process for letting support teams know when there is new KB article that may be of interest to them.
STATUS: Requirements gathering needs to begin for this process. Dorothy to work with teams to develop these requirements.

Release Status

text to show when browser does not support iframes

Roll Call

Name

Org

Present

Bill West

Yale Dev

(tick)

David Backeberg

Yale Dev

(tick)

Chloe Turnbull

Yale BA

(tick)

Hari Adusumilli

Yale QA

(tick)

Timothy Nichols

Yale PM

(tick)

Ricardo Chavira

Yale ITSM

(tick)

Christine Costantino

Yale PM

(tick)

Robert Liu

Yale Dev

(error)

Adriene Radcliffe

Yale ITSM

(error)

Jason Shuff

Yale QA

(error)

Julio Valdes

Yale Config Mgmt

(error)

Agenda

Please come to the meeting on time & prepared

  • If you don't have a status change, that's OK! Just say so.
  • What did you do yesterday?
  • What are you doing next? (like, within the next day or two? Break "ongoing" tasks into pieces).
  • What obstacles are slowing/stopping progress?

Discussion

David:

  • Done:
    • mockup phone services for Kesha's review
    • pushed START items to UAT+QA pass column
    • meet w/ Christine work on Visios
  • Next:
    • incorporated Kesha feedback in phone services mockup
    • arrange with Kesha for UAT of QA-passed items
  • Obstacles:
  • Backlog:

Bill:

  • Done:
    • CMDB application data load work (group, director)
    • R806 work – passed UAT
  • Next:
    • push regression items to preproduction (Wed PM)
    • next dev doc/change request
    • CMDB data contracts
    • one or two addtional fields
    • level-set of CMDB reqs (add to Trello, reject/close irrelevant ones)
  • Obstacles:
  • Backlog:
    • Request Process functional doc draft
    • schedule a SN KB hackathon

Hari:

  • Done:
    • several items passed QA
  • Next:
    • regression in preproduction
  • Obstacles:
  • Backlog:

Bob:

  • Done:
  • Next:
    • R70 mobile approval
  • Obstacles:
    • access on prod (I will get this for you when you're ready to migrate work to prod -bw)
  • Backlog:

Ricardo:

  • Done:
  • Next:
  • Obstacles:
  • Backlog:

Chloe:

  • Done:
    • provided feedback for R793
    • submitted SN enhancement req (R897)
  • Next:
    • R780 SDR follow-up
    • R786 UAT follow-up
    • R791 UAT follow-up
    • R792 UAT follow-up
  • Obstacles:
  • Backlog:

Adriene:

  • Done:
  • Next:
  • Obstacles:
  • Backlog:

Christine:

  • Done:
  • Next:
  • Obstacles:
  • Backlog:

Jason:

  • Done:
  • Next:
  • Obstacles:
  • Backlog:

Julio:

  • Done:
  • Next:
  • Obstacles:
  • Backlog:

Past Meetings

  • No labels