# Getting Partners and Stakeholders on Board

To jump to the Project Initiation main page, click [here](https://openup.gitbook.io/handbook/projects/pre-project). 

Read this section and then use the **stakeholder checklist** and [**Project Overview Document**](https://docs.google.com/document/d/1xDjx5-Wfqbsi8WnyaOrEQd-r98a_p27Jjp6WQ4nj_zc/edit) to make sure you have all the information you need to start a project.

\*see [Stakeholder Managemen](https://openup.gitbook.io/handbook/projects/project-planning/stakeholder-management)t, Project Implementation.

## ENGAGING STAKEHOLDERS

The first stage of every project. Get to know: 

**WHO** 

* is involved
  * internally
  * externally

**HOW** 

* invested each partner and stakeholder is in the project's success
* they can potentially contribute

**WHAT** 

* respectively, is each partner and stakeholders' level of commitment to the project

  they want to contribute

  * Financially
  * To the labour process

### 1. What are the DESIRED GOALS & OUTCOMES for each stakeholder?

* What do they want out of the project? 

Use the goals and outcomes to create a concept note that explains how the project supports OpenUp's mission. 

[Concept note template.](https://docs.google.com/document/d/1K-mBZlabZYBi_LApktb7eYpmR1NCo7M8oroDechZfA8/edit) 

### 2. What are the RESOURCE CAPACITIES of each stakeholder?

Commitments should be made up front regarding how much **time** and **money** each stakeholder is able to provide. Project managers should keep each part accountable. Resources- grants, funding, manpower, etc.- should be factored into the project budget. 

For more on resource capacity, see [here.](https://openup.gitbook.io/handbook/projects/pre-project/defining-project-parameters-and-limitations) 

####

For more information, see Budgets and Finance. 

### 3.DEFINE THE ROLES of all parties involved. 

Defining and delegating roles- a step preceded by **getting to know the skill sets and limitations of the people on hand**- is a vital part of the early planning process. 

Delegating and defining roles clearly defined roles and communicating them to everyone is vital to a successful project. Knowing what people can and cannot do, will help you plan accordingly.

#### Common roles include:

* [Product Owner](https://openup.gitbook.io/handbook/project-planning/common-roles#product-owner) (See also: <https://www.scaledagileframework.com/product-owner/>)
* [Project Manager](https://openup.gitbook.io/handbook/project-planning/common-roles#project-manager)
* [Implementers ](https://openup.gitbook.io/handbook/project-planning/common-roles#lead-developer)(coders, designers, writers etc.)
* [Communications or Marketing](https://openup.gitbook.io/handbook/project-planning/common-roles#communications-and-marketing-lead)

###

####

###

##

Add the stakeholders details to **stakeholder database**.