Decide on team norms and workflow

[carodew]

This is probably a workshop/collaborative design session where the build team can suss out how we want to get things done. Can probably be combined with #4.

it should include …

• input from everyone who will be involved in building the site
• an intro to Kanban (if needed)
• identifying the phases a unit of work needs to go through (not always sequentially but usually so)
• talk about team communication preferences
• how often we need to meet and at what cadence
• discussion on what 'done' is

it's done when …

• The agreed upon phases have been added as columns in the Kanban board ("Project" in GH) in a way the team can agree is sensible and workable
• we have a publicly documented Definition of Done for all work that will end up on the website

[carodew]

I'm going to merge #4 into this one since I plan on doing it all in one workshop 🤞

[carodew]

proposal for definition of done

1. conform to WCAG 2.0 AA (accessibility standard)
2. conform to 18F content guidelines
3. conform to 18F front end guidelines
4. responsive down to 320x568 ppi and up to whatever works best for the design.

[carodew]

Note – instead of creating a ton of columns in the kanban board, I instead added each phase as part of a checklist in the issue template. That seems more manageable and still fulfills the goal of making sure we consider each phase as we go (or make a conscious decision not to).

Got some feedback on the Definition of Done and will post it with some edits in the wiki

[carodew]

done!