---
# System prepended metadata

title: '**Project Process**'

---

# **Project Process**

## **Flowchart**
![](https://i.imgur.com/uAGCTHb.png)

## **Launch Checklist**

[Input form PM Request for Project Launch](https://alchemistcoin.typeform.com/to/aHvz53yW)

This request will create a master task in clickup (Project Launch List), provide the responses submitted by the PM through the form into the description and will automatically apply a template with different subtasks (and further subtasks) and dependencies.

There will also be another task created (Project X Master Doc) on another list (Master Doc). If you want to jump to this part of the process [please click here](https://hackmd.io/o1sbHWYaQCCr15PgPSIx2A#Master-Doc-Task-amp-List-Master-Doc.)


![](https://i.imgur.com/5K16Wvu.png)

### **Dependencies**

We use 4 main categories, but a lot of subtask for example of development are linked to other underlying subtasks of other categories. A great example is our medium article.

You can see the dependencies on the top by clicking onto the subtask:

![](https://i.imgur.com/M3XxXYd.png)

#### **Yellow dependencies**

Describes that this specific subtask can't be resolved unless the "yellow" subtask/task is completed. 
In this example: MVP (development), Documentation (development) and the Medium Article Review by PM (underlying subtask).

#### **Green dependencies**
Describes that this specific subtask was waiting on another subtask that is now approved or published.
In this example: No "waiting for" or yellow dependency was approved yet.

#### **Red dependencies**

Describes that this specific subtask is a blocker for other (sub)tasks.
In this example: Marketing (upper subtask) and the Discord Announcement (another marketing subtask)

#### **Blue dependencies**

Describes that this specific subtask is linked to other tasks, but it is not waiting for them. It is also not blocking the progress.
In this example: Design (main category), Instagram, Twitter and Reddit (all other marketing subtasks)

## **Statuses**

On every task and subtask on the project launch list we use 5 statuses, they portray the actual state of the task (or subtask). 

![](https://i.imgur.com/I52lMxW.png)

We define them like this:

#### **New**

A new task, untouched - "to do" to pick up and start working on it!

#### **Active**

In the status active, the main work will be done. It's like the hand sign to say - we start working on it or better: this task (or subtask) is work in progress.

Once the active work is finished and should be reviewed, we need to continue by changing the status to review.

#### **Review**

Each Task on status review should be signed off.
Most of the tasks are duty of the PM. 
Exception: The design category should be approved by marketing.

2 possibilities:

- Approval
    - Move task to next status: approved
- No Approval
    - Move task back to active and get into detail in the comments.

#### **Approved**

The first goal of every subtask should be to reach the status approved. Once every subtask reaches this stage, the "master task" will move automatically to approved. 

We are now ready to launch the project.

#### **Published**

Once we decide to launch, set up a plan (time coordination) and change each subtask if published to the status published.
Right after the final check (everything moved to public?) the master task can be moved to published.

Congratulations - we sucessfully launched a project and checked off every item on the launch checklist.

## **What has to be done**

#### **Assignments**

We currently do not have everyone that is a constant assignee in this process on clickup. 
Everyone who will accomplish regardless of the type of project tasks, should be assigned by the template.

Constant categories are Marketing, Design and Knowledge Base.

For testing: please assign manually subtasks.

On each launch it is most likely the PM will change. Therefore the PM should (right now) self assign all development tasks and every review by PM tasks. He should also be the approver in the most cases, she/he gives the final "go" by approvals (exception design subtask reviews).


#### **Comment section**

Every task and every subtask has a comment section. It should be used frequently by everyone. Share links of drafts, ressources, examples, critism and feedback. A documentation will help to identify and ultimately improve this and upcoming processes and executions. 

#### **Change status of a subtasks**

Every subtasks needs to be moved to the current state. If someone picks up a subtask she/he should change the status from "new" to "active". As described earlier, subtask ready to review - great - move the subtask to status "review". Most of the subtasks do have a underlying review by PM subtask (exception developement because the PM has to document these subtasks anyway). Once the PM get assigned to a review task, she/he should review the state and give an approval => the PM should now set her/his review subtask and the upper subtask to approved. 

Once every subtasks reaches the approved stage, the "master task" will automatically move to approved. Before going to the last status "published" we should coordinate together a schedule to publish every single item. Once everything is published, we can formally check off by change the status of the master class to published and therefore complete the launch checklist.

The time coordination will certainly be defined in more detail in the near future.

## **Master Doc Task & List Master Doc / Translations**

As described on the start there will be also another task created. This task is created on the list "Master Doc" and will be named like "Project X Master Doc".

This process is seprated from the launch checklist, because this list is also used for change requests for master docs of existing projects. 

For change requests we use another typeform as input: PM [Change Request for Master Doc](https://alchemistcoin.typeform.com/to/lAG3TSli) 

## **Statuses**

We do use the same statuses like on the launch project. [Click here to jump to them.](https://hackmd.io/o1sbHWYaQCCr15PgPSIx2A#Statuses)

## **What has to be done**

#### **Assignments**

We currently assign the master doc tasks to grt and Stew.
Their task is to prepare the master doc for the community site.

On each launch it is most likely the PM will change. Therefore the PM should (right now) self assign the review by PM subtask, she/he gives the final "go" by a approval.

#### **Comment section**

Every task and every subtask has a comment section. It should be used frequently by everyone. Share links of drafts, ressources, examples, critism and feedback. A documentation will help to identify and ultimately improve this and upcoming processes and executions. 

#### **Change status of a subtasks**

Every subtasks needs to be moved to the current state. If someone picks up a subtask she/he should change the status from "new" to "active". As described earlier, subtask ready to review - great - move the subtask to status "review". Once the PM get assigned to a review task, she/he should review the state and give an approval => the PM should now set her/his review subtask and the upper subtask to approved.

Once the master doc reaches the approved stage, the "master task" will automatically move to approved. Before going to the last status "published" we should coordinate together a schedule to publish every single item. Once everything is published, we can formally check off by change the status of the master class to published and therefore complete the launch knowledge base task or change request.

## **Translations**

Once the master doc is published we can give our translators the go to start their work. By changing the status to published a new task will be created on the 3rd list "translations" and will automatically apply a template with all translators as assignees of their own langague (currently already in use).

If all subtasks are resolved the status of the "change" will automatically be set to "complete".

## **Statuses**

We only use 2 statuses on the translation list, we do not need anymore.

#### **In progress**

Every created task by a project launch or by a change request will create a "to-do" task with the status "in progress".

Once every subtask is resolved, the "translation task" will automatically move to status "complete".

### **What has to be done**

{%youtube vmfUEIvqLvs %}

Head over to the in progress task and click on it. Read the description to know what to do. Go to subtasks and search for your subtask (your langague) and click on it. Write a comment, create a checklist, whatever you want - it is your subtask. On the top left corner hit the mark if you are finished.

























