---
# System prepended metadata

title: Starting a new project

---

# Starting a new project
## 1. Discovery
> Resulting artifacts: Product definition documentation + Refined and prioritized features

Explain: 
- What are we talking about (short explanation of the product / app - what it is and what it is not)
- Planned release date
- Who are our target users & how can we help them? (End user / Business / Partners / Tech)
- Relevant use cases
- Expected deliverables (apk, aar, git repo, prototype, documentation?)

Check more on Discovery phase [here](https://dandypeople.com/blog/product-discovery-process-framework-and-tools/) and more on Design Sprint [here](https://www.thesprintbook.com/the-design-sprint).
Check more on backlog prioritization [here](https://www.productplan.com/learn/prioritize-product-backlog/).

## 2. Design
> Resulting artifacts: Design prototype
- Either go for a simple low-fidelity or a high-fidelity prototype. The important thing is to have at least an idea of what has to be build and how it should look (to allow planning and better measurement of how long it'll take to be build). If possible including details such as colors to be used.

You can read more on prototyping [here](https://blog.adobe.com/en/publish/2017/11/29/prototyping-difference-low-fidelity-high-fidelity-prototypes-use).

## 3. Kick-off meeting
> Resulting artifacts: Project Team agreements, first sprint planning

Note: Provide the developers with the artifacts produced in the Discovery and Design phase in advance. This documentation should be read beforehand and discussed in the kick-off meeting to clarify questions from stakeholders.

- Define:
  * Project timeline overview (including not only the release date, but also deadlines for other milestones, such as an alpha/beta version).
  * Roles and responsibilities.
  * Central source of truth: A person (normally the PO) that'll define the priority of features, who has the power to add new features to the backlog, and has the final approval on how the app should behave or look.
  * Team agreements. For example:
    * Only work at a max of 3 stories at the time (WIP)
    * All changes to the Blacklog / Sprint must be approved by the PO
    * Every story must contain an acceptance criteria
    * Update Jira board everyday at the end of the day
    * Track connect Jira cards to MR/PRs

- Plan: 
Based on the artifacts produced so far, plan the first sprint.