-
Notifications
You must be signed in to change notification settings - Fork 0
Definition of Done
This document describes what it means for a feature to be considered done. This means the feature is ready to be shipped. Once a feature passes these tests it's done! New work is either technical debt or a new feature. To learn more visit:
- http://guide.agilealliance.org/guide/definition-of-done.html
- http://www.allaboutagile.com/agile-principle-7-done-means-done/
#1. General Requirements
- A wiki page exists documenting the feature's
- Description & Goal
- Requirements
- General Solution
- All Trello tasks are completed
#2. Designs are Complete
- Wireframes and storyboards
- Product implements UI and UX
#3. Code is Complete
- Project runs without errors or warnings
#4. Testing TBD
#5. Documentation
- Supporting documents are in the wiki
- TBD
#6. Deployed TBD
Kick Off, Feb 20
SCRUM, Feb 22
Functional Requirements, Feb 23
SCRUM, March 3
SCRUM, March 8
SCRUM, March 15
SCRUM, March 22
SCRUM, March 29
SCRUM, April 5
SCRUM, April 12
SCRUM, April 19
SCRUM, April 26
User Accounts
Assigning Evaluations
Assignment Management
Project Evaluation Report
Groups
Class Rank
Definition of Done
[Evaluation MVP (Haggis) Functional Requirements](Evaluation MVP-(Haggis)-Functional-Requirements)
Laravel Resources List
Reading List
Terminology