CS361: Assignment 3: Project Plan and Sprint 2 Plan (for Milestone #1)


5/5 - (2 votes)

CS361: Assignment 3: Project Plan and Sprint 2 Plan (for
Milestone #1)
Now that you’ve been introduced to the microservices concept, start planning your individual
project. It’s OK to change your plan later!
First, define the entire set of user stories for your individual project. The timespan for the user
stories is this term but you don’t have to finish implementing all the user stories this term. These
user stories will need to go in a Product Backlog column/section/category of your task
management system.
Next, move some of those user stories into a Sprint Backlog—these will be the user stories you
WILL complete during next Sprint (for Milestone #1) and comprise your Sprint Plan. Note these
minimum requirements for Milestone #1:
● Has a way for users to interact (e.g., provide input, push buttons, etc.)
● Reflects CSH
● Reflects three quality attributes you choose (i.e., satisfies the non-functional requirements
you write for each quality attribute)
○ Hint: If you choose “usability” or “inclusivity” as a quality attribute, your
corresponding non-functional requirement can involve the CSH
Complete each item below by replacing the highlighted text (Usability note: double-click the text to
select it).
1) Task Management System
Choose a task management system based on the spike you did previously.
Which task management system did you choose?
2) Product Goal and Backlog
You’ll be using some Scrum methods in this course. Unfortunately, the Scrum Master and
Product Owner roles don’t work well in this setting. You will, however, be experiencing
Scrum Events and Artifacts.
a) What is your Product Goal for your individual project?
The Scrum Guide (
doesn’t give a detailed description of the Product Goal: “describes a future state”,
“long-term objective”. Example Product Goal: “Develop software I can use to
communicate with my dog when I’m on vacation.”
b) In a Product Backlog column, section, or category of your task management system
create user stories for your entire individual project. Use INVEST to guide you.
Requirements for user stories:
● Each has a name that briefly describes the functionality
● Each uses the “As a… I want to… so that…” format (see textbook)
● Total of at least 10 user stories (you will not have to implement all of these)
● As a set, must have no obvious violations of INVEST
Name (e.g.,
As a… I want to… so that… format
1 Name AsAFormat
2 Name AsAFormat
3 Name AsAFormat
4 Name AsAFormat
5 Name AsAFormat
6 Name AsAFormat
7 Name AsAFormat
8 Name AsAFormat
9 Name AsAFormat
10 Name AsAFormat
Enter these user stories into your task management system. Take a screenshot so that
the grader can confirm you added the stories.
3) Non-Functional Requirements
Select the top three quality attributes you care about for your individual project. See
s for ideas. Convert them into non-functional requirements.
a) Which three quality attributes did you choose? Name and define each.
Quality attribute name Quality attribute definition
QualityAttributeName QualityAttributeDefinition
QualityAttributeName QualityAttributeDefinition
QualityAttributeName QualityAttributeDefinition
b) Why did you choose these quality attributes? Ex: How are they relevant to your end
user? How are they relevant to your Product Goal? (1+ sentence per quality attribute)
Quality attribute Why it’s relevant to YOUR project
QualityAttribute OneOrMoreSentence
QualityAttribute OneOrMoreSentence
QualityAttribute OneOrMoreSentence
c) Convert your quality attributes to non-functional requirements. Must be testable.
What are your three non-functional requirements? How will you test that they’re
satisfied? (1+ sentence each)
Quality Attribute 1 QualityAttribute
requirement 1
How will you test that
the non-functional
requirement is satisfied
Quality Attribute 2 QualityAttribute
requirement 2
How will you test that
the non-functional
requirement is satisfied
Quality Attribute 3 QualityAttribute
requirement 3
How will you test that
the non-functional
requirement is satisfied
4) Sprint 2 Plan (for Milestone #1)
a) What is your Sprint Goal?
b) Next, select at least three user stories from your Product Backlog and move them to
your Sprint Backlog. Choose what you think you can complete, but recall the
minimum requirements (see Overview). Which user stories did you select?
c) Take a screenshot that shows you’ve moved these user stories into a Sprint Backlog
in your task management system.
d) Now that you’ve selected your Sprint user stories, you will define several tasks for
each user story—the tasks you’ll need to complete to complete the user story. Add
tasks to each user story and take screenshots showing each user story’s tasks in your
task management system. Note: It might work best to make your user story a task and
your tasks subtasks of the user story.
e) Lastly, you’ll need a Definition of Done for the Sprint. You’ll need to show this DoD
is satisfied when you do your implementation.
Requirements for Definition of Done:
● Has an least one acceptance criterion for each user story
● Each acceptance criterion uses the “Given… when… then…” format
Acceptance criterion For which user story?
AcceptanceCriterion UserStoryName
AcceptanceCriterion UserStoryName
AcceptanceCriterion UserStoryName
Each non-functional requirement is
You are NOT required to put the DoD in your task management system.
PDF or Word format via Canvas.
You must follow instructions at Modules > ‘HOW TO: Attach a Document to “Text Entry” Field’.
You are responsible for satisfying all criteria listed in the Canvas rubric for this assignment. You
will be able to revise this assignment if you miss points.
Please ask via Ed so that others can benefit from the answer.

Scroll to Top