---
# System prepended metadata

title: MIPxx - Work Proposal (WP) Framework
tags: [Capital Management Improvement MIP Set]

---

---
tags: Capital Management Improvement MIP Set
title: MIPxx - Work Proposal (WP) Framework

---

# MIPxx - Work Proposal Framework

# Sentence Summary
The Work Proposal Framework enables a clear pathway for decentralized workforce teams to coordinate with Maker Governance when requesting funds from the protocol.

# Paragraph Summary
The Work Proposal Framework is a request for funds mechanism for a decentralized workforce to coordinate around opportunities to deliver work in exchange for funding from MakerDAO. The Framework defines the overall process, templates, and best practices for increased MIP usability. The framework can be viewed as an evolution of both MIP40 and MIP55, with more mature operations and engagement points for Governance and the workforce. 

# Component Summary
**MIPxxc1: The Work Proposal Framework** describes the overall process to request and receive work assignments and funding from MakerDAO. 

**MIPxxc2: Adding a Work Proposal** describes the requirements a work proposal must include to be considered eligible for a Governance vote. 

**MIPxxc3: Standard Work Proposal Configurations** describes standard, best practice conditions certain sections of the Work Proposal available to workforce teams to utilize. 

**MIPxxc4: Governance Cycle** defines how the Work Proposal framework integrates with Maker's Governance Cycle. 

**MIPxxc5: Work Proposal Tracking** defines how Governance must track and archive Work Proposals data.

# Motivation
The Work Proposal Framework is a response to the challenges and frustrations observed with the current funding and coordination mechanisms available to Governance and the decentralized workforce. This framework is created to enhance the alignment of the workforce to the desires of Governance, by clearly defining how funding expectations related to producing deliverables and value. This is accomplished by creating a dynamic but efficient process to communicate a workforce team's ability to deliver, approach to delivery, work-related use of funds, and consistent reporting requirements to unlock insight into the work. 

This MIP does not impact any current approved budgets at MakerDAO and utilization for current or future budgets is optional. It is being introduced as an available tool for the DAO to use as desired.

# Specifications 
## MIPxxc1: The Work Proposal Framework Overview
The Work Proposal Framework is initiated through the submission of a Work Proposal to Maker Governance. The Work Proposal is available for any individual or team to submit to Governance for approval as long as it meets the requirements defined in MIPxxc2. The Work Proposal Framework is dependent on the DAO-level Objective Framework (MIPxx), and requires a DLO to first define available opportunities for the team to submit work proposals against. 

This framework does not restrict the definition of workforce teams - meaning this is available to Core Units, vendors, businesses, or any group of contributors that organize around an opportunity. It should be noted that assessment of the work proposal's team is taken into consideration, so a DLO can restrict what teams or entities are eligible for Work Proposal submissions. 

This framework aims to reduce governance overhead and ease the proposal writing process by documenting best practices for consistent application in a Work Proposals. To accomplish this, best practices are named and defined in MIPxxc3. Bespoke configurations of Work Proposals may be needed for some sections to bring innovation to the delivery of a project, however other sections of the proposal are better suited for default configurations (such as Budget Implementations). Governance should amend this MIP with updated best practices as they are discovered to encourage the maturity of the Framework. 

A Work Proposal is subject to Maker Governance approval. MIPxxc4 defines the Governance cycle defined for Work Proposals. 

Once a Work Proposal is approved, a MIP editor must update MIPxxc5 for both the tracking of active teams contributing to MakerDAO, the objectives they're working on, and retrospective archival purposes. 

## MIPxxc2: Adding a Work Proposal
A Work Proposal is a proposal or application, made by a team, to complete deliverables related to a specific DAO-level Objective (MIPxx). Work Proposals use a bottom-up approach enabling workforce teams to practice autonomy while defining their unique approach and value-add for the project. If a DLO defines specific requirements for eligible Work Proposals, Governance Facilitators must block the proposal from entering any governance cycle until corrections have been made. 

A Work Proposal has the following required sections: 
**1. DLO Subproposal Number** - A DLO index number is assigned by a MIP editor once a DLO is approved. This defines the relationship between a Work Proposal and a DLO. 
**2. Workforce team Bio** - a description of the Workforce team. A section reserved to provide previous work examples related to the DLO, and demonstrate the team's abilities and unique attributes that position them to successfully deliver against the objective.
* The Workforce Team Bio must define a point of contact - or a team lead - and their contact information. This is to ensure clear lines of communication and to define a point of contact that interfaces with the DAO.

**3. Project Plan for Producing Deliverables** - A DLO will define the desired timeline for delivery. The project plan section requires a Workforce team to define how they will deliver against this timeline. 
**4. Milestones** - A DLO defines specific deliverables required to consider an objective as delivered. This section details how the deliverables will be defined as milestones for the project, and commitments to reporting on work to the DAO. 
**5. Forecasted Challenges that May Impact Deliverables or Timeline** - MakerDAO is an innovative project, with many challenges to navigate. The value expert-workforce participants bring to Maker is proactively navigating these challenges. This section is to detail challenges and describe how the team will address those challenges if non-ideal conditions arise, or to list strategies they will utilize to overcome them. 
**6. Budget Breakdown & Proposed Funding Milestones** - A DLO defines a Budget Cap for an objective. This Budget Cap may be shared among several teams, or directed towards an individual team. A DLO may also dictate how funding for a project is enabled (such as streaming, milestone based, or even defined incentives). A DLO may also leave the Budget distribution to be defined by the Work Proposal. This section allows for price competition to be an attribute of Work Proposal comparisons, if desired. This section must include the following subsections. 
* **Budget Breakdown** - An expense category level forecast for expenses related to the project.
* **Budget Distribution** - A description of how the Work Proposal budget request is to be transferred to the workforce team. 
* **Budget Implementation** - A technical-level implementation of how the protocol will transfer funds to the workforce team. 

A template for Work Proposals is provided here: https://hackmd.io/@0xRetro/BJjfjj75j

## MIPxxc3: Standard Work Proposal Configurations
!!!WIP!!!

### Project Plan 
* Template Tool
* Standard Project Plan Breakdown - Research, Proof of Concept, Beta-release, Production Release, Maintenance, Assessment & Continuous Improvement
* Project Management Methodologies - Epics, Agile, Waterfall

### Milestones
* Delivery Based
* Time Based
* Event Based
* SES Auditor Framework

### Forecasted Challenges
* Known Challenges
* Unique Decentralized Challenges
* Unique DeFi Challenges
* Unknowns 

### Budget Breakdown 
* SES Auditor Framework Compliant Breakdown
* Simple Breakdown 

### Budget Distribution 
* Maintenance Stream 
* Continuous Stream
* Milestone Based 
* Incentive Based
* Performance Based

### Budget Implementation 
* DssVest
* Manual Implementation 

## MIPxxc4: Governance Cycle
Work Proposal Submissions follow the below the below governance cadence: 
* RFC Period: 2 week minimum 
* Formal Submission: Anytime after the RFC period has passed
* Frozen Period: 2 weeks
* On-chain vote: 1 week

The voting parameters for a DLO on-chain vote are: 
* Abstain
* Approve
* Reject

## MIPxxc5: Work Proposal Tracking
This subcomponent for the Work Proposal Framework is reserved for tracking the status of Approved Work Proposals and key details for delivery. A MIP editor must update this MIP following an on-chain vote with an Approve outcome. A sample entry is provided below: 

```
MIPxxc2-SPxx - Work related to DLO #
Status: Active/Delivered/Closed
Forum Link: 
```

* Active defines a Work Proposal as accepted and currently worked on by a team.
* Delivered defines a Work Proposal as completed, but still pending a future milestone. This means that expenses related to the Work Proposal are not closed. 
* Closed defines a Work Proposal that has either been delivered, and all funds related to the proposal have been transferred. This could be because of a completion of a Work Proposal, or the early termination of a proposal. 

Work Proposal Tracking Entries: 