Process

process.md

Process

Prerequisites

1. Requirements.
   • Break it down into bite-sized pieces (bulletted lists are ideal).
   • Single source of truth (e.g., JIRA).
   • If not JIRA, add a link to the requirements in JIRA.
   • What device targets? (desktop, mobile/web, mobile app, etc.)
2. Assets (i.e., images, fonts).
   • Include Cloudinary URLs in the ticket.
   • Use issue links in JIRA (golden path).
3. Move tickets into the sprint before you ask a dev to work on it.

Progression

1. Create routes for site pages.
2. Page container layout. These are main high level content areas with no content in them at first. Grid system placements, columns, etc.
3. Add content (copy). Think basic HTML 1.0 forms and stuff. No styles whatsoever. It turns out, this is also very accessible.
4. Behavior. Button clicks, etc.
5. Style the page/components.

Note: You should be able to link tickets in JIRA as pre-requisites to other tickets.

Ticket hand-offs

1. Look for tickets in ToDo to pick up, obviously.
2. If requirements or assets are missing or unclear, drop a comment and kick the ticket back into ToDo. Tag the person who wrote the requirements and/or supplied the assets.
3. When done, send it to the next swimlane.
   • Do a soft hand-off, adding as many relevant details you can think of to the next party so they aren't blocked.
4. When a ticket moves from one swimlane to another, it could be useful to assign to ticket to another individual so they see it in their list of actionable tickets and doesn't lose tracking.