M2 Development Iteration

Milestone M2 Checklist

☐ Demo video

☐ Demo video report, including who-did-what part

☐ Version of your code from the demo video in a GitHub release (URL submitted to eCourseware dropbox)

☐ Up-to-date versions of your user stories, definitions, model-class design, and reporting artifacts (submitted to eCourseware dropbox)

☐ Task reporting in the form of GitHub issues and pull requests

☐ Customer sign-off

☐ Teammate evaluations

1. Demo Video, Project Artifacts, and Live Demo (Public)

Similar to Milestone M1, there are two main deliverables for Milestone M2: a demo video and a collection of project artifacts.

You should refer to the Milestone M1 instructions document for the detailed instructions regarding what each of these deliverables should include and the criteria by which they will be graded. In particular, see these parts of the document:

Demo Video and Report, including who-did-what report: Same instructions as last time (still must be 8–10 minutes in length). Demo video and who-did-what document creator will again be an A&B eligible role.
Project Artifacts: Same instructions as last time, except that now the Git tag must be “m2”.

2. Project Workflow, Task Planning, and Task Reporting

All work contributed to the project must follow the process described in the Project Workflow Instructions document. This process includes full task planning and outcome reporting.

3. Submitting the Milestone

3.1. Customer Sign-Off

Before your milestone submission will be considered complete, your customer have signed off on it, as per the form below. (Note that I will contact the customer directly to collect their sign-off, so you need only to get their verbal approval.)

3.2. GitHub Release

Once all team members tasks have been completed and their pull requests have been merged into the master branch, your team must create a release for the milestone:

Set the Tag version to m2v1. If changes (e.g., bug fixes) are made to the release after it is created, you can create a new release that includes the changes—just be sure to increment the version (e.g., m2v2).
Set Release title to Milestone M2, version 1 (replacing version 1 with the appropriate version of the release).

As the last step, your team must submit the URL of the release page to the appropriate eCourseware dropbox. Only one team member needs to perform this step. If you need to correct a release, don’t forget to resubmit the URL as well to reflect the correct version.

3.3. eCourseware Dropbox Submission

As the last step, your team must submit the following to the appropriate eCourseware dropbox. Only one team member needs to perform this step. If you need to correct a release, don’t forget to resubmit the URL as well to reflect the correct version.

URL of the GitHub release page, as a text comment in the dropbox.
All requirements, design, and reporting artifacts (including anb.docx, db_design.pptx, definitions.docx, stories.xlsx, and video_m2.docx).

4. Teammate Evaluations

At the end of each iteration, each team member must provide an evaluation of each other team member. Instructions and forms for performing these teammate evaluations will be communicated by email near the end of the iteration.

Milestone M2 Customer Sign-Off Form

Customers: Please indicate your approval of the following items—but ONLY if you agree 100% with the statement for the item.

If you have ANY disagreement, do not give your approval. Instead, provide the team with feedback, and have them resolve whatever issue is preventing your approval.

☐ I have reviewed a demo of the software, and I have provided the team any feedback I had.

☐ I have reviewed the user stories, and they are up to date and consistent with my wishes.

☐ I have reviewed any new user-interface designs, and I approve of them.

☐ New! The team has delivered the software to me, and I have received everything that I need from them.

Grading Rubric

Below are each of the grading items for this Milestone, along with their point values and weights. If an item is not submitted at all, 0 points will be awarded for that item. The top-level bullets specify grading criteria. The sub-bullets indicate standard deductions for errors in a submitted item. The deduction list below may not be complete because there may be mistakes that we did not expect. The deduction for an unexpected mistake will be assessed at the time it’s discovered and will reflect how severe the instructor thinks the mistake is. If the deductions for a grading item total more than the total points for that item, 0 points will be awarded for the item.

Progress on Product

20 points with weight of 30%

Made inadequate progress given the number of team members and time in the iteration
- -2 to -20 depending on severity

Demo Video

20 points with weight of 40%

Fails to provide a gentle introduction that addresses a general audience
- -2 deduction
Fails to tell a user-task oriented cohesive story
- -3 deduction
Fails to use realistic data
- -1 to -3 depending on severity
Fails to demo key features that arguably should have been demoed
- -1 for each missing feature up to -5
Fails to differentiate old and new features
- -2 deduction
Bad demo length
- -1 per minute too short up to -4
- -1 per minute too long up to -4
Bugs apparent
- -1 per bug up to -3
Problems with the video report document
- -5 missing document
- -3 fails to follow Markdown template

Process

Overall weight of 30%

Task Reporting

20 points with weight of 5%

Failed to document outcomes of tasks
- -10 deduction
Failed to follow instructions
- -2 per mistake up to -6

Release

20 points with weight of 5%

Failed to upload correct release URL to eCourseware on time
- -8 deduction

User Stories and Definitions

20 points with weight of 10%

See Milestone M0 rubric
Not up to date
- -6 for not keeping statuses up to date
- -2 per clearly missing user story (e.g., for features already implemented)

Model Class Diagram

20 points with weight of 10%

See Milestone M0 rubric
Not up to date
- -10 Not updated to be consistent with model implementation