Skip to content
This repository has been archived by the owner on Feb 21, 2024. It is now read-only.

Decide on what 'done' means #4

Closed
4 tasks
carodew opened this issue Feb 6, 2018 · 1 comment
Closed
4 tasks

Decide on what 'done' means #4

carodew opened this issue Feb 6, 2018 · 1 comment

Comments

@carodew
Copy link
Contributor

carodew commented Feb 6, 2018

This is probably a workshop/collaborative design session where the build team can suss out how done is done. Can probably be combined with #3.

it should include …

  • input from everyone who will be involved in building the site
  • acceptance criteria that should apply to all issues
  • (optional) it might include some quick and dirty design principles, if there's appetite for this

it's done when …

  • We document the Definition of Done somewhere publicly available and easy to find. Could be in the readme doc but also could be in the wiki.
@carodew carodew added this to the Lay the foundation milestone Feb 6, 2018
@carodew carodew added this to To do in What we're doing Feb 6, 2018
@carodew carodew moved this from To do (3) to Ready in What we're doing Feb 12, 2018
@carodew
Copy link
Contributor Author

carodew commented Feb 14, 2018

I folded this into #3

@carodew carodew closed this as completed Feb 14, 2018
What we're doing automation moved this from Ready to Done Feb 14, 2018
willcahoe added a commit that referenced this issue Sep 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
Development

No branches or pull requests

1 participant