ELR Project Inception

Problem Understanding (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Goal Definition	Team cannot articulate the short term (this semester) and long term (project lifetime) goals of the project, and is not aware of the relevant tech stack and approach to execute those goals	Team can somewhat articulate the short term (this semester) and long term (project lifetime) goals of the project, but is not aware of the relevant tech stack or approach to execute those goals	Team can somewhat articulate the short term (this semester) and long term (project lifetime) goals of the project, and is aware of the relevant tech stack or approach to execute those goals	Team can convincingly articulate the short term (this semester) and long term (project lifetime) goals of the project, and is aware of the relevant tech stack or approach to execute those goals
Problem Space	Team cannot articulate the problem that exists that requires that the project be built, AND is not aware of other solutions that may be competitors, AND is not aware of what the differences are between the proposed solution and competing solutions	Team cannot articulate the problem that exists that requires that the project be built, OR is not aware of other solutions that may be competitors, OR what the differences are between the proposed solution and competing solutions	Team can somewhat articulate the problem that exists that requires that the project be built, and is partially aware of other solutions that may be competitors, and what the differences are between the proposed solution and competing solutions	Team can clearly articulate the problem that exists that requires that the project be built, and is aware of other solutions that may be competitors, and what the differences are between the proposed solution and competing solutions
Demographics	Team does not know who the targeted end users of the project are, or why they would want to use the project	N/A	N/A	Team can identify targeted end users of the project, and why they would want to use the project
Project Plan	Team has no clear plan for accomplishing short term goals, and no clear understanding of how short term goals will feed long term goals	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	Team has a clear plan for accomplishing short term goals, along with the relevant user stories, and an idea of who will execute the stories and when. The team has a clear understanding of how short term goals will feed long term goals
Development Plan	Team does not have a development plan for learning any required technologies	Team has a development plan for learning any required technologies, but the development plan is not documented.	Team has a development plan for learning any required technologies, and the development plan is documented, but there are not defined targets to demonstrate successful understanding.	Team has a well documented development plan for learning any required technologies, and well defined targets to demonstrate successful understanding.

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 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 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 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 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 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/Requirements	Most user stories/requirements included in the sprint do not have task(s) as dependencies or do not include acceptance tests	Most user stories/requirements included in the sprint have task(s) as dependencies and include acceptance tests	All user stories/requirements included in the sprint have task(s) as dependencies and include acceptance tests AND most user stories/requirements included in the sprint include at least 1 happy path and at least 1 alternate path acceptance test	All user stories/requirements included in the sprint have task(s) as dependencies and include acceptance tests AND all user stories/requirements 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 its associated task	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 its associated task	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 its associated task	Most commit messages during the sprint identify functionality being changed and why changes are needed AND all branches used in the sprint (excluding MAIN & DEV) have names identifying the number and functionality of its associated task AND most commit messages during the sprint have a first line summarizing the changes

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