Technical Team

Marvin Addison, Marc DeBonis, Daniel Fisher, Karen Herrington, Kim Homer, Mike Hosig, Greg Kroll, Steve Legge, Ken McCrery, Andrew Olson, Kevin Rooney, Brenda van Gelder

Agenda

1. Discuss recommendations from the Advertising-Marketing meeting
   1. To avoid confusion for users with the change password project it is recommended that this project not begin any advertising or promotion until after the change password project go-live date of July 1, 2011.
      • Note: The advertised implementation date for the change password project is 7/1/2011, however, in order to accommodate for the end of 1st summer session 2011 and the Fourth of July university holiday the actual or enforced implementation date is July 6, 2011.
   2. It was recommended to delay the "CAS nagging" until August 2011.
   3. It was recommended to advertise this self-service password reset application at New Student Orientation (NSO) that begins July 11, 2011.
   4. It was recommended that if possible, this SSPR application should be put into production before the Change Password project implementation of July 1, 2011 in order for users to be able to set their account recovery options prior to having their password expired on July 1st.
      • Is a June 1, 2011 production date possible?
   5. From a technical perspective it was recommended that the production implementation of the change password and SSPR applications do not occur on the same date.
2. Issues, questions, and status update from development teams

Attendees

Attendees: Marvin Addison, Hashim Durrani, Daniel Fisher, Karen Herrington, Kim Homer, Mike Hosig, Greg Kroll, Ken McCrery, Andrew Olson, Kevin Rooney

Meeting Notes

1. Regarding the recommendations in the above agenda, if the June 1st production date is feasible then the other recommendations about delaying the advertising and CAS "nagging" are invalid because then we would want to promote the self-service password reset prior to passwords expiring on July 1, 2011 due to the change password project.
2. It is feared that since the change password project is already promoting itself if we start advertising the self-service password reset project this may confuse users especially those that have already changed their password(s) and now think this is somehow related.
   • This team tentatively agreed on a June 1, 2011 go-live date.
3. There was discussion about a tighter coupling/integration of CAS and Account Manager
4. An analysis of guest access and associated workflow is a whole separate project.
5. SMS gateway
   1. Does it need load testing? If so, this may have to wait until our contract with bulletin.net is complete.
   2. "Profiling" looks good.
6. IVR (Interactive Voice Response)
   1. May not be ready by June 1, 2011.
   2. Currently there is nothing available for testing.
   3. We need a drop dead date by which testing must begin or leave IVR for a later date.
   4. Kevin will "nail down" CNS on this service.
7. OpenId
   1. We are waiting for an opinion from VT legal on use of this service.
   2. We may need a "vanity domain" (URL) to use for the "realm".
   3. Ken recommended against using a vanity domain as that introduces yet another one to maintain and manage a certificate for. Ken recommends using my.vt.edu which is a persistent URL and will likely never go away.
   4. Kevin & Andrew will meet to discuss further but agree that the URL cannot change.
8. Testing and Usability
   1. How should we formalize testing?
   2. We need feedback (from non-developers) on the user interface (UI).
   3. IP&S has a graduate student on staff that is an expert in UI. They will use him to do some quick usability testing.
   4. Who will distill feedback from usability testing into requirements for the UI?
   5. IP&S will start using their graduate student, then based on his recommendations make changes to the UI before using the resulting UI in a wider usability testing with Kim's team.