Skip to content

As a singly locker owner, I want my stuff backed up so that I never lose it

erictj edited this page Sep 6, 2011 · 4 revisions

Analysis

Goal

The goal for this story is that locker owners should always have their Me/ directories backed up so they don't lose their data.

    • Automated, or manually triggered, or both?
    • Multiple, full .tgz archives of the Me/ directory, or incremental backups?
    • Downloadable by the locker owner?
    • If downloadable, can they upload the backup to restore their locker manually?
    • If Singly is automating the backup, will there be a way to restore previous backups from the dashboard?

Scoping

  • 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: ...

Acceptance criteria

  • 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

Testing

How will testing be accomplished? What tests or test infrastructure need to be created?

Interdependencies

  • 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

Wireframes

  • Rough outline of what the user interface will look like

Mockups

  • Shiny

Tasks

  • Anything which probably needs to be done for implementation
  • List everything you know so far

Deployment

  • new libraries?
  • migrations?
  • anything else?

Known issues

  • List of issues which came up during implementation which should be considered before acceptance

Pre-acceptance checklist

  • 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

Acceptance checklist

  • 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 checklist

  • Merge into master
  • Check that tests pass
Clone this wiki locally