Purpose: This meeting was a follow up on the 31 Aug 2012 CSI Planning meeting
with CSI PMs to discuss CSI project management as an Intergroup Collaborative
project and to begin defining the Configuration Management process.
Date and Time: 10 Sep 2012; 1300-1430
Location: AIS PMO Office, 204 Sandy Drive
Participants: Rich Dumm, Barbara Howie, Shawn Smith
Discussion Points:
Where are we in the project?
Using the Central Person Registry Design Wiki page at
https://wikispaces.psu.edu/display/IAM/Central+Person+Registry+Design+Wiki,
Barbara pointed out that there is a great deal of useful information available, but
there is no way to determine if the information is the most recent, or if CPR or its
components are considered baselined for integration purposes or if they are still
under development. The page changes can be compared using the Wiki tool, but
there are no comments to determine the reason for the change. This information
may be in some other document, such as a Version Description Document (VDD) or
internal wiki. The source code is in version control using Subversion (SVN). Shawn
asked to be given access to any internal Wiki and SVN.
Technical Discovery – 2 weeks
In addition to internal Wiki and SVN access, Shawn plans to meet with 1 or 2
technical people at a time within the CSI Team for the purpose of technical
discovery. He asked that the project management team be involved. The technical
people on the team are defined at https://wikispaces.psu.edu/display/IAM/CSI++Project+Team and for the purpose of the technical discovery process are as
follows:
IAM
AIS
Sherry Kathy Brown
Ed
Technical Lead (tbd)
Jimmy
Emily
Jerome
Lynn
CSS
Bob Walters
Steve Moyer
Jason Gullickson
Scott Haas
Post meeting note per Rich: “The IAM team, under Technical Discovery, should
reflect only Jimmy, Ed, and Jerome. The others are not part of the CSI project and
they should be removed from the list in this document. They would not be part of
the interview and discovery process unless there is a specific need for them.”
Configuration Management
We do not know where the authoritative repository is and what the process is for
issue / change management. Version control is maintained using SVN, but we do
not know how CSI tracks changes. Shawn had Barbara launch AccuWork/AccuRev
to demonstrate how AIT is tracking changes to the software and linking them to the
code. This was for demonstration purposes only. Another tool may already be in
use, or there may be comparison required to determine what the best tool is for the
CSI project.
Project Planning and Management
There needs to be an integrated project plan for CSI. We need to create a hi- level,
integrated WBS for Ron, Ken, and Renee to present to Kevin. We also need a project
management plan that describes the integrated group roles and responsibilities,
resources, and defines the Software Development Lifecycle (SDLC).
ACTION ITEMS (dates are approximate)




Rich - Follow up on getting Shawn access to Internal Wiki and SVN.
19 Sep – Project Management Plan - Rich (template), Barb, Dawn
08 Oct - Group Technical Meeting to present Shawn’s findings and
recommended path forward – Shawn
Oct 14 -Hi-level, Integrated WBS for Kevin – includes projections based on
workforce – CSI Team