# Internal Checklist * **Team setup**: Set up a meeting with the tech lead. Ensure s/he understands the customer's business, deliverables, and milestones. * **Slack**: Create slack channels. Send invites to all team members to both channels. Invite the customer to the external channel. * **JIRA**: Setup permissions, groups, workflows, and [swimlanes](broken://pages/-MVVGPaX_mvbf8YfitG9). Invite customer(s) and project members to the project (always set up a classic JIRA project). * **Github**: Create new repo(s) on Github and a team group. Grant access to all members of the team. * **Figma**: Provision a new Figma project. * **CI & CD**: We have template projects for all the frameworks we have expertise in. Ask the tech lead to use these as templates and set up Github actions for CI & CD. * **Meetings**: Setup standups, sprint planning sessions, demos, and retrospective meetings. * **Product Backlog**: Write user stories and build a product backlog. * **Estimation Criteria**: Set up time with the team and explain the ticket estimation criteria and the point system. * **Wikis**: Maintain a wiki either on Notion or on Confluence. --- # 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://playbook.wednesday.is/project-management-playbook/general-guidelines/checklists/internal-checklist.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.