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 not included in the wireframe	Some features are not aligned to the mission and vision of the project OR some features specified in the backlog are not included in the wireframe	All features are aligned to the stated mission and vision of the project AND all features specified in the backlog are included in the wireframe
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 AND most features are not represented in all platforms	Wireframes accommodate all platforms on which the application is intended to run AND 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 AND many issues were found in navigation or many wireframes could not be reached via navigation	Wireframes are interactive AND 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 while navigating AND all wireframes could be navigated to
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	Not all proof of concept code is deployed on actual systems or servers	N/A	N/A	All proof of concept code is deployed on actual systems or servers

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	N/A	N/A	All user stories and tasks are tagged correctly AND all user stories and tasks are in the correct list
Repo Organization	Many commits to DEV or MAIN branches OR 1 or more commits to DEV or MAIN branches does not have a comment explaining the error OR branch merged to DEV before task was completed OR (non-DEV) branch merged directly to MAIN branch OR repo is not organized nor documented so that an outsider can easily locate all code, tests, and other documents	Few or no commits to DEV and MAIN branches and a comment was added to each of those explaining the error AND no branches merged to DEV before the task was completed AND no (non-DEV) branch was merged directly to MAIN AND repo is either organized or documented so that an outsider can easily locate any code, tests, and other documents	Few or no commits to DEV and MAIN branches and a comment was added to each of those explaining the error AND no branches merged to DEV before the task was completed AND no (non-DEV) branch was merged directly to MAIN AND directory names make it easy for an outsider to locate all code, tests, and other documents AND code in the repo is organized logically	Few or no commits to DEV and MAIN branches and a comment was added to each of those explaining the error AND no branches merged to DEV before the task was completed AND no (non-DEV) branch was merged directly to MAIN AND directory names make it easy for an outsider to locate all code, tests, and other documents 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 either do not have task(s) as dependencies OR most user stories included in the sprint do not include acceptance tests	Most user stories included in the sprint have task(s) as dependencies AND most user stories included in the sprint 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