Loading ...
Sorry, an error occurred while loading the content.
  • Back
  • About Group

  • Join Group
53 messages added in the last 7 days
New MessagesSee All
  • Re: Timeboxes in Kanban

    I come to a different definition of a timebox. For example, a pomodoro is a time box. I can still be doing single-piece flow in conjunction with that, no

    agileschools 3 hours ago
  • Re: Timeboxes in Kanban

    Timebox for me is more to do with having regular cadence. E.g. If a sprint is 2 weeks and at the end of every sprint , I deliver to production. So I build all

    hrishi_karekar 4 hours ago
  • Re: Timeboxes in Kanban

    Hi Mike - Thanks for clarifying and confirming my thought that your focus was on "sets of work items". Probably little value in debating the semantics of all

    amaeze77 5 hours ago
Fetching Sponsored Content...

Group Description

This group discusses the use of The Kanban Method to drive change in technology businesses, as defined in David J. Anderson's book, "Kanban - Successful Evolutionary Change for your Technology Business"


The Kanban Method was first described by David Anderson in 2007. Since then many have adopted it and reported successful implementations. This group aims to help current practitioners. New members are recommended to visit the Limited WIP Society, where a list of useful resources can be found, including relevant blogs and published articles.


David Anderson has defined the Kanban Method as

First follow the foundational principles


  • Start with what you do now
  • Agree to pursue incremental, evolutionary change
  • Initially, respect current roles, responsibilities & job titles

then adopt the core practices

  1. Visualize
  2. Limit WIP
  3. Manage Flow
  4. Make Process Policies Explicit
  5. Implement Feedback Loops
  6. Improve Collaboratively, Evolve Experimentally (using models/scientific method)


It is not expected that implementations adopt all six practices initially. Partial implementations are referred to as "shallow" with the expectation that they gradually increase in depth as more practices are adopted and implemented with greater capability.


Members are encouraged to focus on inquiry, dialogue, ideas and understanding, rather than advocacy, argument, individuals and defensiveness, and asked to keep posts relevant to Kanban. Thanks


We want to maintain a very high signal to noise ratio on this list. As such, announcements and commercial posting will not be tolerated unless they are from regular contributors, and specifically about a Kanban related topic.

Group Information

  • 2542
  • Other
  • Aug 20, 2007
  • English

Group Settings

  • This is a restricted group.
  • Attachments are permitted.
  • Members cannot hide email address.
  • Listed in Yahoo Groups directory.
  • Membership requires approval.
  • Messages from new members require approval.
  • All members can post messages.

Message History