Sprint 0 Marking Scheme
Provides a grading rubric for a Sprint 0 deliverable, scoring summary, competition, backlog, setup, documentation, definition of done, personas, process, and user experience.
What this file does
Provides a grading rubric for a Sprint 0 deliverable, scoring summary, competition, backlog, setup, documentation, definition of done, personas, process, and user experience.
When to use it
- Evaluating a team's Sprint 0 submission in a university capstone course
- Creating a marking scheme for an agile project kickoff phase
- Reviewing completeness of project planning artifacts like personas and backlog
Sprint 0 Marking Scheme
Team Name: BC Hub
Github: [GitHub Repo Link]
summary.md (Max 8 marks)
-
Project objectives have been specified clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
Your mark: 2
-
Key users have been identified clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
Your mark: 2
-
Scenarios have been described clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
Your mark: 2
-
Principles have been described clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
Your mark: 2
summary.md Total Mark: 8 / 8
competition.md (Max 2 marks)
- Competition has been identified clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
competition.md Total Mark: 2 / 2
Product Backlog PB.md (Max 8 marks)
-
Sufficient stories created to occupy team for release 1 (max 2 marks)
- 2 marks = Excellent
- 1 mark = Few user stories, clearly not enough to occupy team for release 1
- 0 marks = No user stories
Your mark: 2
-
Relevant persona clearly identified for each user story (max 2 marks)
- 2 marks = All user stories identify relevant persona
- 1 mark = Part of the stories do not mention persona
- 0 marks = No personas mentioned in user stories
Your mark: 2
-
All user stories identify goal/desire and all identify why/benefit (max 2 marks)
- 2 marks = All user stories identify goals
- 1 mark = Part of the stories do not identify goals
- 0 marks = No user story identifies goals
Your mark: 2
-
Writing (max 2 marks)
- 2 marks = Writing is very clear for all stories
- 1 mark = Writing is not clear for some stories
- 0 marks = Writing is poor and with errors
Your mark: 2
PB.md Total Mark: 8 / 8
Setup (max 3 marks)
-
Frontend
- 1 mark = Frontend setup is complete
- 0 marks = Frontend is not setup
Your mark: 1
-
Backend
- 1 mark = Backend setup is complete
- 0 marks = Backend is not setup
Your mark: 1
-
Database
- 1 mark = Database setup is complete
- 0 marks = Database is not setup
Your mark: 1
Setup Total Mark: 3 / 3
Documentation: README.md (max 3 marks)
-
Motivation and Project Description
- 1 mark = Short detailed description of motivation behind the project and why it exists
- 0 marks = Motivation is missing or has grammar errors/typos
Your mark: 1
-
Installation for your Software/System
- 1 mark = Instructions for installation process are clear and concise, with provided commands.
- 0 marks = No instructions or installation section has grammar errors/typos
Your mark: 1
-
Contribution
- 1 mark = Contribution process is well-explained, allowing contributors to easily get on board
- 0 marks = Contribution is missing or has grammar errors/typos
Your mark: 1
README.md Total Mark: 3 / 3
Definition of done: done.md (max 2 marks)
- Definition of done is:
- 2 marks = Relevant to the project and applies to all stories
- 1 mark = Somewhat relevant and does not apply to all stories
- 0 marks = Missing or unclear
done.md Total Mark: 1 / 2
Done.md is supposed to apply to the individual user stories, not the project as a whole.
Personas.pdf (max 8 marks)
-
Quality of the persona should be measured based on the presence/absence quality of description of the following elements: Age, personality, personal background Skills, professional background Attitude towards technology, domain, etc. Goals when using the system (max 4 marks)
-
4 marks = Two or more high quality personas provided
-
3 marks = Two personas provided but quality is not very good
-
2 marks = Only 1 persona provided with good quality
-
1 mark = One persona of poor quality
-
0 marks = No personas provided
Your mark: 4
-
-
Relevance to the system (max 2 marks)
- 2 marks = Personas are highly relevant to the system
- 1 mark = Personas are somewhat relevant
- 0 marks = Not all or no personas are relevant
Your mark: 2
-
Persona Descriptions (max 2 marks)
- 2 marks = Appropriate length and is well-written
- 1 mark = Short and/or with errors
- 0 marks = No writing or poor quality
Your mark: 2
Personas.pdf Total Mark: 8 / 8
Process: process.md (max 10 marks)
-
Team organization (roles) divided clearly (max 2 marks)
- 2 marks = Team organization (roles) are divided clearly
- 1 mark = Unclear team organization
- 0 marks = Not completed
Your mark: 2
-
Decision making (max 2 marks)
- 2 marks = decision making is described clearly
- 1 mark = unclear decision making
- 0 marks = Not completed
Your mark: 2
-
Prioritizing user stories (max 2 marks)
- 2 marks = Clear criteria is used on how user stories are prioritized
- 1 mark = Somewhat clear criteria used
- 0 marks = Not completed
Your mark: 2
-
Meetings (max 2 marks)
- 2 marks = Meeting plan described clearly
- 1 mark = Description is unclear
- 0 marks = Description is missing; Not completed
Your mark: 2
-
Next phase (max 2 marks)
- 2 marks = description is clear
- 1 mark = somewhat clear
- 0 marks = no description provided
Your mark: 2
process.md Total Mark: 10 / 10
User experience: (max 4 marks)
-
User experience is logically related to scenarios (from summary.md) (max 2 marks)
- 2 marks = Relates well
- 1 mark = Somewhat related
- 0 marks = Missing or not related
Your mark: 2
-
Graphic representation is clear and represents well indended user interface elements (max 2 marks)
- 2 marks = Clear and well done
- 1 mark = Not very clear,
- 0 marks = missing or completely unclear
Your mark: 2
User experience Total Mark: 4 / 4
Total Mark
Sprint 0 Total Mark : 47 / 48
What's inside
10 sections, 24 scoring criteria, 1 total mark line
Change this for your project
- Replace
BC Hubwith your team name - Replace
UTSCCSCC01/finalprojectw22-bc-hubwith your GitHub repository URL - Adjust mark values and criteria to match your course's grading scheme
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Breaks down each deliverable into specific, measurable criteria with point ranges
- Includes a total mark calculation for quick grading
Related Documents
AICA PRD Quality Rubric
Defines a 10-dimension scoring rubric (0-5 each) to evaluate and create PRDs, with a target score of 36+ for agent-driven implementation.
Judging Rubric
Defines a 100-point scoring rubric for an AI-for-social-good hackathon, covering five criteria with detailed score bands and tie-breaking rules.
Liscribe v2 — Rubric of Success
Defines the complete UI specification, success criteria, and non-negotiable principles for a macOS transcription app with three independent workflows.
QualRubric
Defines a qualitative rubric for PhD qualifying exam presentations, focusing on context, organization, and knowledge demonstration rather than numerical scoring.