Step 4: 📤 Define & prioritize MVP features

[jdmedlock]

Task Description

• Each team member should add their ideas to the Project Vision & Feature Planning template before the team meeting
• Prioritize each feature - Must Have, Should Have, Nice to Have
• Meet with the team to review each feature & refine priorities

Technical Considerations
N/a

Additional Considerations
All Must Have tasks will make up your MVP. Make sure that you control the scope of the project by limiting the number of Must Have features to the ones you can reasonably complete by the end of Sprint 6.

Remember that you can always add new features once you complete the MVP.

Resources
Choose a Project & create a Vision Statement (Chingu Handbook)
Define & Prioritize MVP features (Chingu Handbook)

Member of Epic: #16

[PaulaR-05]

MVP provided by CHINGU:

What You Need to Do (This is the MVP)

• Structure

1. This is a purely frontend application. No backend is required.
2. You may use any languages, tools, or libraries you prefer when designing and building this app.
3. You may NOT use AI-base solution generators like GitHub CoPilot.
4. Useful links and resources:
   The Array Game

• Styling

1. Surprise us!!!
2. Add a footer containing a link to your team's GitHub repo
3. In general, you will find these UI design principles helpful.
4. Recommend using this resource for clean CSS

• Functionality

1. Leaderboard showing the number of games the current player has won and lost
2. Game controls
3. A 10x10 grid the game is played on
4. User can see the game window with these components

• Leaderboard

1. User can see the display of the total number of wins and losses for each
2. User can see the tally of wins for each of the three ways the game can end
3. User can see the tally of losses for each of the three ways the game can end

• Game Controls

1. User can see a button in the game control panel to start a new game, which updates the Leaderboard, clears the grid, and starts a new game.
2. If the user tries to start a new game while one is in progress a modal alert will be displayed to confirm that the current game may be abandoned.
3. When a game is started the user will see a button to roll the dice
4. After rolling the dice a new roll will be blocked until the new array has been marked on the grid by clicking squares in the grid
5. User can see the value of each dice after they are rolled
6. The user will see a button to allow them to clear the grid and to start refilling it using the values from the current roll. This allows the user to try different options.
7. The user will see a button that allows them to submit their answer after filling in the grid from the current roll of the dice.

• Grid

1. When the dice are rolled the user will be able to click on squares to mark their array.
2. When a square is clicked it's color will change from the color used for unoccupied squares to the color designation for occupied squares.
3. If the total number of squares marked on the grid don't match the numbers on the dice an error message must be issued and the user should be given the option to re-mark the grid to match the dice.

[PaulaR-05]

I think, after completing the MVP we could add some of these features to the game :)

• Extras (Not Required)

1. Implement the game to allow human-to-human competition between 2 players or human-vs-computer competition.

2. Allow the user to choose the color to be used to fill in the grid

3. Maintain player metrics across sessions for the last 3 games that have been played

4. Allow the user to specify the dimensions of the grid

5. Add a countdown timer showing time remaining in the game and create an input field to allow the user to set the starting number of minutes and seconds.

6. Animate the rolling of the dice

7. Play a sound to simulate the rolling dice

8. Add a graph to the leader board to show the number of times a number has been rolled.

9. Support dark/light mode