> For the complete documentation index, see [llms.txt](https://open-data-charter.gitbook.io/open-up-guide-for-the-care-sector/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-data-charter.gitbook.io/open-up-guide-for-the-care-sector/implementation-milestones/project-kickoff.md).
# Project Kickoff
In this first stage we have the following milestones:
1. [Formation of the implementation](/open-up-guide-for-the-care-sector/implementation-milestones/project-kickoff.md#the-implementation-team) team
2. [Initial approach and scope definition ](/open-up-guide-for-the-care-sector/implementation-milestones/project-kickoff.md#defining-the-project-scope)
## The implementation team
The implementing team is responsible for carrying out the various steps necessary to bring the Indicator System to a province, state or department, or a municipality. It is recommended that the team consists of the following profiles:
* An institutional actor from the public sector who can implement the Guide and the building of the Indicators System. This person will be the promoter of the CIS within the public sector.
* An operational team that can adapt the indicators suggested by the Guide to the data, the public sources and the specific needs of the locality. At this point, it is recommended to analyse the legal framework of the context in which it will be implemented. This team will be integrated by people who can do desk research and validation through interviews or focus groups with relevant actors.
* A data team. This team will be responsible for identifying the databases needed to build the CIS, as well as processing the datasets for use by institutional actors or decision-makers.
## Defining the project scope
During this stage, the working team is formed and a joint review of the list of indicators included in the Open Up Guide is recommended. In this activity, the working team reviews each of the indicators, and makes initial comments on whether or not each indicator is replicable within the local context, and how it would be replicable or what adaptations to the descriptions would be necessary to comply with them. During this stage, a first possible identification of the sources of the data sets is also made.
Activities and objectives of the initial reconnaissance stage
The expected outcome of this stage is to have a first list of indicators that will make up the System, and to make an initial exploration of which data sets are immediately available to start with, as well as those that would be desirable to have. During the following stages, specialists in the different areas of care will guide us towards the missing data, or give us feedback on the relevance of the chosen data.
At this stage, the team will also have to decide which of the indicators in the guide are priorities for implementation according to the local context.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://open-data-charter.gitbook.io/open-up-guide-for-the-care-sector/implementation-milestones/project-kickoff.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.