> For the complete documentation index, see [llms.txt](https://docs.urbanarray.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.urbanarray.org/roadmap/initial-phases/preliminary-planning-0.md).

# Preliminary Planning (0)

Phase 0 (December 2023- March 2024 )

In the Preliminary Planning Phase, we lay the groundwork for the relaunch of Urban Array. We assemble a core team of talented individuals with expertise in community development, project management, fundraising, marketing, and communications. Together, we define our vision, mission, and core values that will guide our activities and decisions. We establish clear goals and objectives, set up communication channels, and create a robust project management infrastructure. This phase is crucial for building a strong foundation for our relaunch.

### Assemble the Core Team:

* [x] Identify individuals with relevant skills and expertise in community development, project management, fundraising, marketing, and communications.
* [x] Recruit and onboard team members who align with the vision and mission of Urban Array.
* [ ] Define roles and responsibilities within the core team.

### Define Vision, Mission, and Values:

* [x] Conduct brainstorming sessions and discussions to establish a clear vision for Urban Array's relaunch.
* [x] Articulate a compelling mission statement that reflects the organization's purpose and goals.
* [x] Identify and define the core values that will guide the activities and decisions of Urban Array.

### Establish Goals and Objectives:

* [x]    Determine specific and measurable goals that align with the relaunch process.
* [x]    Break down goals into smaller, actionable objectives to track progress.
* [x]    Set realistic timelines and milestones for achieving each objective.

### Set up Communication Channels:

* [x]    Implement Slack as the primary communication platform for the core team.
* [ ]    Create channels and threads for different topics, projects, and teams.
* [ ]    Establish communication guidelines and best practices to ensure effective collaboration and information sharing.

### Create Project Management Infrastructure:

* [x]    Utilize Jira Work Management to set up a centralized project management system.
* [ ]    Define project boards, workflows, and tasks to manage the relaunch process.
* [ ]    Assign team members to specific tasks and track progress in Jira.
* [ ]    Regularly review and update project boards to ensure transparency and accountability.

### Create Knowledge Base(s):

* [x]    Develop a comprehensive public knowledge base using Gitbook.
* [x]    Develop a project focused knowledge base using Confluence.
* [ ]    Organize information into categories and sections for easy navigation.
* [ ]    Document key processes, guidelines, and best practices for reference.
* [ ]    Ensure the knowledge base is accessible to both the core team and the public.

<br>

<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.urbanarray.org/roadmap/initial-phases/preliminary-planning-0.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.