Managing Milestones

In Lumin, projects are required to define their roadmaps by specifying milestones and deliverables. In Lumin, milestone reporting is vital to communicate with the funders that the development of the project is continuing as promised. Funds will stream towards the project team as long as the Project owner provides Proof of Deliverable Completion reports and funders do not withdraw funds due to their dissatisfaction with the reports. Therefore, deliverable reporting is the main way to maintain the consent of funders and continue to receive optimistic funding approval.

In the proposal creation process, Proposal Owners will be asked to write a list of deliverables aimed to be completed under each milestone, the required milestone budget, and the duration for completing the work for each milestone.

• Milestones: refers to a significant event or achievement in the development process that marks progress towards the completion of a project

• Deliverables: refers to a smaller chunk of accomplishment to complete a milestone (ex; Milestone: Finishing the UI/UX of the Product -- Deliverable 1: Create low fidelity wireframes in Miro.) Project Owners need to upload documents for the completion of each deliverable under a milestone.

• Required Budget: refers to funding that the project team needs to achieve the completion of the milestone. This budget will drip in the timespan of the Estimated duration.

• Estimated duration: refers to the approximate duration for the completion of a milestone. The Milestone budget will be streamed in that period.

After defining milestones, Project Owners are expected to manage milestones (edit or add milestones if needed) and report milestone completion(to learn more about project owner responsibilities, refer: Project Owner Responsibilities.)

Reporting Milestones

In Lumin, to complete a milestone and start the stream of funding for the next one, Project Owners need to upload Proof of Deliverable Completion document for each deliverable in an ongoing milestone. These uploaded documents will be publicly displayed to communicate the project team's development process. Also, the reports will be open for feedback by the funders (to learn more: Becoming a Funder) so that the contributing team can always maintain alignment between the progress of their work and the funders' consent. Based on the feedback, project teams could re-upload their reports. Also, if project funders are not satisfied with Project Owners' Proof of Deliverable Completion documents, they can withdraw their committed funds.

The trigger of the stream of a new milestone after completing one by uploading Proof of Deliverable Completion reports will look like this:

• Imagine your project has a second milestone titled "Finishing up high fidelity UX mockups" with two deliverables, two months duration, and a 10,000 USDC budget.

• Over 2 months, 10,000 USDC will be streamed to the project's treasury address.

• Whenever you finish any of the deliverables, as the Project Owner, you upload a Proof of Deliverable Completion document for them.

• When you have uploaded the two Proof of Deliverable Completion documents and the 2-month duration for Milestone 2 has passed, then you will be able to complete the Milestone 2 and initiate Milestone 3.

• You conclude milestone 2 by making a transaction to complete a milestone, and you initiate funding for Milestone 3.

There is no reporting process required for Milestone 1, as it represents guaranteed payment for the project. This means that, regardless of any issues that may arise, the funding amount for Milestone 1 cannot be withdrawn by the funders. In order to initiate Milestone 1, two conditions must be met: first, the proposal pool needs to have sufficient funds to cover the budget for the milestone, and second, the Proposal Owner must trigger the stream.

To see the step-by-step guide for uploading Proof of Milestone Reports :

How to report a Milestone?

Editing Milestone

Project Owners can edit their project details, including milestones. However, Project Owners can only add and edit future milestones, not an already active ones. Each edit will introduce 3 day buffer period to allow funders to reevaluate changes.

The editing function is mostly needed in;

• Editing future milestones in the case of roadmap changes

  • For example, if a problem occurs in the project development, which will cause a delay in the completion of milestones, Proposal Owner would edit future milestones to ensure the roadmap compatibility with the development process.

  • For example, Proposal Owner may add a new milestone specific such as "Deploy in Celo Chain" because Celo requires your project team to deploy in the Celo chain to provide the grant.)

• Correcting a mistake at the creation of the Proposal

• Incorporating feedback from the funders

• Re-scoping of the budget and changes in the team

How to edit Milestone? (WIP)