Skip to content

Latest commit

 

History

History
170 lines (102 loc) · 7.74 KB

File metadata and controls

170 lines (102 loc) · 7.74 KB
description
Also known as your research plan template

Project Brief Template

{% hint style="info" %} Notes to reader: To use this document... 1.) copy. 2.)remove this section before use. 3.)You are welcome to remove project brief sections to fit your use case {% endhint %}

Project Title

Date: xxxxx, xxth, xxxx

Version: review

Prepared by: ________

The Problem

Background

Setting the stage for the project (may include any previous project/research that led to this project, related projects, etc. This is the section where you can describe what causes the problem, how often it occurs, where and when it occurs, and who the problem impacts.

Problem statement

A problem statement is a clear and concise description of the problem or issue a team aims to address in a project. It identifies a problem’s current state, desired future state, and the gaps that lie between the two.

It doesn't define the solution to the problem or provide a road map for solving the problem; it only gives an outline of what the problem is.

However, the team can later use the problem statement to validate that their work delivered an outcome that resulted in the solution.

Assumptions

They’re called assumptions because you assume that for your project to move forward successfully as planned, these things will be in place. Even though you don’t have proof at the moment, you expect them to occur during the project. But just because you assume them to be true doesn’t mean that everyone else does. That’s why it’s important to go through the process of identifying your project assumptions.\

Business needs and goals

business needs and goals are gaps between the current state of a business and its goals. Needs are the basic drivers of change in an organization that are identified as requirments.

The Audience

Your target audience is the reason you’re working on this project. No matter what type of project you’re working on, it’s important to include your target audience in your project brief so everyone on your team is on the same page about who the audience is.

Primary Secondary

Measuring Success

Project outcomes and the definition of success are the assets and deliverables you plan to deliver at the end of your project. This will define your success metrics, which helps you evaluate the success of your project once you finish it.

Project Outcome

A project goal refers to`` the desired outcome of a project

Definition of Success

Project success can be defined as the achievement of something desired, planned or attempted

Due Date

  • Completed by _____

The Scope

Your project scope statement will act as the primary tool for stakeholders and teammates to refer back to and use as a guideline to accurately measure project success.


Timeline and approach

Months June July August Sept. Oct. Nov. Dec. Jan. Notes


<what will you be doing?/>

<what will you be doing?/>


<what will you be doing?/>

<what will you be doing?/>

Risks

what are some of the risks that would disrupt the project

Opportunities

Clearly state all the opportunities you see that would help make the project successful.

Deliverables

At the end of this project what are your deliverables.

Team

{% hint style="info" %} option 1 to share who will be doing what, is to use the RACI {% endhint %}

To be completed by

Name Role Capacity Estimate

To help support by providing knowledge of past/current experience

Name Role Capacity Estimate

To be informed: be available for questions and updates in order for the team to move the project toward completion.

Name Role Capacity Estimate

The requestor: be available for questions and updates in order for the team to move the project toward completion.

Name Role Capacity Estimate


RACI: roles and responsibilities

{% hint style="info" %} Option 2 to share who will be doing what, is to use the RACI {% endhint %}

Names Insert process Insert process


RACI Key

Responsible (R)

  • This is someone who is responsible for getting the work done
  • This person is expected to be hands-on when executing the task
Accountable (A)
  • This is the person who is responsible for overseeing the task and making sure the work gets done properly
  • They are not hands-on with the work, but instead, they are managing and ensuring the completion of the work

Informed (I)
  • This person or group of people is to be kept up to date on the progress of a task or deliverable
  • This is commonly upper-management or a client who should understand the progress of the project but does not have immediate input on the completion of the work
Consulted (C)
  • This person assists by providing information and support about a particular task or deliverable
  • They are not directly responsible for a task, but instead, they provide necessary information that will help the R get their work done

Ideas and Notes

Notes you captured to help guide the work.

Other information

add helpful links or information here to help guide your research.

Question

{% hint style="info" %} what questions do you have? {% endhint %}

Useful links