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

  • Join Group
5 members, 6 messages added in the last 7 days
New MessagesSee All
  • Re: getting proper metrics out of Jira

    Hey Larry, The Jira API is nowhere near intuitive when it comes to mining flow data. However, take a look at the utility we created to help with that:

    daniel_vacanti 13 hours ago
  • Re: getting proper metrics out of Jira

    Oh, and if Go is more your thing, Actionable Agile have a tool that can extract cycle data for use with their tool that is open source:

    optilude 14 hours ago
  • Re: getting proper metrics out of Jira

    On 5 October 2015 at 21:54, Larry Maccherone larry@... ... It's not. https://github.com/optilude/jiraflow/tree/master/server/analysis contains two

    optilude 14 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

  • 2561
  • 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