Definitions
Owned by Todd Ford
Definition of Done (DOD)
Team agreed on this DOD as of
Team updated this DOD on
Code meets the requirements of the feature or defect.
Code meets acceptance criteria.
Code passes unit testing.
Code has been checked in.
Release notes have been updated.
Support team is notified of new version.
Future consideration:
Specify “where” we “check in” the code. (e.g. Local vs. Azure DevOps)
Jira Status Definition
To Do - Newly Created tickets
Work Approved - Approved by product team on Stories and ready to be refined and worked on. Note: note bugs will get work approved once refined.
In Progress - Work in sprint being addressed by development team
Blocked - Blocked by development or product and cannot be worked on currently
In Testing - Testing with QA team
Done - Meet definition of done and no work is needed
Cancel - Will not be worked on by anyone
Story Point Estimates
0: Intentionally closed with no effort.
1: < .5 day
2: ~ .5 day
3: ~ 1 day
5: ~ .5 week
8: ~ 1 week
13: ~ 1.5 week
>13: ~ Break down the Story/Bug more
Priority Definitions for Software Development
Critical:
Work has stopped
Application/website is down
Company or client is losing money due to system outage or significant defect
High:
Unblock another person or team
Escalated request (Contractual obligation with a short timeline to deliver)
Go-live issues for UAT (to avoid planned implementation delay or to allow implementation team to finalize dates)
Medium:
New or changes in functionality, or defect corrections
Default flow of work
Low:
Cosmetic changes
Spelling changes
Nice-to-have