CS$361$: Assignment $3$: Project Plan and Sprint $1$ Plan $($for Milestone #$1)$

Overview

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. These user stories will need to go in a Product Backlog column$/$section$/$category of your task management system. You won$$t have to finish implementing the entire Product Backlog this term.

Next, move some of those user stories into a Sprint Backlog$$these will be the user stories you WILL complete during this Sprint $($for Milestone #$1)$ and comprise your Sprint Plan.

Note these minimum requirements for Milestone #$1$:

$$ At least three user stories completed

$$ All features that are part of the milestone must be working. The milestone should not have partially completed features.

$$ Has a way for users to interact $($e$.$g$.,$ provide input, push buttons, etc.$)$

$$ Reflects each of the Inclusivity Heuristics

$$ Reflects three quality attributes of your choice $($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 Inclusivity Heuristics.

$$ Hint $2$: $$Maintainability$$ is another good quality attribute to select because, later in the course, you will be asked to improve the maintainability of your code by eliminating the $$code smells$$ listed in Chapter $8$ of the textbook.