442 Sprint 3-4 Grading

Release Demo (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Usability	Several UI bugs occurred OR included 1+ bugs impacting functionality OR a typical (untrained) user could not use the features completed during sprint	N/A	N/A	Few or no UI bugs occurred AND no bugs impacting functionality occurred AND a typical (untrained) user could use the features completed during sprint
Sizing and Security	Release is not usable on both mobile and desktop screen sizes OR users’ passwords stored on the server in plaintext	Release is usable on mobile and desktop screen sizes AND users’ passwords are hashed before being saved on the server	Release is usable on all reasonable mobile, tablet, & desktop screen sizes AND users’ passwords are hashed before being saved on the server	Release is usable on all reasonable mobile, tablet, & desktop screen sizes AND users’ passwords are hashed and salted before being saved on the server AND prevents XSS and SQL injection attacks
Requirements	Few or no user stories included in the sprint follow the template OR few or no features completed in the sprint match the expectations set by their user stories and acceptance tests	Many user stories included in the sprint follow the template AND many features completed in the sprint match the expectations set by their user stories and acceptance tests	Most user stories included in the sprint follow the template AND most features completed in the sprint match the expectations set by their user stories and acceptance tests	All user stories included in sprint follow template AND all features added in the sprint match the expectations set by their user stories and acceptance tests
Release	Little or no functionality developed in the sprint was specified in a user story OR release includes files that are not in the repo (files that only specify passwords/API keys not required to be in the repo) OR few tasks included in the sprint either were completed or have comments explaining the issues preventing completion and steps taken to solve those issues	Some functionality developed in the sprint was specified in a user story AND all files include in the release are in the repo (files that only specify passwords/API keys not required to be in the repo) AND many tasks included in the sprint either were completed or have comments explaining the issues preventing completion and steps taken to solve those issues	All functionality developed in the sprint was specified in a user story AND all files include in the release are in the repo (files that only specify passwords/API keys not required to be in the repo) AND most tasks included in the sprint either were completed or have comments explaining the issues preventing completion and steps taken to solve those issues	All functionality developed in the sprint was specified in a user story AND all files include in the release are in the repo (files that only specify passwords/API keys not required to be in the repo) AND all tasks included in the sprint either were completed or have comments explaining the issues preventing completion and steps taken to solve those issues

Onboarding (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Scrum Board Organization	1 or more user stories or tasks are not tagged correctly OR 1 or more user stories or tasks are not in the correct lists OR 1 or more user stories or tasks are moved to BACKLOG from another list OR work was done after sprint deadlines	N/A	N/A	All user stories and tasks are tagged correctly AND all user stories and tasks are in the correct list AND no cards were moved to the BACKLOG from another list during the sprint
User Stories	Most user stories included in the sprint do not have both task(s) as dependencies and acceptance tests	Most user stories included in the sprint have both task(s) as dependencies and acceptance tests	All user stories included in the sprint have both task(s) as dependencies and acceptance tests AND most user stories included in the sprint have acceptance tests which include at least 1 happy path test and, where appropriate, at least 1 alternate path test	All user stories included in the sprint have both task(s) as dependencies and acceptance tests AND all user stories included in the sprint have acceptance tests which include at least 1 happy path test and, where appropriate, at least 1 alternate path test
Tasks	Few or no tasks included in the sprint are both a dependency of exactly 1 user story and include task test(s) OR few or no tasks included in the sprint which created, updated, or deleted files link to the single branch created for it	Most tasks included in the sprint are both a dependency of exactly 1 user story and include task test(s) AND most tasks included in the sprint which created, updated, or deleted files link to the single branch created for it	All tasks included in the sprint are both a dependency of exactly 1 user story and include task test(s) AND most tasks included in the sprint which created, updated, or deleted files link to the single branch created for it	All tasks included in the sprint are both a dependency of exactly 1 user story AND all tasks included in the sprint include task test(s) AND all tasks included in the sprint which created or modified files link to the single branch created for it
Git Repo	1 or more commits to MAIN branch OR 1 or more commits to DEV branch without a comment explaining the error OR many commits to DEV branch OR 1 or more completed tasks' branches were not merged to the DEV branch using a pull request OR 1 or more branches merged to DEV branch before their task was completed OR repo is neither organized nor documented such that onboarding developers can find all code, tests, and other documents	No commits to MAIN branch AND few or no commits to DEV branch with a comment added in each of those commits' GitHub pages acknowledging the commit was a mistake AND all completed tasks' branches were merged to the DEV branch using a pull request AND no branches were merged to DEV branch before their task was completed AND repo is either organized or documented so that onboarding developers can find all code, tests, and other documents	No commits to MAIN branch AND few or no commits to DEV branch with a comment added in each of those commits' GitHub pages acknowledging the commit was a mistake AND all completed tasks' branches were merged to the DEV branch using a pull request AND no branches were merged to DEV branch before their task was completed AND directories are used to organize code, tests, and other documents and have names so that onboarding developers would know where a new file should be added	No commits to MAIN branch AND few or no commits to DEV branch with a comment added in each of those commits' GitHub pages acknowledging the commit was a mistake AND all completed tasks' branches were merged to the DEV branch using a pull request AND no branches were merged to DEV branch before their task was completed AND directories are used to organize code, tests, and other documents AND directory and file names allow onboarding developers to know the functionality within each file
Branch Names	Few or no branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's card number and describe the work the task implemented	Many branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's card number and describe the work the task implemented	Most branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's card number and describe the work the task implemented	All branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's card number and describe the work the task implemented
Commit Messages	Few or no commit messages during the sprint describe the functionality being changed and why the commit matters	Many commits messages of "Add files via upload" during the sprint OR most commits messages during the sprint do not describe the functionality being changed and why the commit matters	Few or no commits messages of "Add files via upload" during the sprint AND most commits messages during the sprint describe the functionality being changed and why the commit matters	Few or no commits messages of "Add files via upload" during the sprint AND most commits messages during the sprint describe the functionality being changed and why the commit matters AND most commits messages during the sprint have a first (subject) line stating why the commit matters

Testing (20% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Acceptance Test Definition	1 or more user stories included in the sprint lacked acceptance test(s) OR 1 or more acceptance tests for user stories completed in the sprint failed	N/A	N/A	All user stories included in the sprint have acceptance test(s) AND all acceptance tests for user stories completed in the sprint passed
Acceptance Test Language	1 or more user stories included in the sprint lacked acceptance test(s) OR no acceptance tests could be run and approved by a typical (untrained) user OR most acceptance tests do not specify all of the inputs needed OR most acceptance tests do not specify the exact results for the steps implemented by this feature	All user stories included in the sprint included acceptance test(s) AND few acceptance tests can be run and approved by a typical (untrained) user AND most acceptance tests specify all inputs to use AND most acceptance tests specify the exact results for the steps implemented by this feature	All user stories included in the sprint included acceptance test(s) AND most acceptance tests can be run and approved by a typical (untrained) user AND AND all acceptance tests specify all inputs to use AND all acceptance tests specify the exact results for the steps implemented by this feature	All user stories included in the sprint included acceptance test(s) AND all acceptance tests can be run and approved by a typical (untrained) user AND all acceptance tests specify all inputs to use AND all acceptance tests specify the exact results for the steps implemented by this feature
Unit and Task Test Definition	1 or more user stories included in the sprint did not not have tasks as dependencies OR few or no tasks included in the sprint have task test(s) verifying the task worked OR 1 or more tasks completed in the sprint have a failing task tests	All user stories included in the sprint had tasks as dependencies AND many tasks included in the sprint have task test(s) verifying the task worked AND all task tests for tasks completed in the sprint pass	All user stories included in the sprint had tasks as dependencies AND most tasks included in the sprint have task test(s) verifying the task worked AND all task tests for tasks completed in the sprint pass	All user stories included in the sprint had tasks as dependencies AND all tasks included in the sprint have task test(s) verifying the task worked AND all task tests for tasks completed in the sprint pass
Unit and Task Test Efficacy	1 or more user stories included in the sprint did not not have tasks as dependencies OR few or no tasks included in the sprint have task test(s) that include specific inputs to use, exact results to expect, and make a convincing case the task was/will be completed correctly	All user stories included in the sprint have tasks as dependencies AND many tasks included in the sprint have task test(s) that include specific inputs to use, exact results to expect, and make a convincing case the task was/will be completed correctly	All user stories included in the sprint have tasks as dependencies AND most tasks included in the sprint have task test(s) that include specific inputs to use, exact results to expect, and make a convincing case the task was/will be completed correctly	All user stories included in the sprint have tasks as dependencies AND all tasks included in the sprint have task test(s) that include specific inputs to use, exact results to expect, and make a convincing case the task was/will be completed correctly