Monthly Archives: August 2010

FLAVE means more than just “visually outstanding”

Some acronyms are actually useful for remembering models or concepts. Lately, it seems that teams could use some help remembering some of the core principles of Kanban, so I’ll offer up my own acronym to help myself as much as anyone else: FLAVE.

The software-development world needs another acronym like it needs another methodology. Yet, if you’re anything like me — someone who loathes acronyms, by the way — you find that some acronyms are actually useful for remembering models or concepts (for instance, it’s easy to recall all of the elements of Bill Wake’s INVEST when creating stories).

Lately, it seems that teams could use some help remembering some of the core principles of Kanban, so I’ll offer up my own acronym to help myself as much as anyone else (definitions taken from David Anderson):

  • F

    Measure and manage Flow: Track work items to see if they are proceeding at a steady, even pace.

  • L

    Limit work-in-progress: Set agreed-upon limits to how many work items are in progress at a time.

  • A

    Adapt the process: Adapt the process using ideas from Systems Thinking, W.E. Deming, etc.

  • V

    Visualize the workflow: Represent the work items and the workflow on a card wall or electronic board.

  • E

    Make process policies Explicit: Agree upon and post policies about how work will be handled.

The concepts aren’t in any particular order, except to create the acronym word. What, FLAVE isn’t a word? This guy just doesn’t know how to spell it.

Advertisements

Leave a comment

Filed under kanban