# A short project coordinator guide ## Scoping - defining your project A project - by definition - is ... > a temporary effort with a specific start and end date, designed to create a unique outcome. > > ([source](https://monday.com/blog/project-management/what-is-a-project/)) It's important to **define what your project is about and what it isn't** - the process of finding this out is called **scoping.** Partially, this can also be part of the project itself, e.g. finding out technical solutions or defining problems more clearly. But as a project coordinator, you should ... * ... set rough time boundaries on the project before the project start (expected end of the project) * ... define project areas - what should be worked on in the project (data collection? data visualization?) * ... identify some initial tasks and team roles * ... clearly identify the logic of problem -> solution -> impact To discuss this with the NPO, you can use parts of this [Mural template](https://app.mural.co/template/d5ee45d0-3770-49d1-b52a-639e17a80032/cae03a5a-15e5-46b2-b61d-ad41436e1b53) (German only) that you deem helpful. We can set a Mural from this template up for you. After you have discussed the scope and content of the project, it's a good idea to **write this down** in a project description. For this, we have the Google Docs *project home* template ([German](https://docs.google.com/document/d/1g_XQfCOoHlN_fWDvAjNhNcvMKkWkyNtaUgnF-E9CMqc/edit?tab=t.0#heading=h.rzf18ep3hwyb), [English](https://docs.google.com/document/d/1bJcn-bkn_GnJSeMhR7UrqJ1VjILaB25MhSXGshhwLO4/edit?tab=t.a9ayehn0m4h9)). You can make your own copy and fill in the parts that are relevant for you. ### Ethical concerns? If you have any ethical concerns regarding your project (idea), the ethics committee is there to help. You can find more information about the processes and tools [here](/projects/the-ethics-questionnaire-and-its-companion-document.md). ## Team selection - finding volunteers *coming soon.* ## Onboarding & Kickoff Once you have found volunteers to work on your project, you need to get them ready for the project. Your team is ready to work if: * everyone joined the Slack channel * everyone has access to data (depends on the project, see Q\&A below) * you had a kickoff meeting * you have established some sort of project management and everyone has access to it * everyone has access to a tool to work on code (depends on project, GitHub for code projects) * everyone has read and signed the *data protection and confidentiality agreement* if necessary #### :question:Do volunteers need to sign anything before they start the project? It depends: * if you are not working with a partner organization and are solely working with open data, then you are good to go. * if you are working with data of a NPO, volunteers should sign the "Data protection and confidentiality agreement" ([English](https://docs.google.com/document/d/1Ety-E1DbzWINkWQzh3pLYi-5OvAPD0MyNsCrrqSz1cg/edit?tab=t.0#heading=h.7se8ozrlx85b), [German](https://docs.google.com/document/d/1xhjPDWl07_48KmDuIGuiWL3Beyo9EpwUrBTzqNYiiPI/edit?tab=t.0#heading=h.7se8ozrlx85b)). Please ask in #core-general for support with set up of this document and the process. #### :question:Can I open a Slack channel? yes, please do. Please invite @Leo Preu so that he can keep track of the project for the purposes of our internal reporting. #### :question:How do I invite new people to the CorrelAid Slack workspace? * use `/invite` in a slack channel, then select "invite someone new to join this workspace". #### :question:Where should we put the code? * best practice is to work in GitHub repositories * ask in #core-general for GitHub repositories to be opened in the CorrelAid organization. please specify if it should be public or private. #### :question:Where should we put the data? * GDPR relevant data (see [here](/projects/data-security-and-privacy.md)) must not be uploaded to GitHub or CorrelAid's Google Workspace. Ask in Slack #core-general for help with initial data transfer. * if you are working with GitHub, you can use `.gitignore` to avoid data being accidentally uploaded to GitHub (see this [folder](https://github.com/CorrelAid/r-project-template/tree/main/data) and the `.`[`gitignore`](https://github.com/CorrelAid/r-project-template/blob/main/.gitignore) in the same repo for an example). * if you are working with data that is freely available and openly licensed, it is fine to upload it to GitHub. Please add license information in the README. * if you have questions, ask in #core-general. #### :question:Where should I put meeting minutes etc.? * ideally, you should keep project documentation in a place where CorrelAid (employees) have access to so that it won't be "lost" if you ever leave the organization. * Tools we have: * Google Drive/Google Docs in CorrelAid Google Workspace. Fill in this [form](https://docs.google.com/forms/d/e/1FAIpQLScJYiZDTlo0S4N7eeRVyo7GgSHFzdiaKvBt5RJ8C5Fo_22r0g/viewform) if you don't have an account yet. * if you need access to folders to store your project's content (e.g. local chapter folders, general CorrelAid folders), please ask in #core-general. * [Slack Canvas:](https://slack.com/help/articles/203950418-Use-a-canvas-in-Slack) Slack's channel canvas feature is quite useful for organizing links, project documentation and even meeting minutes. #### :question:How can we organize tasks / do project management? we can offer two solutions for task management: * [GitHub projects](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) * [Slack lists ](https://slack.com/help/articles/27452748828179-Use-lists-in-Slack) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.correlaid.org/projects/short-coordinator-guide.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.