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	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 user stories or tasks were moved to BACKLOG from another list	N/A	N/A	All user stories and tasks are tagged correctly AND all user stories and tasks are in the correct list
Git Repo	1 or more commits to or non-DEV branches merged to MAIN branch OR 1 or more commits DEV branch without a comment explaining the error OR Many commits to DEV branch OR 1 or more completed tasks' branches not merged to DEV branch OR 1 or more branches merged to DEV branch before task was completed OR repo is neither organized nor documented so that an outsider can find all code, tests, and other documents	No commits to nor non-DEV branches merged to MAIN branch AND few or no commits to DEV branch with a comment on any commits explaining the error AND all completed tasks' branches merged into DEV branch AND no tasks' branches merged to DEV branch before the task was completed AND repo is either organized or documented so that an outsider can find all code, tests, and other documents	No commits to nor non-DEV branches merged to MAIN branch AND few or no commits to DEV branch with a comment on any commits explaining the error AND all completed tasks' branches merged into DEV branch AND no tasks' branches merged to DEV branch before the task was completed AND directories are used to organize code, tests, and other documents AND code in the repo is organized logically	No commits to nor non-DEV branches merged to MAIN branch AND few or no commits to DEV branch with a comment on any commits explaining the error AND all completed tasks' branches merged into DEV branch AND no tasks' branches merged to DEV branch before the task was completed AND directories are used to organize code, tests, and other documents AND directory and file names allow a user to understand what each file contains
User Stories	Most user stories included in the sprint do not have task(s) as dependencies or do not include acceptance tests	Most user stories included in the sprint have task(s) as dependencies and include acceptance tests	All user stories included in the sprint have task(s) as dependencies and include acceptance tests AND most user stories included in the sprint include at least 1 happy path and at least 1 alternate path acceptance test	All user stories included in the sprint have task(s) as dependencies and include acceptance tests AND all user stories included in the sprint include at least 1 happy path acceptance and at least 1 alternate path acceptance test
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 or modified 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 or modified files link to the single branch created for it	All tasks included in the sprint are a dependency of exactly 1 user story AND most tasks included in the sprint include task test(s) AND most tasks included in the sprint which created or modified files link to the single branch created for it	All tasks included in the sprint are 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
Branches & Commits	Few or no commit messages during the sprint clearly identify functionality being changed and why the changes are needed OR few or no branches used in the sprint (excluding MAIN & DEV) have names identifying the number and functionality of the task(s) using it	Most commit messages during the sprint identify functionality being changed and why the changes are needed AND many branches used in the sprint (excluding MAIN & DEV) have names identifying the number and functionality of the task(s) using it	Most commit messages during the sprint identify functionality being changed and why the changes are needed AND most branches used in the sprint (excluding MAIN & DEV) have names identifying the number and functionality of the task(s) using it	Most commit messages during the sprint identify functionality being changed and why changes are needed AND most commit messages during the sprint have a first line summarizing the changes AND all branches used in the sprint (excluding MAIN & DEV) have names identifying the number and functionality of the task(s) using it

Testing (20% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Acceptance Test Definition	One or more user stories included in the sprint lacked acceptance test(s) OR one or more acceptance tests fail	N/A	N/A	All user stories included in the sprint have acceptance test(s) AND all acceptance tests pass
Acceptance Test Language	No acceptance tests can be run and approved by a typical (untrained) user OR many acceptance tests do not include specific inputs to use or do not specify the exact results seen	Few acceptance tests can be run and approved by a typical (untrained) user AND few acceptance tests do not include specific inputs to use or do not specify the exact results seen	Most acceptance tests can be run and approved by a typical (untrained) user AND all acceptance tests include specific inputs to use and the exact results seen	All acceptance tests can be run and approved by a typical (untrained) user AND all acceptance tests include specific inputs to use and the exact results seen
Unit and Task Test Definition	One 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's results OR one or more tasks completed in the sprint have a failing task tests	All user stories included in the sprint had tasks as dependencies AND all task tests many tasks included in the sprint have task test(s) verifying the task's results 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's results 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's results AND all task tests for tasks completed in the sprint pass
Unit and Task Test Efficacy	One 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