kikobar/fablab-docs
1
0
Fork 0
mirror of https://github.com/fablabsg/fablab-docs.git synced 2024-09-28 13:57:14 +00:00
Code Issues Actions Packages Projects Releases 2 Wiki Activity

Add ToRs for all the phases

Browse source
This commit is contained in:
Enrique Barcelli 2024-08-17 15:54:51 +08:00
parent 7cbd830880
commit e040531f45
Signed by: kikobar
GPG key ID: 006C13A68E25D3B7
7 changed files with 222 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
ConceptualisationToR.md
View file

@ -4,14 +4,36 @@
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

39
FinalDesignDevelopment.md Normal file
View file

@ -0,0 +1,39 @@
# Final Design and Development ToR
## Project objectives
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

39
Implementation.md Normal file
View file

@ -0,0 +1,39 @@
# Implementation and Stabilisation ToR
## Project objectives
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

39
PIR.md Normal file
View file

@ -0,0 +1,39 @@
# Post-Implementation Review ToR
## Project objectives
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

39
PilotDesignDevelopment.md Normal file
View file

@ -0,0 +1,39 @@
# Conceptualisation ToR
## Project objectives
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

39
PilotExecution.md Normal file
View file

@ -0,0 +1,39 @@
# Pilot Execution ToR
## Project objectives
### Scope
> List and describe the scope of the project.
### Deliverables
> List and describe the deliverables of the project.
## Project roles and responsibilities
> Describe the roles and reponsibilities of the people involved in the project.
## Resources, financial and quality plan
> Describe the resources needed and how they are going to be obtained, provided or paid for.
>
> This means man-hours of effort, infrastructure, etc. and their cost.
## Work breakdown structure and schedule
> Describe the project timeline and its main milestones.
>
> As this project is a phase of an overaching project, it should describe its own timeline and milestones within the context to the key milestones of the ovearching one.
>
> Each project phase will have its own ToR in a separate file.
## Key issues and risks
> Describe the main issues and risks of the project, ranking them on High, Medium or Low, and indicating their mitigation measures if available.
>
> This should be for the issues and risks identified at the time of the issuance of the ToR, because in reality we will track the issues and risks on the tracker.
## Assumptions and constrains
> List of any significant assumptions we have made at the time of preparing the ToR.

10
README.md
View file

@ -93,15 +93,15 @@ Such eco-system is made of several components:
- [Conceptualisation](ConceptualisationToR.md)
- Pilot Design and Development
- [Pilot Design and Development](PilotDesignDevelopment.md)
- Pilot Execution
- [Pilot Execution](PilotExecution.md)
- Final Design and Development
- [Final Design and Development](FinalDesignDevelopment.md)
- Implementation and Stabilisation
- [Implementation and Stabilisation](Implementation.md)
- Post-Implementation Review
- [Post-Implementation Review](PIR.md)
## Key issues and risks