Attendees

Phil Benchoff
Susan Brooker-Gross
Al Cooper
Mary Dunker
Frank Galligan
Karen Herrington
Greg Kroll
Randy Marchany
Ismael Alaoui

Agenda

  1. Project(s) structure, roles, and responsibilities.
  2. Scheduling future meetings.
  3. Review the Soft PDC project initiation form.
  4. Review project level indicators and complete the project scorecard.
  5. Begin Scope development
    1. Review these Background Questions.
    2. Identify stakeholders

Meeting Notes

  1. Project(s) structure, roles, and responsibilities.
    1. Over arching project is Soft PDC, first phase is Policy Development which is needed before any software development can take place.
    2. Project Manager: Greg Kroll
    3. Project Leader: Frank Galligan
    4. Project Sponsor: Policy Management Authority – represented by chair Randy Pelt
    5. Project Advocate (smile): Mary Dunker
  2. Scheduling future meetings.
    1. Majority preferred one hour meetings every other week.
    2. Thursday's if possible but not between 2:30-3:30 or even 4:00pm.
  3. Review the Soft PDC project initiation form.
    1. How are Soft PDC's different from the CNS wireless PDC?
      1. Wireless PDC is for the wireless network only. CNS has no desire to operate their own certificate authority.
      2. The Level Of Assurance (LOA) for the soft PDC is higher.
      3. The soft PDC could be used for encryption of e-mail and files.
      4. The soft PDC would have wider availability and could be used by students.
      5. There is no funding for wide distribution of eToken's, e.g., to students.
      6. There are no plans to discontinue support for eToken's.
    2. A potential problem is keeping track of multiple PDC's. For example, wireless PDC, eToken, multiple soft PDC's.
    3. It was suggested that we consider a project goal of reducing the number of PDC's to 1 or 2.
    4. Note: under "Organizational Involvement" the reference to "Student Services" is the "Student Network Services" department of CNS.
    5. When we get to the collect requirements stage of the project, past experience show that identifying potential end users and meeting with them to determine their needs and requirements would boost project success. It would also provide an immediate use for the Soft PDC.
  4. Review project level indicators and complete the project scorecard.
    1. As a team we "scored" this project at 293.25 making it a medium complexity and risk project.
  5. Begin Scope development
    1. Review these Background Questions.
      1. Refer to the Background Questions page for specific responses.

For our next meeting Greg will review all the "Background Questions" and attempt to group similar questions. Also an attempt will be made to prioritize the questions.

  • No labels