1. TeraGrid Project Management Tim Cockerill Sr Project Manager NCSA April 6, 2009

2. Evolution of Project Management GIG and each RP had separate PM activities which were loosely coupled –Separate NSF research awards and project management Separate planning functions and reports, until PY3 started integrated annual reporting/review –TeraGrid starts adapting traditional project management methods so that they apply to these research awards GIG mainly project-based, RPs operations-based –Traditional project management methods suitable for projects – deliverables and end dates –Operations are ongoing support activities 2

3. Evolution of Project Management (2) PY4 IPP (Integrated Project Plan) –Result of last year’s review process –WBS too detailed to see forest for the trees –Program Plan too high level –Amalgamation of GIG plans and RP plans Established TeraGrid Project Management Area –Assigned Area Director –Formed Project Management Working Group – more tightly coupled project management Integrated GIG/RP planning process developed as evolution of GIG formalized project planning process 3

4. Evolution of Project Management (3) PY5 IPP is first plan developed utilizing the fully integrated GIG/RP planning process Now have more tightly coupled, fully integrated project management processes for –Planning –Tracking –Reporting –Managing Change 4

5. Planning Planning Process has dedicated session at 4pm today Integrated RP/GIG planning for PY5 –first integrated TeraGrid plan –4 month planning process Result of plan is the PY5 IPP which was submitted as part of this Annual Review Overview of PY5 Plan dedicated session at 1:30pm tomorrow 5

6. IPP Elements Description –Overview, Motivation, Plans –Background –Benefit to the TeraGrid Project and Community –Project Success Criteria –How TG-wide Collaboration will be Facilitated –Table of High-Level Project Deliverables Assumptions, Constraints, Risks Cross-Area Dependencies Budget and Staffing 6

7. Tracking Track progress against the IPP Sampling frequency 2x reporting frequency A Project Manager will query AD for status of deliverables A Project Manager will evaluate need for Change Management if scope/schedule/cost varies from original plan First formalized tracking exercise of IPP begins April, 2009 7

8. Reporting Develop and manage integrated RP/GIG reporting process Develop report templates Manage document flow - Sharepoint Quarterly and annual report preparation by ADs, TGF, and PM-WG –Quarterly: 4-week effort –Annual: 8-week effort –Annual Review: 2-week effort 8

9. Change Management Developed Change Management Process –On Main Page of TG Wiki http://www.teragridforum.org/mediawiki/images/1/1b/TG_Configu ration_Management_v1.doc Unique process – managing change across multiple NSF awards that contribute to a single collaborative project Individual awards with independent control Modified traditional change control process Process focuses on communication of change 9

10. Change Management Process Flow 10

11. END

12. 2008 Integrated PM-WG Activity July/August/ 2008 –PM Working Group is established by TG Forum/NSF –PM-WG Charter established September/October 2008 –PM-WG Members assigned by TG institutions –PM-WG kickoff meeting at ANL in early September –PM-WG establishes TG Integrated Planning Process –PM-WG begins PY5 Integrated Planning Process November/December 2008 –PY5 IPP (Integrated Project Plan) completed –Change Management process developed and documented http://www.teragridforum.org/mediawiki/images/1/1b/TG_Configuration_Management_v1.doc