ELR Sprint Grading

Release Demo (40% of total)

Topic	Unsatisfactory (0)	Developing (1-2)	Satisfactory (3-4)	Exemplary (5)
Usability	Multiple bugs during demo OR Features added would not be usable by an average user	N/A	N/A	Few or no bugs during demo AND Features added would be useable by an average user
Installation	Features were not consolidated into one environment - more than one student needed to demonstrate features locally, or the project is server based and features could only be demonstrated locally.	N/A	N/A	All features were merged and deployed/demonstrated on a single machine. If the project is server based, this machine was the server.
User Stories/Requirements	Few, if any, user stories/requirements created or developed in sprint follow template OR Few, if any, features developed during sprint have an associated user story/requirement OR Few, if any, features added in sprint match the expectations set by their user stories/requirements and acceptance tests	Many user stories/requirements created or developed in sprint follow template AND Many features developed during sprint have an associated a user story/requirement AND Many features added in sprint match the expectations set by their user stories/requirements and acceptance tests	Most user stories/requirements created or developed in sprint follow template AND Most features developed during sprint have an associated a user story/requirement AND Most features added in sprint match the expectations set by their user stories/requirements and acceptance tests	All user stories/requirements created or developed in sprint follow template AND All features developed during sprint have an associated a user story/requirement AND All features added in sprint match the expectations set by their user stories/requirements and acceptance tests
Release	Few or no features completed during the sprint AND Cannot document work was performed consistently throughout sprint	Cannot document work was performed consistently throughout sprint	Documents work was performed consistently during the sprint AND Any tasks and user stories that were included in this sprint but not completed are shown in the scrum board as being continued in the next sprint	Documents work was performed consistently during the sprint AND Any tasks that were included in this sprint but not completed were not included in the release and the task and its user story are shown in the scrum board as being continued in the next sprint

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/Requirements	Most user stories/requirements included in the sprint do not have task(s) as dependencies OR user stories/requirements 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/requirements 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 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 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/requirements 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/requirements 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