370/442 Project Inception

Project Design (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Alignment	Design does not represent an adequate solution to the stated mission and vision of the project	Many features are not aligned to the mission and vision of the project AND some features specified in the backlog are missing	Some features are not aligned to the mission and vision of the project OR some features specified in the backlog are missing	All features are aligned to the stated mission and vision of the project and all features specified in the backlog are included
Platform Support	Wireframes do not accommodate all platforms on which the application is intended to run	Wireframes accommodate all platforms on which the application is intended to run, but many features are not represented in all platforms	Wireframes accommodate all platforms on which the application is intended to run, but some features are not represented in all platforms	Wireframes accommodate all platforms on which the application is intended to run, and all features are represented equally
Interactivity	Wireframes are not interactive	Wireframes are interactive, but many issues were found in navigation, or many wireframes could not be reached via navigation	Wireframes are interactive, but a few issues were found in navigation, or a few wireframes could not be reached via navigation	Wireframes are interactive, and no issues were found with navigation between wireframes
Consistency and Style	Wireframes use inconsistent fonts, colors, or alignments AND colors show poor contrast or coordination AND design looks incomplete or unfinished	Wireframes use inconsistent fonts, colors, or alignments OR colors show poor contrast or coordination AND design looks incomplete or unfinished	Wireframes use inconsistent fonts, colors, or alignments OR colors show poor contrast or coordination OR design looks incomplete or unfinished	Wireframes are consistent in all visual elements and color choices show appropriate contrast, and design appears complete and professional
Proof of Concept	Proof of concept code is available only on localhost	N/A	N/A	Proof of concept code is deployed to the server

Onboarding (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Scrum Board Organization	Scrum board does not include BACKLOG, PLANNED, IN-PROGRESS, TESTING, COMPLETED, and CLOSED pipelines OR 1 or more user stories or tasks are missing tags or incorrectly tagged OR 1 or more user stories or tasks are not in the correct pipeline	N/A	N/A	Scrum board includes BACKLOG, PLANNED, IN-PROGRESS, TESTING, COMPLETED and CLOSED pipelines AND all user stories and tasks are tagged correctly AND All user stories and tasks are in the correct pipeline
Repo Organization	Repo does not use or incorrectly uses MAIN & DEVELOP branches OR Repo is not organized nor documented so that an outsider can easily find where code, tests, and other documents are stored.	Repo uses MAIN & DEVELOP branches correctly AND Repo is documented so that an outsider can easily find where code, tests, and other documents are stored.	Repo uses MAIN & DEVELOP branches correctly AND Repo's directory names make it easy for an outsider to easily find where code, tests, and other documents are stored AND code in the repo is organized logically.	Repo uses MAIN & DEVELOP branches correctly AND Repo's directory names make it easy for an outsider to easily find where code, tests, and other documents are stored AND Repo organization and file names make it easy for an outsider to understand what each file contains.
User Stories	Most user stories included in the sprint do not have task(s) as dependencies OR user stories included in the sprint do not include acceptance tests	Most user stories included in the sprint have task(s) as dependencies AND user stories included in the sprint include acceptance tests	All user stories included in the sprint have task(s) as dependencies AND all user stories included in the sprint include acceptance tests AND most user stories include tests of happy and alternate paths.	All user stories included in the sprint have task(s) as dependencies AND all user stories included in the sprint include acceptance tests AND all user stories include tests of happy and alternate paths.
Tasks	Few or no tasks included in the sprint are a dependency of a user story OR Few or no tasks developed during sprint include task test(s) OR few or no tasks included in the sprint are linked to the single branch created for it.	Most tasks included in the sprint are a dependency of a user story AND many tasks developed during sprint include task test(s) AND many tasks included in the sprint are linked to the single branch created for it.	All tasks included in the sprint are a dependency of a user story AND most tasks developed during sprint include task test(s) AND most tasks included in the sprint are linked to the single branch created for it.	All tasks included in the sprint are a dependency of a user story AND all tasks developed during sprint include task test(s) AND all tasks included in the sprint are linked to the single branch created for it.
Commit Messages	Few or no commit messages clearly identify functionality being changed or why changes were needed	Many commit messages identify functionality bring changed and why commit was needed AND Most branches used in this sprint have a name that identifies the task it was created for	Most commit messages identify functionality bring changed and why commit was needed AND Most branches used in this sprint have a name that identifies the task it was created for	Most commit messages identify functionality bring changed and why commit was needed AND All branches used in this sprint have a name that identifies the task it was created for AND most first lines provide summary of the commit

Testing (20% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Acceptance Test Definition	One or more user stories developed during sprint lacked acceptance test(s) OROne or more acceptance tests fail	N/A	N/A	Acceptance test(s) defined for every user story included in the sprint AND All acceptance tests pass
Acceptance Test Language	No acceptance tests can be run and approved by a typical (untrained) user ORMost acceptance tests include project developer-specific language/terms	Few acceptance tests can be run and approved by a typical (untrained) user ANDFew acceptance tests include project developer-specific language/terms	Many acceptance tests can be run and approved by a typical (untrained) user ANDNo acceptance tests include project developer-specific language/terms	All or nearly all acceptance tests can be run and approved by a typical (untrained) user
Unit and Task Test Definition	Few or none of the user stories included in the sprint were broken down into tasks OR Few or no tasks included in the sprint have task test(s) which verify the code works correctly	Most or all user stories included in the sprint were broken down into tasks AND Many tasks included in the sprint have task test(s) which verify the code works correctly	Most or all user stories included in the sprint were broken down into tasks AND Most tasks included in the sprint have task test(s) which verify the code works correctly	All user stories included in the sprint were broken down into tasks AND All tasks included in the sprint have task test(s) which verify the code works correctly
Unit and Task Test Efficacy	Few or no tasks have task test(s) that make a convincing case the task was/will be completed correctly OROne or more task tests do not pass	Many tasks have task test(s) that make a convincing case the task was/will be completed correctly ANDAll task tests pass	Most tasks have task test(s) that make a convincing case the task was/will be completed correctly ANDAll task tests pass	All tasks have task test(s) that make a convincing case the task was/will be completed correctly AND All task tests pass