Sprint 0 Marking Scheme
Provides a marking rubric for evaluating Sprint 0 deliverables including summary, competition, backlog, setup, documentation, definition of done, personas, process, and user experience.
View sourceWhat this file does
Provides a marking rubric for evaluating Sprint 0 deliverables including summary, competition, backlog, setup, documentation, definition of done, personas, process, and user experience.
When to use it
- Assessing a team's Sprint 0 submission in a university software engineering course
- Creating a grading template for project kickoff deliverables
- Reviewing completeness of a project's initial documentation and planning
Sprint 0 Marking Scheme
Team Name: [Byte-Peeps]
Github: [https://github.com/UTSCCSCC01/finalprojects22-byte-peeps]
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 Feedback: Couple more users could have been identified as a potential user like company admin stuff e.t.c
-
Scenarios have been described clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all
Your mark: 1 Feedback: Walter White/Alice was not mentioned in the personas. Need to use the same people in scenarios as in Personas
-
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: 7 / 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 Feedback: Depending on how much time you put, this might turns out to be more work than you anticipate at this point. Integrating ML models to your website might be a challenging task, and same for integrating different social media platforms. But I belive, once you are able to integrate one of them using their APIs, others should be similar.
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: 2 / 2
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
9 sections with scoring criteria and feedback for each deliverable, plus a total mark out of 48
Change this for your project
- Replace
[Byte-Peeps]with your team name - Replace
https://github.com/UTSCCSCC01/finalprojects22-byte-peepswith your repository URL - Adjust the total mark (47/48) to reflect actual scores
Where it goes
Keep it in your repository where the agent or team that needs it will read it.
Worth borrowing
- Rubric breaks each deliverable into sub-criteria with explicit point ranges
- Includes space for written feedback per section
- Maps user stories to personas and goals for backlog evaluation
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.