This extends ‣

Use for all active projects. The idea is to have a better and more organized place for active projects, but also to prove them out and not miss things as we release.

• In the context of Chingu this may be an initial MVP or sprint, but not little one-or-two-day small-team things. That stuff doesn't need elaborate treatment, but should still be agreed upon and discussed.
• This shouldn't be all-encompassing: Don't cover the entire voyage's project scope/vision. That's too much for this template. That is oftentimes referred to as the application, rather than simply a project.

Use comments on this document!

<aside> 🦉 This is a blame-free zone.

When you have an idea, use this template! No matter how weird or off roadmap. Don't get particularly far down the steps beyond very basics at first.

</aside>

Stage 1: Description and Justification

One Sentence Description: If at all possible, this should be framed as a problem statement in question form.

What do we need to make a shift management app MVP?

• The DShift initial MVP focuses on the core features of the project idea — Managing shifts — by narrowing the scope down to one manager per company link.

• [x] Feedback Round Is the scope of this agreeable? Have we reached agreement that this project is of sound team value? How does it deliver that? Is it good for each developer?

Stage 2: Design

The best features start with design and UX. This is where the project will come to life! This is where we'll flesh out what the feature looks like and how people will find it and use it. This will help in defining what needs to be developed and help everyone understand exactly what we're building.

Describe the functional design.

Explain what the feature will do and how users will interact with it. For example: "a button in a page that opens up a "results" form"