Skip to content

Instantly share code, notes, and snippets.

@trinonsense
Created May 15, 2014 22:28
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 trinonsense/96ab9dd442539d526939 to your computer and use it in GitHub Desktop.
Save trinonsense/96ab9dd442539d526939 to your computer and use it in GitHub Desktop.
Reviewing project collaboratively before elaboration and development

Project Review

goals

  • collaborative, iterative, and continuous project cycle with marketing, product, and design
  • context!
    • feature context
    • technical context
  • benefits:
    • for development and design team: comprehensive context to use in elaboration for more accurate stories and estimations
    • for product and marketing team: shorter feedback loop of project discussions from development and design team to create better business strategies and quicker business decisions for the product

format

  • review project documents and project Trello board notes
  • deep dive of each feature of the project
  • open format discussion
  • general technical implementation
  • place discussion notes on project Trello board
  • weekly meeting until teams feel comfortable with discussed project context
  • optional meeting, but encouraged for team members to rotate in and out
  • individually review project before team review
  • invite product team member, if needed
  • invite design team member, if needed
  • invite marketing team member, if needed

caveats

  • we're not elaborating, no stories
  • don't get too detailed: technical, feature, or design
  • prepare for features to be taken out or added in or modified
  • nothing is final
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment