Collaboration/Team/Processes/Project management

The Flow team has been using Mingle, but is considering changing to Trello.

items
Tasks and bugs can have a related story and then appear on that story card.
 * stories
 * tasks (mainly Oliver and quiddity)
 * bugs (automatically loaded from bugzilla)

Status lanes
Ready for Analysis - In Design - Ready for Development - In Development - Awaiting Final Code Review - In Testing - Accepted

Only cards

 * No relation between them, though a checklist can reference card #NNN
 * Multiple checklists per card
 * Main one is Acceptance criteria
 * Could have a design checklist


 * Can assign people to cards, but can't assign people to checklist
 * Six colors of cards
 * Design, BA/CL, Engineering, Bug ?
 * Echo had: Testing/Deployment (brown) - Bugs (red) - Interface Design (purple) - Front-end Development (blue) - Back-end/Queuing Development (yellowy-green) - Product Management (green)

Status lanes
Default Trello columns are
 * To Do - Doing - Done

could add Backlog We could duplicate Mingle's lanes, but moving cards around is busywork that developers forget to do. Patches merged in gerrit is what matters.

Echo had
 * Backlog - Product Management - Design in Progress - Dev Ready - In Development - Needs Code Review - Ready to Deply - Deployed - Done

Multiple boards
Instead of unwieldy Backlog column (hundreds of items) we could have a separate Flow backlog board.

Mobile has a board per iteration