Flow

A Flow lays its Items out along several Lanes. The Lane Columns form a narrow band whose width is the number of Lanes times --toki-lane-gap, and every Card and Meta lines up in one column outside that band. The attributes below are the output of flowAttributes(), written by hand as a plain HTML author would.

One Lane

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Plan

    The plan is checked against the budget.

  3. Launch

    The first stable version ships.

Fork and Join

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

    The notes are folded into the plan.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Reuse a freed column

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Spike

    A short experiment checks an idea before it is scheduled.

  3. Decide

    The experiment joins the main Lane after this event.

  4. Prototype

    The freed column is reused by the next side Lane.

  5. Review

    The prototype joins the main Lane after this event.

  6. Launch

    The first stable version ships.

Four Lanes at once

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Lane a

    The first side Lane starts.

  3. Lane b

    The second side Lane starts.

  4. Lane c

    The third side Lane starts, so four Lanes run at once.

  5. Lane a ends

    The first side Lane is finished.

  6. Lane b ends

    The second side Lane is finished.

  7. Lane c ends

    The third side Lane is finished.

  8. Launch

    The first stable version ships.

One color per Lane

  1. Kickoff

    The main Lane gets the first color.

  2. Lane a

    The second Lane gets the second color.

  3. Lane b

    The third Lane gets the third color.

  4. Lane c

    The fourth Lane gets the fourth color.

  5. Lane a ends

    The Marker keeps the color of its Lane.

  6. Lane b ends

    The Marker keeps the color of its Lane.

  7. Lane c ends

    The Marker keeps the color of its Lane.

  8. Launch

    The main Lane keeps its first color to the end.

Side start

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Alternate is drawn as Side end

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Default colors and gaps

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Fold it back

    The feature joins the main Lane after this event.

  4. Launch

    The first stable version ships.

Milestone in a Flow

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    The milestone Marker still leaves room for the Fork's bend.

  3. Fold it back

    The feature joins the main Lane after this event.

  4. Launch

    The first stable version ships.

A Flow in a Card

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Fold it back

    The feature joins the main Lane after this event.

    1. Nested Flow

      A Flow inside a Card starts from its own attributes.

  4. Launch

    The first stable version ships.

Horizontal Fork and Join

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

    The notes are folded into the plan.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Horizontal, four Lanes at once

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Lane a

    The first side Lane starts.

  3. Lane b

    The second side Lane starts.

  4. Lane c

    The third side Lane starts, so four Lanes run at once.

  5. Lane a ends

    The first side Lane is finished.

  6. Lane b ends

    The second side Lane is finished.

  7. Lane c ends

    The third side Lane is finished.

  8. Launch

    The first stable version ships.

Horizontal, collapsed on Side end

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

    The notes are folded into the plan.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Horizontal, collapsed on Side start

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Horizontal, Alternate is drawn as Side end

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.

Horizontal, right to left

  1. Kickoff

    The team agrees on the goals and the first milestones.

  2. Draft the feature

    A smaller group starts on the feature while the main work goes on.

  3. Review

    Early users try the feature and send their feedback.

  4. Fold it back

    The feature joins the main Lane after this event.

  5. Launch

    The first stable version ships.