• Sprint 0:
  • AWS Amplify Project: Functions
• Sprint 1 / 2:
  • Remove Lowercase Assumption
  • AWS Amplify Project: Authorization
  • AWS Amplify Project: Datastore
• Sprint 3:
  • Auto Generate Item ID
  • AWS Amplify Project: Storage

• Sprint 1:
  • Add AI Chatbot to maintain services
  • Add fields to the main table
• Sprint 2:
  • Create User Table & Services

WWH Template (Replace everything in the <>)

Field	Value
Milestone:	<Create new Milestone to organize all sub-tasks under>
Owner:	<Main Owner for the Project>
Contributors:	<Other Contributors to the Project>
Reviewer:	<Reviewer of the Project Spec>
Status:	<Current Status of the Document. Either: In Progress / In Review / Approved / Rejected>

As a <the person or role who will benefit from the feature>

I want <the feature>

So that <the benefit or value of the feature>

Put this as documentation on top of the class

<If Necessary, insert further narrative of what the current behavior is, and why it is painful>

<Give a high level description of what the feature is>

• [<Task 1>](<Link to Task 1 Issue>)

  • <Description of what needs to be done for the task>

  • <Also write any other concerns that you might have about the implementation of the task>

Scenario	Expected Response
When <a certain input is given>	Will <have expected response>

These scenarios should be written up as tests, using the following naming convention:

'will <have expected response> when <a certain input is given>'