Sprint 1 Marking Scheme

# Sprint 1 Marking Scheme

**Team Name:** [Byte Peeps]  

*(Convention: N=sprint number, ex: sprintN.md means sprint2.md for sprint 2, and SR(N-1)md means SR1.md for sprint 2, that is Sprint Retrospective for Sprint 1, to be hold during planning meeting at the beginning of Sprint 2)*

---
## Planning Meetings (RPM.md, sprintN.md) (max 5 marks)

  - RPM.md (Release Planning Meetings) (max 3 marks)
    - 3 marks = Meeting is documented, participants are recorded, everyone has participated, Release goals are specified and there are sufficient references to user stories to be completed during the release
    - 2 marks = Meeting is documented, participants are not recorded or at least one member has not participated, Release goals are somewhat specified and there are some references to user stories to be completed during the release
    - 1 mark  = Meeting is documented, participants are not recorded or the majority has not participated, Release goals are unclear or the references to user stories to be completed during the release are missing or incomplete
    - 0 marks = No meeting document submitted or the submitted document contains no relevant information to the RPM
    
    
Your Mark: 3
    
  - Sprint Planning meeting (sprintN.md) (max 2 marks)
    - 2 marks = Meeting and sprint goal is documented, all spikes clearly identified, team capacity recorded, participants are recorded, everyone has participated, decisions about user stories to be completed this sprint are clear, tasks breakdown is done.
    - 1 mark  = Meeting and sprint goal is documented, some spikes not clearly identified, one or more members of team's capacity not recorded, participants are not recorded or the majority has not participated, decisions are unclear,
    there is no clear evidence which user story will be completed or task breakdown is unclear or incomplete
    - 0 marks = No meeting document submitted or the submitted document contains no relevant information to the sprint 1

    Your Mark: 2

  Planning Meetings Total Mark: 5 / 5

---
## Daily Stand-ups (max 10 marks)
  - Team updates are done on the C01/301 Discord server within your team's #standup channel
  - Standup Format:
      ```
      [Standup Date] - Sprint # Standup #
      1. What did you work on since the last standup?
      2. What do you commit to next? 
      3. When do you think you'll be done?
      4. Do you have any blockers?
      ```
  - Each person is required to post a minimum of 3 standups per sprint (Max 10 marks; 3 marks per daily standup, 1 mark for 3 days completed)
  - Standup updates answers the necessary questions and is good quality
    - 3 marks = All teams members have sent their updates in the channel and are well written/good quality
    - 2 marks = At least 1 group member has not sent their update or is low-quality
    - 1 mark  = At least 2 group members or more have not sent their updates or is low-quality
    - 0 marks = At least 3 group members or more have not sent their updates or is low-quality

  Daily Stand-ups Total Mark: 10 / 10

---
## User Stories (Tracked in Jira) (max 10 marks) 
  - Correctly formulated user stories (max 2 marks)
    - 2 marks = all stories in Jira Backlog follow the User Story template
    - 1 mark  = two or more stories in Jira Backlog do not follow the template
    - 0 marks = the majority of stories in Jira Backlog do not follow the template or no stories at all

    Your Mark: 2

  - Broken down into tasks/subtasks (max 2 marks)
    - 2 marks = all Sprint 1 stories estimated, broken into tasks/subtasks, tasks assigned to all team members
    - 1 mark = one or more Sprint 1 stories are not recorded Jira, or not estimated, or nor broken into tasks, or at least one task not assigned, or at least one team member unassigned a task
    - 0 marks = the majority of Sprint 1 stories not recorded in Jira or not estimated, or nor broken into tasks, or tasks not assigned, or team members unassigned a task

    Your Mark: 1 (BYT - 23 Subtasks not assigned)

  - Estimated (max 2 marks)
    - 2 marks = all stories in Jira Backlog are point estimated and the point value is recorded in Jira
    - 1 mark  = two or more stories in Jira Backlog are not point estimated or the point value is not recorded in Jira
    - 0 marks = the majority of stories in Jira Backlog are not point estimated or the point value is not recorded in Jira

    Your Mark: 2

  - Prioritized	(max 2 marks)
    - 2 marks = all stories in Jira Backlog are prioritized in the order which matches the priority of their associated milestones
    - 1 mark  = two or more stories in Jira Backlog not are prioritized in the order which matches the priority of their associated milestones]
    - 0 marks = the majority of stories in Jira Backlog appear to be not prioritized in the order which matches the priority of their associated milestones

    Your Mark: 2

  - Clearly Defined Acceptance Criteria (max 2 marks)
    - 2 marks = all Sprint 1 stories have clearly defined and testable acceptance criteria
    - 1 mark  = one or more Sprint 1 stories do not have clearly defined or testable acceptance criteria
    - 0 marks = the majority of the Sprint1 stories do not have clearly defined or testable acceptance criteria

    Your Mark: 2 

  User Stories Total Mark: 9 / 10

---
## Tracking on Jira  (max 20 marks) 
  - Are all your stories and tasks being worked in this sprint tracked on Active Sprint Board? (max 2 marks)
    - 2 = all stories recorded
    - 1 = part of the stories missing
    - 0 = no stories on Active Sprint Board

    Your Mark: 2 
  
  - Did you start all stories for sprint one? (max 2 marks)
    - 2 marks = all stories started or some stories not started, but logical explanation provided as a story comment
    - 1 mark  = part of the stories not started and explanation why not is not provided
    - 0 marks = no story started
    
    Your Mark: 2

  - Do the pull request on GitHub match the tasks listed on Jira Active Sprint Board? (max 2 marks)
    - 2 marks = no tasks are missing
    - 1 mark  = two or more tasks are missing
    - 0 marks = no tasks or tasks do not match at all
    
    Your Mark: 2

  - Is the pull request done by the person to whom the task has been assigned to?  (max 2 marks)
    - 2 marks = all assigned tasks are completed
    - 1 mark  = two or more tasks were not completed as assigned
    - 0 marks = no task was completed by anyone
    
    
  Your Mark: 2
  
  - Is each pull request made from a separate branch for each individual task? (max 5 marks)
    - 5 marks = pull request for each task made from own separate branch
    - 4 marks = pull request for 1 or more tasks not made from own separate branch
    - 3 marks = pull request for 2 or more tasks not made from own separate branch
    - 2 marks = pull request for 3 or more tasks not made from own separate branch
    - 1 mark  = pull request for 4 or more tasks not made from own separate branch
    - 0 marks = pull request for the majority of tasks not made from own separate branch
    
    
Your Mark: 5
    
  - Is the git commit message clear? (max 2 marks)
    - 2 marks = all commit message begin with the ticket number of the task followed by a short description of commit changes
    - 1 mark  = one or more commit messages do not begin with the ticket number of the task followed by a short description of commit changes
    - 0 marks = majority of commit message do not begin with the ticket number of the task followed by a short description of commit changes
    
    
Your Mark: 1 (Some commit messages do not start with the ticket number e.g some commit messages on BYT113 branch)
    
  - Tasks Distribution (max 3 marks)
    - 3 marks = every team member had at least one task assigned and completed
    - 2 marks = every team member had at least one task assigned and made a pull request
    - 1 mark  = at least one team member did not complete any task or did not have any task assigned
    - 0 marks = most of team members have no tasks assigned and/or completed

    Your Mark: 3

  - Branch Naming (max 2 marks)
    - 2 marks = every team branch is named after the associated single ticket number
    - 1 mark  = at least one branch is not named after the associated single ticket number
    - 0 marks = most branch names are not named after the associated single ticket number
    
    Your Mark: 2

Tracking on Jira Total Mark: 19 / 20

---
## Sprint Completion (Max 20 marks) 
  - Minimum of 5 user stories needed  
    (If you do not have 5 user stories for that sprint, you must have a sufficient number of subtasks for all your user stories)
  - Unstarted stories removed during the sprint will not count if an explanation is provided for why the story was not started/completed
  - Started stories that are incomplete will be counted
  - Mark Breakdown: [x = Percentage of story points completed * 20]

  Your Mark: 20 / 20

---
## System Design (PDF or MD file or another suitable format) (max 10 marks) 
  - Cover Page and Table of Contents (max 2 marks)
    2 marks = both are present
    1 mark  = at least one is present
    0 marks = None present
    
    Your Mark: 2
  
  - CRC Cards [or equivalent, if the team is not using CRC) (max 4 marks)
    - 4 marks = Class names and Collaborators have matching names and responsibilities are stated clearly
    - 3 marks = At least one of the class names does not match the collaborator names or the responsibilities for at least one class are unclear
    - 2 marks = Two class names do not match the collaborator names or the responsibilities of two or more classes are not stated or are unclear
    - 1 mark  = The majority of class names do not match the collaborator names or the responsibilities of the majority of the classes are not stated or are unclear
    - 0 marks = No CRC provided or the provided document does not match the CRC model

    Your Mark: 4

  - Software Architecture Diagram (max 4 marks)
    - 4 marks = The Architecture Diagram is present, it is formatted using proper graphic symbols, and it follows a known Architecture diagram.
    If the system architecture does not follow the MVC (studied in class), a web link or reference has been provided to support the used architecture
    - 3 marks = The Architecture Diagram is present, it is not formatted well, and it follows somewhat a known Architecture diagram.
    If the system architecture does not follow the MVC (studied in class), a web link or reference has been provided to support the used architecture
    - 2 marks = The Architecture Diagram is present, it is not formatted well, or it does not follow a known Architecture diagram.
    A web link or reference has been provided, but it does not support the used architecture
    - 1 mark  = The Architecture Diagram is present, it is not formatted well, and it is unclear what Architecture it follows.
    There is no web link or other reference lending support to the presented diagram.
    - 0 marks = No diagram present or the presented document does not look like a software architecture diagram

    Your Mark: 4
  
  System Design Total Mark: 10 / 10

---
## Sprint Demo (Max 14 marks) 
  - Attendance (max 2 marks)
    - 2 marks = full team is present
    - 1 mark = one member is not present
    - 0 marks = more than one member is not present

    2
  
  - Working software (max 8 marks)
    - 8 marks = features presented work flawlessly
    - 1 mark removed for each bug/error identified or for missing records on Jira

    
    - Need to include the restriction to the username/password size  

    7

  - Presentation (max 2 marks)
    - 2 marks = UI demonstrated is visually appealing and intuitive for users
    - 1 mark = one or more errors identified by the demo TA
    - 0 marks = UI is visually unappealing

    - logout button appearance can be improved 

    1

  - Documentation (max 2 marks)

  - 2 marks = documentation has been created for frontend and backend systems with great detail
  - 1 mark = documentation has been created for frontend and backend systems with some errors
  - 0 marks = documentation has not been created

   2


  Your Mark: 12 / 14

---

Notes: Sprint 1 Docs were submitted few minutes late. Tiemstamp shows the time June 11, 12:14 am. The submission was due on June 10, 11:59 pm. We are not penalizing you this time. But make sure to submit on time going forward.

## Total Mark

85 / 89