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 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 follow project conventions for branching, merging, and pull requests.	Repo sometimes follows project conventions for branching, merging, and pull requests.	Repo often follows project conventions for branching, merging, and pull requests.	Repo always follows project conventions for branching, merging, and pull requests.
User Stories/Requirements	Most user stories/requirements 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/requirements included in the sprint have task(s) as dependencies AND user stories included in the sprint include acceptance tests	All user stories/requirements included in the sprint have task(s) as dependencies AND all user stories/requirements included in the sprint include acceptance tests AND most user stories/requirements that involve user input include tests of happy and alternate paths.	All user stories/requirements included in the sprint have task(s) as dependencies AND all user stories/requirements included in the sprint include acceptance tests AND all user stories/requirements that involve user input include tests of happy and alternate paths.
Tasks	Few or no tasks included in the sprint are a dependency of a user story/requirement 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/requirement 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/requirement 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/requirement 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