1. Project Services and Status reports Project Leader:Penelope Constanta Stakeholders:CD Project and Activity Leaders Resources: Ruth, Pordes, Penelope Constanta, Amber Boehnlein, Eileen Berman, Marcia Teckenbrock

2. Project Status Report: Project Services2 7 June 2005 Project Services: Scope - Goal Project Services’ scope is to provide the means (database, interfaces, etc.) to those services and infrastructure that support Project organization, communication and planning in the Computing Division.  Project services is meant to hold information relevant to projects and activities in CD and also be integrated with the Effort reporting system.  Project services is meant to hold only general metadata about a project and/or activities and it does not replace any of the project management tools used by US CMS, BPM, QCD etc. Project Services aims to provide:  a central reference site to find information about CD projects: project leaders and definitions time lines and pointers to internal information project status and plans

3. Project Status Report: Project Services3 7 June 2005 Project Services: Data Proposed Mandatory data about a Project:  Project Name  Project Description  Project Leader(s): Projects are assigned to persons or line organization (Department, Group etc), so a Project Leader might not be a person.  Activity(s) that effort can be reported to (at least one) Activity Description Activity Leader(s)  Stakeholders  Other non-mandatory information such as Project type (on-going work, etc) to be defined.

4. Project Status Report: Project Services4 7 June 2005 Project Services: Deliverables Project Deliverables:  Database to contain all project related information: For project management For effort reporting  Web based user interface to manage the database Link in all the project status reports  Status reports now in DocDB. Need to work on Topics and links to projects databases. Reports etc.

5. Project Status Report: Project Services5 7 June 2005 Project Deliverables/Milestones Phase I Delivered: Pilot database (Access) containing:  All project activities as defined in Effort reporting system  Any matched information from old ProjectsDB Delivered: Pilot Web interface using ColdFusion (http://wwwserver2.fnal.gov/cfdocs/projectsdb/index.cfm)http://wwwserver2.fnal.gov/cfdocs/projectsdb/index.cfm  Allows viewing of project related information  Allows changing of: Responsible organization Stakeholders Project Leaders Project Start and End time Project Status Project Deliverables Project Description Issues Documentation URL Project web site

6. Project Status Report: Project Services6 7 June 2005 Project Services: Next steps Phase I Two parallel process: Project information update  Project leaders need to review and update information about their projects  Start Time: Now, End Time: Now + 1 month Augment and enhance database tables to accommodate CD needs  Requires project leader input  Start Time: Now, End Time: Now + 2 months?

7. Project Status Report: Project Services7 7 June 2005 Project Services: Effort Profile (i) Phase I – Effort for current pilot:  Design: 4 people, less than 0.25 FTE in a month  Development: 2 people, for 0.2 (Penelope) and 0.4 (Nadya) FTE in a month Phase I Required for Data update: ? people for less 5% of a month  Required: Attention and commitment from all the stakeholders. I.e. department heads and activity leads.

8. Project Status Report: Project Services8 7 June 2005 Project Services: Phase II Rework user interface using CodeCharge  Interface needs to provide forms for data input that will be used for both Project Services and Effort Reporting system Start Time: 6/15/05, End Time: 12/15/05, FTE:0.20 Augment database tables  Modify tables (add fields, new tables etc) according to project leaders’ input Start Time: 7/18/05, End Time: 10/15/05, FTE:0.10

9. Project Status Report: Project Services9 7 June 2005 Project Services: Effort Profile (ii) To finish Phase II required:  Design: 4 people, ~5% each for 6 months  Development: 2 people, for ~10% and ~40% for 6 months Penelope + Marcia or we need help from EIU. Marcia other assignments are:  Docdb ~10% with some picks  OSG and plone ~40%  Hepap/hepic ~10% Phase III: just an acknowledgement…

10. Project Status Report: Project Services10 7 June 2005 Risks CodeCharge: New development software learning curve Untimely or unreasonable Project leaders’ input requests

11. Project Status Report: Project Services11 7 June 2005 Project Services: Phase III Import database to Oracle and integrate with EIU project  No schedule at this point … too far into the future