lab03 : First Retro and MVP Preparation

num	ready?	description	assigned	due
lab03	true	First Retro and MVP Preparation	Fri 10/15 11:00AM	Fri 10/22 11:59PM

Points

Grading for First Retro Participation and MVP Preparation

Graded: (lab03-I) (5 pts) You earn these individual points if you participated in the first retrospective.

Graded: (lab03-T) (20 pts) You earn these team points based on the attendance/participation in your retrospective; 3.33 per team member for teams of 6, 4 per team member for teams of 5, 5 points per team member for teams of four.

Graded: (lab03-T) (20 pts) You earn these team points when the content in team/retrospectives/RETRO_01.md is updated per the instructions from lect05.

New since lect05:

Graded: (lab03-T) (10 pts) You earn these team points when you recorded the outcome of (one of) your Retro experiments in team/retrospectives/RETRO_01.md by the due date of the MVP.

Graded: (lab03-I) (20 pts) You earn these points for submitting feedback on overall team performance via a CATME.org form survey that you got email invitations and possibly reminders for.

Graded: (lab03-T) (15 pts) You earn these team points if your team posted, or commented on already posted, articles or tutorials in at least one of the ..._articles channels. You need at least 3 such interactions (posts or comments) to get full credit. Please document that you (which members of your team?) did these posts or comments in your LEARNING.md file.

Graded: (lab03-T) (10 pts) You earn these team points if the team links spreadsheet is updated with all the requested links to your repo information.

Ten days to MVP Code Freeze. Twelve to MVP video demos. Please prepare:

Planning your demo (MVP video)

Plan an up-to-five minute presentation video
Please prepare a max. 5 minute YouTube video (unlisted or public, your choice)
- See the bottom of the lab02 description for information about creating your MVP video.
- Links to videos will be made available to (some of) the class for peer review, but will not be made public
Present to an audience of potential users
- Not to an audience of CS148 students, or the instructor or TAs.
- Explain what problem the app solves, or what need it fulfills, as you demo the features of the app.
Stay focused on user functionality.
- Do not go into details of implementation, or team process.
- There will be other presentations for that.
Optionally, you may introduce with a powerpoint slide, and/or close with one, but the bulk of the time, you should be sharing your screen and showing us your app.
At the end, tell us a bit about upcoming features planned for the next iteration.

At or after next week’s (week 5) lab session you’ll be asked to evaluate other teams’ presentation(s), so plan to watch them and be ready to do some very brief writing after each one.

Point us to your video

create a file team/MVP_DEMO.md containing your MVP video link and any additional information you see fit that you think doesn’t belong in the project’s README.md

Add the following information to your README.md:

===================================================================================

Installation

Prerequisites

TODO: List what a user needs to have installed before running the installation instructions below (e.g., git, which version(s) of your framework(s) of choice)

Dependencies

TODO: List which libraries / add-ons you added to the project, and the purpose each of those add-ons serves in your app.

Installation Steps

TODO: Describe the installation process (making sure you give complete instructions to get your project going from scratch). Instructions need to be such that a user can just copy/paste the commands to get things set up and running. Note that with the use of GitHub Actions, these instructions can eventually be fully automated (e.g. with act, you can run GitHub Actions locally).

Functionality

TODO: Write usage instructions. Structuring it as a walkthrough can help structure this section, and showcase your features.

Known Problems

TODO: Describe any known issues, bugs, odd behaviors or code smells. Provide steps to reproduce the problem and/or name a file or a function where the problem lives.

Contributing

TODO: Leave the steps below if you want others outside your team to contribute to your project.

Fork it!

Create your feature branch: git checkout -b my-new-feature

Commit your changes: git commit -am 'Add some feature'

Push to the branch: git push origin my-new-feature

Submit a pull request :D

License

If you haven’t already, add a file called LICENSE.txt with the text of the appropriate license. We recommend using the MIT license: https://choosealicense.com/licenses/mit/”