Team

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

Agenda

  1. Clarification/Feedback from Erv
  2. Focus groups
  3. Communications plan

Meeting Notes

  1. Clarification/Feedback from Erv
    1. This project needs to include plans to change all passwords, including PID, Banner/Oracle, and Hokies.
      • Note: the web service for Hokies passwords will have to be completely built from scratch.
      • Action item: Greg will invite a representative from MIG to future project meetings.
      • See Brenda's comments below.
    2. Erv requested project phases and timelines be included in the project initiation form to include a self-service password reset for all 3 passwords before he approves the project.
      • Action item: Greg, Karen, and Kevin will revise the project initiation form. Greg will send the revised form to Brenda for Erv's approval.
    3. Another separate password change project (for weak passwords) needs to be discussed.
      • See Brenda's comments below.
    4. Jeb Stewart will negotiate project timelines with Internal Audit (IA).
  2. Focus groups Potential focus groups include:
    1. Authenticating using something like OpenID. Already used by Google & Yahoo. Kevin will mock up a prototype for testing by Kim Homers team. 4Help student consultants are a suggested test group.
    2. A "geek" focus group to discuss technical details of implementation.
    3. A group to discuss potential opportunities for collecting information from the user. This may be a mini-project or project phase in itself.
      • Action item: Kevin will organize the focus groups.
      1. There was some discussion about the possibility of adding something to the VT Alerts sign-up page asking if the information collected could be used for self service password resets also.
      2. Comment: The tool/service should be smart enough to know what credentials (PID, Banner/Oracle, Hokies) the user already has.
      3. The order of importance of the components needed for this project are:
        1. Authentication method
        2. User preferences
        3. Notifications