sachamorgese / unnamed-project

1 stars 0 forks source link

Decide workflow #4

Closed sachamorgese closed 5 years ago

sachamorgese commented 5 years ago

What tools should we use? How should we proceed? Who's taking care of what? What do we want to learn? Let's discuss here

sachamorgese commented 5 years ago

I'd like to go with agile/scrum for this project:

1) It allows us to work independently. 2) It's an industry standard (in countries where people know what they're doing).

Since this is a side-project, we need some extra flexibility. All of the deadlines are going to be guidelines, nothing more than that. However, some issues have a higher priority and being unable to complete them in the appropriate time might slow down the others. Other people can take over, but we need to have good communication.

I'd like to go with 6 phases. First 2 phases code = false. Last 4, code = true.

Brainstorming < --- We talk and come up with ideas, decide MVP, Stack, and Workflow. NOW

Planning/Design < --- We expand on the previous phase, start writing documentation and create issues. UI, UX, API, testing etc.

Set Up (could be seen as Sprint 1?) < --- We set up everything we need to deliver the MVP. This includes all dependencies, wiring up React/Redux/Whatever we're going to use. Write unit testings here.

Sprints < --- We get into full coding, I propose 1-week sprints. Write unit testings here. Some integration testing as well, if possible.

Testing < --- We try to break the app and then fix it. Integration testing.

Release < --- Sell out, bro down!

What do you think?

sachamorgese commented 5 years ago

This issue was moved to Techkyo/tech-kyo-blog#4