This page provides details about activities and grading of Sprint 1.

Additional Project Information

All of the stories you need for Sprint 1 can be found in Elaboration phase stories

Project Activities (5% in final grade)

Team Exercises (part of 13% for team exercises)

Submission Instructions

Grading Rubric

5% in final grade Exceptional Performance
100 points		 Competent Performance
88 points		 Acceptable Performance
75 points		 Developing Performance
50 points

Unacceptable Performance
0 points

Architecture, Diagram and rationale
15%		 Team properly documents their design work and rationale. Tiers/Layers Diagram is properly updated, constructs (e.g. classes/components/services) are added to appropriate M/V/VM bounded tier section. Diagram is clear and works to support the claims. Team documents their design work and rationale. Tiers/Layers Diagram is updated, and works to support the claims. Only a few issues found. Team documents their design work and rationale. Team documents their design work and rationale. Tiers/Layers Diagram is updated, and works to support the claims but consistency is lacking. Team documents their design work but rationale is inconclusive. Tiers/Layers Diagram lacks evidence to support the claims. There is little effort in either the descriptions or evidence in the diagram to support the claims.
Code Communication
25%		 Code adheres to style guideline; uses good variable, method, and class names; provides Javadocs for methods and classes; appropriate user of helper methods. Code shows adherence to good code communications practices with only a few issues found. Adherence to good code communications practices is apparent but consistency is lacking. There are multiple major issues with adherence to good code communication practices. Code does not meet most elements of good code communication.
Demo
25%		 Team created a polished demo which covered all required features and unique inputs in detail, was easy to follow and showed the program runs without any problems. Team created a polished demo which was easy to follow but there were a few minor issues noted with the demo. Team created demo but there were major issues with delivery. Team did not appear prepared but was able to carry off something of a demo. Team did not provide demo or created one with minimal results.
Planning Activities
10%		 Team correctly entered user stories into the sprint backlog and tracked them through to completion. All team members were involved in planning activities but there were a few minor issues noted. Only a portion of the team was involved in planning activities, or it was not done consistently. Only a portion of the team was involved in planning activities, and it was not done consistently. Minimal evidence of team performing planning activities.
Version Control Activities
15%		 The team consistently used version control to track project artifacts. The team used version control but its use was not consistent. The team used version control, but its use was only in a bursts. The team had minimal use of version control, or its use was mostly just prior to submission. There is little evidence of the team using version control to track artifacts.
Team Communication
10%		 Team consistently communicates using Slack workspace including Virtual Standups. Team has mostly regular use of Slack workspace including Virtual Standups. Team uses Slack workspace including Virtual Standups in bursts. Some evidence of use of Slack workspace including Virtual Standups. Minimal evidence of use of Slack workspace.