- Requester believes that aim has been achieved
- Specs have been written/modified for all changes to code
- Future required-refactoring stories added to Pivotal
- Future story-undo stories added to Pivotal (where story described temporary behaviour)
- Code review has been completed
- Published nothing that makes us worse internet citizens
- If estimate was incorrect, consider causes and suggest actions to improve
-
-
Save michaelwebb76/32cfd5d6fc1001592ce6 to your computer and use it in GitHub Desktop.
Story Checklist
- Understand what the story requester is actually wanting to achieve and why
- Confirm deadline if applicable
- Generate and/or review suggested approaches
- Selected approach meets system architecture goals
- All assets required for the story are available or sensible placeholders exist
- Review areas of the code that will be affected by your changes
- Review the specs that will be affected by your changes
- Confirm or change the estimate on the story
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment