Construct Needs/Wants/Unattainables Document for Requirements
As a developer, I want to break down our goals into Needs, Wants, and Unattainables, so that our team can more easily understand the scope of asks. The emphasis is on keeping these simple, so they do not constrain us.
Associated Epic: Requirements - Project Setup
Definition of Done
[x] Acceptance criteria defined
[ ] Solution tasks specified
[ ] Feature branch created
[ ] Unit tests written
[ ] Solution is code complete, i.e. passes full suite of unit tests
[ ] Design documents updated if needed
[ ] Pull request created
[ ] Code is reviewed
[ ] Code is merged to dev branch
[ ] Acceptance criteria is met
[ ] Feature branch merged into master
[ ] Feature branch deleted
Acceptance Criteria
[x] Needs are easily understood, documented, and broken down into "In scope", achievable, goals. This includes estimated completion date for our timeline
[x] Wants are understood, documented and broken down into possible stretch goals
[x] Unattainables are understood and documented as "Out of Scope"
[ ] Unknowns should also be documented in this story
Construct Needs/Wants/Unattainables Document for Requirements
As a developer, I want to break down our goals into Needs, Wants, and Unattainables, so that our team can more easily understand the scope of asks. The emphasis is on keeping these simple, so they do not constrain us.
Associated Epic: Requirements - Project Setup
Definition of Done
devbranchAcceptance Criteria