Team

Susan Brooker-Gross, Mary Dunker, Daniel Fisher, Karen Herrington, Kim Homer, Greg Kroll, Joyce Landreth, Randy Marchany, Kevin Rooney, Nate Smith, Brenda van Gelder
((tick) present, (error) absent)

Agenda

  1. Status
    1. Project Initiation Form approval
    2. IT Project Management Portfolio - switch from SETI to CT (Converged Technologies)
    3. VT issued cell phone for testing
    4. Focus groups
    5. Requirements analysis
  2. Begin scope development
  3. Begin project communications planning

Meeting Notes

  1. Status
    1. Project Initiation Form approval
      1. Still waiting to hear from Erv or Jeb.
        1. Action item: Greg will talk to Jeb about this.
    2. IT Project Management Portfolio - switch from SETI to CT (Converged Technologies)
      1. Done. Just before the meeting started.
    3. VT issued cell phone for testing
      1. Karen was informed that these charges were to come out of her budget.
        1. Action item: Greg will talk to Randy Pelt about this.
    4. Focus groups
      1. "Technical" and "security" focus groups have met and good information was collected.
      2. Kevin & Kim met with Matthew Mathai and Andrew Olson to discuss self-service password reset usability.
        1. One recommendation is to be sure to use third party e-mail if we use OpenID.
        2. Since IT people are not good testers we need to be sure to some "real" end users when testing. One suggestion is to get someone that does
          alumni support since alumni more commonly call in for a password reset.
        3. Action item: Kim will prepare wireframes to be ready for testing.
      3. 4Help would like to be involved in testing. Especially the workflow (exactly what the end user will go through and see).
      4. May invite the TechSupport community to comment on this project.
      5. Kevin also met with Carl Harris, Phil Benchoff, and Richard Quintin to discuss the project. No resulting surprises.
        • Richard commented that he is not comfortable with a self-service password reset for Oracle/Banner password.
        • Someone clarified that this service would only be for Oracle/Banner accounts associated with real people as opposed to other Oracle/Banner accounts.
      6. Kevin would like to wrap up all focus group meetings by the end of September 2010. Kim commented that we may want to target people on campus that deal with "new people to VT", i.e., HR, admissions, etc.
    5. Requirements analysis
      1. Regarding the idea of using VT Alerts as a data collection point or use the actual data (cell phone numbers).
        1. Kevin spoke with Carl about this and Carl said we should make the request to Mark Owczarski in University Relations.
        2. Be sure to make a distinction between the possibilities of (1) using the VT Alerts signup screen as a collection point for data for self-service password reset, i.e., ask the user if they would like set their preferences for SSPR?, and (2) using the cell phone from the VT Alerts data store to present to the user to ask if we can use this already entered cell phone number.
        3. Since some people put spouses or parents cell phone numbers for VT Alerts we want to be sure that for SSPR we are getting the cell phone number associated with a user's PID ONLY!
        4. It was decided that we would wait for usability testing to decide whether we need to approach University Relations with this request.
      2. Current thinking is to use a combination of OpenID and third party e-mail for user testing and see how it goes. Usability testing may show that we only use SMS and not e-mail.
      3. One suggestion for students is to capture their third party e-mail used in the VT admission process. This e-mail address needs to be replicated to the registry. If this is used we would have to come up with someplace where the user could change this e-mail address. MyVT?
      4. Action item: Kevin will begin writing the requirements document.
  2. Begin scope development
    1. Greg shared a draft of the start of a project scope document.
      1. Action item: Please review and send comments to Greg.
  3. Begin project communications planning
    1. Greg shared a draft of a project communications plan.
      1. Action item: Please review and send comments to Greg.