442 Project Inception

Project Design (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Alignment	Design did not represent an adequate solution to the project vision	Some features were not aligned to the project vision AND some features specified in the backlog were not included in the wireframe	Some features were not aligned to the project vision OR some features specified in the backlog were not included in the wireframe	All features were aligned to the project vision AND all features specified in the backlog were included in the wireframe
Platform Support	Wireframes were not created for both desktop and mobile platforms	Wireframes created for both desktop and mobile platforms AND few features were included in both platforms	Wireframes created for both desktop and mobile platforms AND most features were included in both platforms	Wireframes created for both desktop and mobile platforms AND all features were included in both platforms
Interactivity	Wireframes lack interactions linking pages together	Many issues were found using wireframe interactions OR many features could not be reached using wireframe interactions	Few issues were found using wireframe interactions OR few features could not be reached using wireframe interactions	No issues were found using wireframe interactions AND all features could be reached using wireframe interactions
Consistency and Style	Design looked incomplete or unfinished AND wireframes did not have consistent fonts, colors, and alignments AND colors showed poor contrast	Design looked incomplete or unfinished AND (wireframes did not have consistent fonts, colors, and alignments OR colors showed poor contrast)	Design looked incomplete or unfinished AND wireframes had consistent fonts, colors, and alignments AND colors showed appropriate contrast	Design looked complete and professional AND wireframes had consistent fonts, colors, and alignments AND colors showed appropriate contrast
Proof of Concept	Lacked exactly 1 "investor" user story OR "investor" user story was not properly formatted OR lacked working proof-of-concept code demoing using fetch to retrieve data stored in the backend database OR lacked working proof-of-concept code demoing frontend framework/HTML+CSS framework OR not all of the proof-of-concept code was demoed from prod	N/A	N/A	Defined exactly 1 "investor" user story AND "investor" user story was properly formatted AND had working proof-of-concept code demoing using fetch to retrieve data stored in the backend database AND had working proof-of-concept code demoing frontend framework/HTML+CSS framework AND all proof-of-concept code was demoed from prod

Onboarding (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Scrum Board	1 or more user stories or tasks are not tagged correctly OR 1 or more user stories or tasks are not in the correct list OR 1 or more cards were moved to the BACKLOG from another list during the sprint	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	"Investor" user story is not blocked by all research, proof-of-concept, and wireframing task(s) OR "investor" user story lacks acceptance tests	"Investor" user story is blocked by all research, proof-of-concept, and wireframing task(s) AND ("investor" user story does not include acceptance tests for mobile platform OR "investor" user story does not include acceptance tests for mobile platform)	"Investor" user story is blocked by all research, proof-of-concept, and wireframing task(s) AND "investor" user story includes acceptance tests for mobile platform AND "investor" user story includes acceptance tests for mobile platform desktop platforms	"Investor" user story is blocked by all research, proof-of-concept, and wireframing task(s) AND "investor" user story includes acceptance tests for both mobile and desktop platforms AND "investor" user story includes acceptance tests for normal system usage (happy path) and at least 1 acceptance test showing how expected errors would be handled (alternate path)
Tasks	Few or no tasks included in the sprint are 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 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 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 a dependency of exactly 1 user story and include task test(s) AND all tasks included in the sprint which created, updated, or deleted 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 number and describe the work the task implemented	Many branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's number and describe the work the task implemented	Most branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's number and describe the work the task implemented	All branches used in the sprint (excluding MAIN & DEV) have names identifying the associated task's 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