Exercise - User Stories, UAC, and Feasibility Matrix draft for Client

  • Due Oct 17, 2023 at 5pm
  • Points 100
  • Available Sep 26, 2023 at 8am - Oct 18, 2023 at 5pm
This assignment is part of the module Day 15 - (Oct 17) Change Mgmt & Quality Assurance and hasn't been unlocked yet.

Completion Prerequisites

The following requirements need to be completed before this page will be unlocked:

    Rubric

    Keep in mind that 96 students have already been assessed using this rubric. Changing it will affect their evaluations.
    Client Exercise - User Stories Draft
    Client Exercise - User Stories Draft
    Criteria Ratings Pts
    Are user stories being created for ALL relevant stakeholders?
    NOTE: It's very likely that some users have more than one user story.
    threshold: pts
    Edit criterion description
    10 pts All relevant stakeholders who will be using the system are captured in the user stories
    7.5 pts 1 relevant stakeholder who will be using the system is not captured in the user stories
    5 pts More than 1 relevant stakeholders who will be using the system are not captured in the user stories
    pts
    10 pts
    --
    Additional Comments
    Did team use proper user story format (i.e role/person, functionality, rationale)?
    threshold: pts
    Edit criterion description
    15 pts Team used proper user story format and used it correctly (role, functionality, business need)
    10 pts For 1-2 user stories, team did not use proper user story format and/or did not use it correctly (role, functionality, business need)
    5 pts For 3 or more user stories, team did not use proper user story format and/or did not use it correctly (role, functionality, business need)
    pts
    15 pts
    --
    Additional Comments
    Are each story scoped to the right size?
    Reminder: As a rule of thumb, user stories should not be too broad. A typical story should take 1 week to complete rather than something like 2-3+ weeks. Remember the guidelines on scoping stories from class.
    threshold: pts
    Edit criterion description
    15 pts All user stories are scoped correctly (e.g. 1 week; include 1 main function (e.g. add donor))
    10 pts 1-2 user stories are not scoped correctly (e.g. 2+ weeks; include 2+ main functions; scoped too narrowly (e.g. need a table to store data))
    5 pts 3 or more user stories are not scoped correctly (e.g. 2+ weeks; include 2+ main functions; scoped too narrowly (e.g. need a table to store data))
    pts
    15 pts
    --
    Additional Comments
    Are User Acceptance Criteria clearly written and validate the user story goal?
    "Valuable" means the criteria should completely validate the story is functioning as expected.
    threshold: pts
    Edit criterion description
    15 pts All UAC are clearly written and validate the user story goal
    10 pts 1-2 UAC are not clearly written and/or do not validate the user story goal
    0 pts 3 or more UAC are not clearly written and/or do not validate the user story goal
    pts
    15 pts
    --
    Additional Comments
    Are UAC written in a testable way?
    UAC should be written as yes/no questions with no ambiguity.
    threshold: pts
    Edit criterion description
    10 pts All UAC are written in a testable (yes/no) way
    7.5 pts 1-2 UAC are not written in a testable way
    5 pts 3 or more UAC are not written in a testable way
    pts
    10 pts
    --
    Additional Comments
    Does the value indicated in Feasibility Matrix seem to align with the previous analyses performed? Does assessment of feasibility seem reasonable?
    threshold: pts
    Edit criterion description
    5 pts User story value completely aligns with previous analyses for all stories. User story feasibility completely reasonable for situation for all stories.
    3 pts User story value does not align with previous analyses for 1-2 stories. AND/OR User story feasibility not reasonable for situation for 1-2 stories.
    1 pts User story value does not align with previous analyses for 3 or more stories. AND/OR User story feasibility not reasonable for situation for 3 or more stories.
    pts
    5 pts
    --
    Additional Comments
    To-Be Diagram ties to user stories
    threshold: pts
    Edit criterion description
    15 pts All proposed functionality in the To Be Diagram is captured in user stories
    10 pts 1-2 proposed functionalities in the To Be Diagram are not captured in user stories
    5 pts 3 or more proposed functionalities in the To Be Diagram are not captured in user stories
    pts
    15 pts
    --
    Additional Comments
    User stories tie to the To Be Diagram
    threshold: pts
    Edit criterion description
    15 pts All user stories clearly tie to functionality of the proposed system in the To Be Diagram
    10 pts 1-2 user stories do not clearly tie to functionality of the proposed system in the To Be Diagram
    5 pts 3 or more user stories do not clearly tie to functionality of the proposed system in the To Be Diagram
    pts
    15 pts
    --
    Additional Comments
    Total Points: 100 out of 100