-
Notifications
You must be signed in to change notification settings - Fork 123
Story template
mdz edited this page Sep 2, 2011
·
22 revisions
- Copy this page and name it after the story.
- Fill in each section as applicable, or write N/A (don't delete sections -- except this one!)
What are we trying to accomplish? (in more detail than the title of the story)
- List of items which should be called out as explicitly in or out of scope.
- Includes: adding a page to display search results
- Excludes: embedding video in the search results
- Bonus: ...
- List of statements of fact which should be true in order for the story to be accepted
- When I click the search button, I see search results
How will testing be accomplished? What tests or test infrastructure need to be created?
- Does this work impact anything else currently in progress?
- Should this work be done on a branch or not?
- If so, create the branch and create an issue label on GitHub
- Rough outline of what the user interface will look like
- Shiny
- Anything which probably needs to be done for implementation
- List everything you know so far
- new libraries?
- migrations?
- anything else?
- List of issues which came up during implementation which should be considered before acceptance
- Ask someone who did not work on the project to get it working on their laptop, to chase out issues you may have missed
- Review open issues which affect your branch
- Fill out the known issues list
- Make appropriate preparations so that remote developers can follow along with the demo
- Demo
- Have the acceptance criteria been met?
- Are the tests sufficient?
- Review known issues
- Does the implementation meet expectations for code quality and clarity?
- What considerations are there for deployment to production?
- Has master been merged in?
- Merge into master
- Check that tests pass