Project Activities (5% in final grade)

Project submissions
- Sprint 1 release
- Sprint 1 demo
- Application implementation
  - Functionality
  - Adherence to prescribed architecture
Other dimensions
- Planning and managing of activities in Trello board throughout and in support of Sprint 1
- GitHub use for version control
- Slack workspace use for team communication
- Individual team member visibility in Trello board, Slack workspace, and GitHub activities
- Each team member completes the Architecture Lesson Spikes:

Team Exercises (part of 13% for team exercises)

GitHub repository

Submission Instructions

Create a Sprint 1 release using the instructions for creating a GitHub code release provided here.
Create the Sprint 2 Done list in Trello. Put it to the left of the Sprint 1 Done list.
Your instructor will observe your demo to gauge the functionality of the product, and may also do independent testing of it for the Functionality dimension.
Your instructor will review your code. Adherence to the architecture will be judged by your code base.
Your TA/instructor will look at your planning activity directly in your Trello planning board. Your planning activity should show consistent updating of the story cards as stories progress through the sprint activities.
Your TA/instructor will look at your version control use, and team communications directly in your GitHub repository, and Slack workspace, respectively.
Your TA/instructor will determine individual contributions to the project directly from the evidence provided in your team's Trello board, GitHub repository, and Slack workspace.

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
Adherence to Architecture 35%	Team properly adheres to architecture supplied in the Architectural Lessons of this sprint.	Team mostly adheres to architecture with a few gaps.	Team lacks adherence to the architecture.	Team poorly adheres to the architecture.	Code base is virtually empty.
Acceptance Test Plan 5%	Complete Acceptance Test Plan submitted showing the status of all tests.	Complete Acceptance Test Plan submitted with a few issues with test status.	Only minor issues were found with the Acceptance Test Plan and test status.	Major problems with Acceptance Test Plan or the status of tests.	No Acceptance Test Plan submitted, or it does not indicate the status of any tests.
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.

document.write(page_topic);

Additional Project Information

Project Activities (5% in final grade)

Team Exercises (part of 13% for team exercises)

Submission Instructions

Grading Rubric