Skip to content

Commit

Permalink
Create sprint0_marking.txt
Browse files Browse the repository at this point in the history
  • Loading branch information
KohinaTheCat authored Sep 28, 2022
1 parent ce343f3 commit a84b9c2
Showing 1 changed file with 224 additions and 0 deletions.
224 changes: 224 additions & 0 deletions marking/sprint0_marking.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,224 @@
# Sprint 0 Marking Scheme

**Team Name:** Catkins
**Github:** https://github.com/UTSCCSCC01/finalprojectf22-catkins

---
## 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: _

- Key users have been identified clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all

Your mark: _

- Scenarios have been described clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all

Your mark: _

- Principles have been described clearly (max 2 marks)
- 2 marks = clearly
- 1 mark = somewhat clearly
- 0 marks = not at all

Your mark: _

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: _

- 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: _

- 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: _

- 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: _

PB.md Total Mark: 8 / 8

---
## Setup (max 3 marks)

- Frontend
- 1 mark = Frontend setup is complete
- 0 marks = Frontend is not setup

- Backend
- 1 mark = Backend setup is complete
- 0 marks = Backend is not setup

Your mark: _

- Database
- 1 mark = Database setup is complete
- 0 marks = Database is not setup

Your mark: _

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: _

- 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: _

- 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: _

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: _

- 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: _

- 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: _

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: _

- Decision making (max 2 marks)
- 2 marks = decision making is described clearly
- 1 mark = unclear decision making
- 0 marks = Not completed

Your mark: _

- 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: _

- Meetings (max 2 marks)
- 2 marks = Meeting plan described clearly
- 1 mark = Description is unclear
- 0 marks = Description is missing; Not completed

Your mark: _

- Next phase (max 2 marks)
- 2 marks = description is clear
- 1 mark = somewhat clear
- 0 marks = no description provided

Your mark: _

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: _

- 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: _

User experience Total Mark: 4 / 4

---
## Total Mark
Sprint 0 Total Mark : 48 / 48

0 comments on commit a84b9c2

Please sign in to comment.