Collaboration/Team/Meetings

Two-week cycle
We work on two-week iterations, at the end of which we deliver a potentially-shippable improvement to Flow.


 * Monday
 * kick-off meeting for the iteration
 * Establish all items ready for development in this iteration, so engineers can work on them.


 * Tu
 * W
 * Th
 * F


 * M
 * Tu
 * W
 * Th
 * F

At the end of this two-week period, we need to have some subset of:
 * Iteration review (show off work, talk to customers) con$ultant's take
 * Design/QA acceptance review meeting (engineers, Product manager Maryana and a designer) accept each story based on acceptance criteria in Mingle.
 * a retrospective so we can improve. con$ultant's take: what to start doing, what to stop doing, what to continue

At some point Maryana and others need to prioritize and refine stories for next sprint. Mobile does this on the first Wednesday

At some point engineers need to estimate upcoming stories. Mobile has a "story review and estimation" meeting on the second Wednesday.

Perhaps we need a meeting around the end of the iteration for official acceptance. Mobile has a Design/QA Acceptance for the PM and QA on the following Monday "so we have more time to get code reviews completed "

Quarterly planning
...