idea(contributing): introduce agile practices

[Zaba505]

Description

Let's better formalize our workflow process by using "story" issues. A "story" issue is basically just an issue template but following the "standards" of an agile user story. For example the template would at minimum require the following:

• brief user story description
• acceptance criteria for recognizing its completed
• link(s) to issue(s) which caused the creation of this story
• story points (probably best to do this through a label)

The flow for creating a "story" issue would be to start with a bug or feature issue and upon reviewing of those a "story" issue would be created to actually encompass the work required to address that bug or feature.

My thoughts

1. I believe this will help us better track work since all work item will now be standardized into a story.
2. I believe this will help new contributors quickly onboard since they won't have to read random issues. Instead they filter for stories which have already been reviewed and should contain all the information necessary to be completed.
3. Story points can also help new contribs determine if they're able to handle the work.

[Zaba505]

@erictg @nikitawootten would love your thoughts on this idea. I know some large open source actually use agile management software like Jira so it wouldn't be too crazy of a scretch to start using this model.

[Zaba505]

@erictg @nikitawootten I've now updated the project management flow.

1. Issues will be assigned to one of the following projects:
   a. Refinement
   b. Prototype
   c. MVP
   d. V1
2. If assigned to Refinement, the issue must be looked over and assigned to one of the other projects based on its priority
3. Then once assigned a project, they can optionally be assigned a milestone. Milestones represent sprints with a cycle time of 1 week.
4. Each project then provides the statuses:
   a. Backlog
   b. Todo (should only contain current sprint issues)
   c. Blocked
   d. In Progress
   e. Done

[Zaba505]

Ok nvm I've now changed it to have only 2 project boards, one for refinement and another for once the issues have been refined. Then, milestones are used for tracking project progress from a high level with the categories, Prototype, MVP, and V1. The main project board then also has a Iteration (aka Sprint) field added for sprint planning.

[Zaba505]

With #56, Megamind now will be using Stories for capturing work items of any kind e.g. new features, bug fixes, documentation updates, etc.