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
 * 11am kick-off meeting for the iteration
 * Establish all items ready for development in this iteration, so engineers can work on them.


 * Tu
 * 4:25pm Standup meeting


 * W
 * Th
 * 10:30am Standup meeting


 * F


 * M
 * 10:30am Standup meeting


 * Tu
 * 4:25pm Standup meeting


 * W
 * 11am Story review and estimation (just like Mobile)


 * Th
 * 10:30am Standup meeting


 * F
 * 11am Iteration retrospective - so we can improve on the next
 * con$ultant's take: what to start doing, what to stop doing, what to continue]

For now we are skipping the big 'A' Agile sprint review where the team shows off work and talks to customers. Our stakeholders should be trying out all the time.

Do we need a meeting around the end of the iteration for official acceptance based on acceptance criteria? I don't think so, but Mobile has a Design/QA Acceptance meeting of the PM and QA on the following Monday "so we have more time to get code reviews completed."

Quarterly planning and review

 * Flow/Release planning (November 2013)
 * Metrics and activities meetings/Quarterly reviews/Core features/February 2014