Added by Gregory Koester, last edited by Gregory Koester on Apr 01, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

A Project Charter is the document issued by management that formally authorizes the work of the project to begin (or continue) and gives the project manager authority to manage the project.

1 Project Overview

1.1 Name 2008 Virtual Symposium on Pandemic Influenza Preparedness
1.2 Sponsorship Ann Marie Kimball, Director, APEC EINet, UW
Louis Fox, Associate Vice President, Learning and Scholarly Technologies, UW
Jacqueline Brown, Assistant Vice President, Information Technology Partnerships, UW
1.3 Project Managers Yuzo Arima (yuzoa@u), APEC EINet, for Health and Business tasks
Greg Koester (koester@u), Learning Scholarly Technologies, PM for Technical tasks at UW
1.4 Email Address / Website Apeceinetworkgroup@u.washington.edu
https://wiki.cac.washington.edu/display/vidconf/Home
http://depts.washington.edu/einet/symposium.html
1.5 Problem Statement There is a lack of communication between the worlds of business and health with regards to pandemic preparedness.
1.6 Description / Background (optional) In a narrative, describe project context and background.
What is the business need that gave rise to this project? Describe the business drivers that created the problem, opportunity or business requirement. Examples: regulatory issues, outdated technology or technological advance, customer request.
1.7 Objectives The overall aim of this videoconference is to promote regional information sharing and collaboration to enhance preparedness against pandemic influenza. In order to improve preparedness regionally, it is vital to understand how each economy in the region is undertaking preparedness. Specifically, EINet's proposed aims are to:
1. Bring together economies in a dynamic, real-time discussion on preparedness through the collaboration of the health and the business/trade sectors, with a focus on critical systems continuity.
2. Share specific examples of current practices---e.g. scenario exercises, communication drills and policy evaluation.
3. Use innovative technologies (e.g. Access Grid) for real-time, virtual interchange, enhancing their utility for future collaboration and response in time of a pandemic.
1.8 Scope Cannot be defined until December 10, Singapore Steering Committee Meeting.
1.9 Start Date/ Completion Date Virtual Symposium Date: May 29/30, 2008

October 2007 - April/May 2008

12/10/2007 Steering Committee Meeting

Local Holidays
April: exclude 4/4, 4/7, 4/9, 4/14, 4/15, 4/25, 4/29, 4/30
May: exclude 5/1-5/6, 5/9, 5/12, 5/19-5/22, 5/26

Jacqueline Brown availability:
  • Jan: out 1/7-1/11; 1/13-1/16; 1/20-1/26 (APAN); 2/9-2/13
  • Feb: out 2/9-2/13
  • Apr: out 4/5-4/12; 4/21-4/24 (Internet 2); 5/5-5/10; 5/16-5/23

    Considering above holidays and JB schedule, open dates are: 4/1-4/3; 4/16-4/18; 4/28; 5/13-5/15; 5/27-5/30
1.10 Time Reporting Possible team specific reporting but not project wide
1.11 Oversight / Reviews Planned Indicate what reviews this project plans: AIT, SIT, CSRB, cac-services, other. Charter, design, and production readiness reviews are recommended.

2 Project Resources

2.1 Project Team
  • Debbie Johnson, Logistics Coordinator (LST), debbiewj@u
  • Ari Tencate, Technology Specialist (Video Conference), tencate@u
  • Arshya Chopra, Technology Coordinator, arshya@u
  • Emi Mizuki, Logistics Coordinator (APEC EINet), emizuki@u
  • Eun-Suk Yang, Business Coordinator (APEC EINet), euny@u
  • Karalee Woody, Technology Director, karalee@u
  • Matthew French, to be determined, hmfrench@u
  • Nedra Pautler, to be determined, pautler@u
  • Sherry Edwards, Business Coordinator (LST), sherrye@u
2.2 Cost Estimate For Major Projects: State the rough cost estimate for the project, both for development and on-going support costs. Note: Start with a rough estimate, but as the project moves through each phase of the lifecycle, this estimate will become more detailed and may be very different than your original.
2.3 Customer Involvement
  • Members of Steering Committee
  • Participants in Symposium

3 Assumptions, Constraints, and Dependencies

3.1 Assumptions What are the assumptions being made?  Use true statements but ones that contain a measure of risk.
3.2 Constraints Describe any constraints on this project that will effect budget, quality, schedule, resources or scope.
3.3 Dependencies
  • APEC Grant for follow up to 2006 symposium

4 Deliverables, Expected Outcomes


4.1 Key Deliverables List what the project team needs to create to meet the project objectives.
4.2 Communication Plan For all correspondence with Steering Committee, c.c. Debbie (debbiewj@u)
4.3 Success Criteria How will we know when the project is done? How will the customer decide if the final deliverable is satisfactory? What measure will be used?

5 Approvals

For Major Projects: This agreement may only be modified with agreement from both the customer and sponsoring parties.