DASH Development and Migration DSpace 8 Project

• Project Name
• Project Goals
• Problem and Value Statements
  • Problem Statement
  • Solution Business Value
  • Alignment with Harvard Library Multi-Year Goals and Objectives
  • Alignment with HUIT Objectives
• Vision
  • (Insert Vision table, as below)
  • Approach
• In Scope/Out of Scope
  • In Scope
  • Out of Scope
• Deliverables and Work Products
  • Key Tasks and Outcomes
• Definition of Done
• Stakeholders
• Project Team
• Cost and Estimated Schedule
• Assumptions, Constraints, Dependencies, and Risks
  • Project Assumptions
  • Project Constraints
  • Project Dependencies
  • Project Risks
• Acceptance

DASH Development and Migration to Hosted DSpace 8

Project Goals:

Invest in sustainable infrastructure and improvements to DASH's workflow, metadata, metrics, and preservation. This will allow Harvard Library to broaden DASH’s service adoption levels and support Harvard's research lifecycle, data repositories, digital asset management, and digital scholarship systems.

• Enhance DASH interoperability 

• Advance repository collaboration 

• Establish a sustainable infrastructure  

• Improve workflow, refine metadata, and diversify repository content 

Problem and Value Statements

Problem Statement

Solution Business Value

Alignment with Harvard Library Multi-Year Goals and Objectives

Alignment with HUIT Objectives

Vision

(Insert Vision table, as below)

Approach

In Scope/Out of Scope

In Scope

Out of Scope

Deliverables and Work Products

Key Tasks and Outcomes

Definition of Done

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? Link to related governance structure wiki page(s) where relevant.)

Project Team

(Roles include: Product Owner, Project Manager, Scrum Master, Business Analyst, Quality Assurance Analyst, Architect, Software Engineer, Systems Engineer, UI Designer, Metadata Analyst, Subject Matter Expert, Release Coordinator)

Cost and Estimated 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. This section may not be relevant for projects for which schedule/date-based information is not available at the time the charter is being written. In that case, be sure to document the schedule, milestones, and deliverable dates in other ways with stakeholders and be transparent about accomplishing them.)

Assumptions, Constraints, Dependencies, and Risks

Project 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

Project Constraints

• • Scope
  • Time
  • Cost

Project Dependencies

Project Risks

Acceptance

Accepted by <Project Sponsor Name>, <Date>

Prepared by <Project Manager Name>

Effective Date: <Date>