project-scope.md

{Project Title}

• Overview
  • Problem Statement
  • Objectives
  • Background
• User Stories
  • {User Persona 1}
  • {User Persona 2}
• Feasibility Assessment
  • Feasibility Criteria
  • Practicality Criteria
• Deliverable Specifications
  • {Deliverable or Phase 1}
  • {Deliverable or Phase 2}
• Team and Timeline
  • Roles and Responsibilities
  • Project Roadmap

Overview

Problem Statement

{1-2 sentences of concise context which frame the problem}

{1 sentence description of how this project should address that problem}

Objectives

• {Brief description of expected outcome}
• {Brief description of expected outcome}
• ...

Background

User Stories

{User Persona 1}

{2-3 sentences describing a person who represents a group of users. It often helps to model this after a real person}

User Needs

• As a {User Persona 1}, I want to {description of task this User Persona wants to perform}, so that {outcome that this User Persona desires}
• As a {User Persona 1}, I want to {description of task this User Persona wants to perform}, so that {outcome that this User Persona desires}
• ...

{User Persona 2}

{2-3 sentences describing a person who represents a group of users. It often helps to model this after a real person}

User Needs

• As a {User Persona 2}, I want to {description of task this User Persona wants to perform}, so that {outcome that this User Persona desires}
• As a {User Persona 2}, I want to {description of task this User Persona wants to perform}, so that {outcome that this User Persona desires}
• ...

Feasibility Assessment

Feasibility Criteria

In order for this project to be feasible the following conditions must be met:

• {Brief description of project dependency to validate}
• {Brief description of project dependency to validate}

Practicality Criteria

f the project is feasible, the following conditions must also be met in order for it to be worth pursuing:

• {Brief description of assumption about project outcome to validate}
• {Brief description of assumption about project outcome to validate}

Deliverable Specifications

{Deliverable or Phase 1}

• Definition of Done
• Dependencies or Constraints
• Does not Include

{Deliverable or Phase 2}

• Definition of Done
• Dependencies or Constraints
• Does Not Include

Team and Timeline

Roles and Responsibilities

The following division of responsibilities borrows the MOCHA framework from the Management Center.

• Manager: {Manager's Name}
• Owner: {Owner's Name}
• Consulted
  • {Consulted Name}: {3-5 word description of their area of input}
  • {Consulted Name}: {3-5 word description of their area of input}
  • ...
• Helpers
  • {Helper's Name}: {3-5 word description of their contribution}
  • {Helper's Name}: {3-5 word description of their contribution}
  • ...
• Approvers
  • {Approver's Name}: {3-5 word description of what they have approval on}
  • {Approver's Name}: {3-5 word description of what they have approval on}
  • ...

Project Roadmap

• {Phase 1}
  • {Description of Phase 1 milestone}
  • {Description of Phase 1 milestone}
• {Phase 2}
  • {Description of Phase 2 milestone}
  • {Description of Phase 2 milestone}