# Pilot Design and Development ToR ## Project objectives ### Scope (work-in-progress) > Beneficiary x Challenges * Approach potential beneficiary/ies to formally introduce FabLabSG and show them how we can aide and contribute to their cause. * Produce free samples that they can benefit/use immediately. * Introduce the 'Challenge' concept that we will be adopting to introduce Inclusivity to the Makers Community and how they can include Inclusivity in their design approach. * Agreed on roles, timeline and responsibility for first Pilot Chalenge * Identify Benefeciary-Contact-Person(BCP) as main contact person for the Challenge/s. * Work with BCP to identify and document the details of possible Challenges, listing all pain-points, must-haves and good-to-haves that each solutions need to consider. > Makers Community x Challenges * Engage possible Makers Community for the first Pilot Challenge detailing how we are using the Challenges and inclusivity to motivate the Makers * Identify Makers-Contact-Person(MCP) for each community. ### Deliverables (work-in-progress) * Identify the Challenge/s that will be used for the Pilot Challenge. * Identify main contact person/s from the Beneficiery/ies and Makers Community for the Pilot Challenge * Produce detail timelines for the Pilot Challenge * Collaterals for Pilot Challenge * Identify various roles needed for the Pilot Challenge. ## Project roles and responsibilities (work-in-progress) > Describe the roles and reponsibilities of the people involved in the project. * Beneficiary Liaison: Zann H, others Establishes and maintains communication with our Beneficieries for mutual understanding and cooperation for the Pilot Challenge. * Makers Community Liaison: ?? Establishes and maintains communication with the Makers Community for mutual understanding and cooperation for the Pilot Challenge. * Pilot Challenge Producer: ?? Runs the Pilot Challenge. , Keeping track of timline, resources and deliverables. ## Resources, financial and quality plan (work-in-progress) > 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.