ASpace Sandbox API Project Charter

Directions: Copy and use this charter and related resources prior to a new project kickoff. Some information may be filled in at the kickoff meeting. Additional HUIT resources and templates.

I. Problem/Value Statement

Problem Statement:

Business Value:

II. Vision and Approach

Describe the solution:

Deliverables/Work Products:   

Define how to measure “done”:

In Scope:

Out of Scope (for medium and large projects):

III. Stakeholders and Project Team

 

Glossary

Stakeholders

Who is sponsoring the work? Who is funding the work? Who will accept the work? What organizations, departments, or people will benefit from this work (for medium and large projects)? Link to /wiki/spaces/librarymeetings/overview where relevant.

StakeholderTitleParticipation
   
   
   

Project Team

Roles: Project Manager, Business Analyst, Quality Assurance Analyst, Architect, Software Engineer, Systems Engineer, UI Designer, Metadata Analyst, Subject Matter Expert

Team MemberRole(s)Affiliation
   
   
   
   

IV. Cost and Schedule

Define the resource commitment, project phases with their associated activities, deliverables and milestones. Include a plan for transitioning to a stabilization phase, if needed, and then operations and maintenance.

IV. Key tasks and outcomes

TasksOutcomesResponsible Parties
   

VI. Assumptions, Risks, and Constraints

Constraints:

  • Scope
  • Time
  • Cost

Assumptions:

  • Stakeholders have identified the appropriate subject matter experts to participate in the Working Group and who can accurately and completely define the business requirements for the project
  • Stakeholders will have made available the time required to participate in project activities and to complete tasks as requested
  • Project sponsor and other stakeholders are empowered to make the decision required for the project to be a success
  • Project sponsor will provide written approval to move forward with system development when requested as part of incremental/iterative system demonstrations

Dependencies:

Risks (description, plan, impact, owner):

DescriptionPlanImpactOwner
    
Update during course of project as needed.