Skip to content

Instantly share code, notes, and snippets.

@chadoh
Created December 18, 2019 19:15
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save chadoh/a8a123b889b6e740784e24fa42224134 to your computer and use it in GitHub Desktop.
Save chadoh/a8a123b889b6e740784e24fa42224134 to your computer and use it in GitHub Desktop.

Product workflow proposal

  1. someone has product/feature idea (probably Javi or Yalda, but could be anyone)

  2. record this idea in the product GitHub repo as an Epic

  3. Tech Lead goes through these raw ideas and adds rough ballpark pessimistic estimates

  4. Product Team sorts estimated epics into sprints

Before the sprint starts

  1. Tech Lead enumerates epics

    • creates prerequisite epics when original epic would take more than two weeks to complete
    • creates and estimates subtasks (does not assign them)
    • documents dependencies between subtasks ("subtask 1 must be worked before subtask 2 and 3; subtask 4 can be worked in parallel")
  2. Tech Lead alerts Product Team if the epics planned for the sprint are likely to take longer than hoped

  3. Tech Lead assigns Epic Leads for each epic for the upcoming sprint

  4. Epic Lead is responsible for

    • understanding epic at a high level
    • pushing back on Tech Lead if estimates seem inaccurate or problematic
    • organizing other engineers who work on it with them throughout the sprint
    • monitoring epic health and alerting Epic Lead / Product Team if it seems like there might be problems shipping in time

During the sprint

  1. Engineers initially focus on epics for which they're lead
  2. If finished with own epic or had none assigned, look at the board and figure out what to work on next. Grab a subtask, assign to self, move to In Progress, contact the Epic Lead or Tech Lead with any questions.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment