Biweekly Trainer's Meeting Agenda & Notes 03-09-11

Agenda/Notes:

Send email to jmjohnstone@ucdavis.edu know if you'll need to dial in and I'll set up the Toll-free ReadyTalk line: 866-740-1260, access code 7545991

Attendees: Joyce

Topics

  1. Training schedule issues
    1. for Steve - check with Fernando on assisting with gradebook drop-ins for grading period starting next week.  Steve will be on campus this week in case Fernando needs assistance.
    2. for Fernando - none
    3. Spring quarter start up - do more drop-ins; training sessions not well attended; do four drop-ins and one training session.  Begin of quarter and end of quarter 3/2. Complete:  Need to clear with Kirk - Steve notified Kirk and they had a email dialogue to confirm.  Change location to Surge II small conference room with three laptops starting Spring Quarter.
    4. Larger vision for training and support as user experience evolves - Action: Joyce send email to Liz/Kirk to see how to go forward on this.
  2. Remedy or RSN Ticket Status
    1. Remedy tickets; check with Dan/Mike on backup plans/capacity planning when short-staffed. Update: Effective immediately Dan will have Theo triage and assign tickets to SmartSite team (Steve or Dave) when ITX is short-staffed. This way tickets won't sit at ITX. Theo starts the process early in AM at the start of his shift.
    2. SmartSite Support Plan
  3. Communication Tasks
    1. See Jira Tickets below
    2. Fernando - SS-276; posted comment Fernando will review document and have Kirk post.

Past Action Items:

  1. Continue to clean up Jira tickets.
  2. Posted changes to CMDCOM-11 on 10/14 for Middleware to complete these changes: due from Middleware Feb 2011.
  3. Posted another comment (on 2/22) to Kirk SAK-549 - Kirk to see if this was still planned:  Where is the request for stuID in roster and pictures?

Real-time list of Blocker & Critical tickets for next production release

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.