addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-crosscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartrashtriangle-downtriangle-uptwitteruseryahoo

Meet using the Lean Coffee format (http://leancoffee.o­rg/).

Focus is on Lean & Kanban for Software Development, IT and knowledge work. Open to other groups and complementary ideas. The goal of the group is to bring the value that Lean and Kanban offers to Wellington organisations by building a community with knowledge and experience to share.

Join or login to comment.

  • Julian A.

    Some good discussions and insightful first-hand knowledge of situations and experiences.

    June 27, 2013

  • Paul S.

    2. Contracts - what does a lean contract look like.
    Below are some ideas around how to structure the relationship with a client when trying to work in a lean way:
    Agile contracts - fixed price - limited committed scope.
    Fixed price / fixed scope - how to deal with this.

    At a corporate level there are some key things that need to be achieved.
    Put the contracts around those core things rather than specifying the detail.

    Outcome based contracts.

    List the application of the high level features.

    Estimate based on actual cost of similar projects
    Break the project into smaller chunks (quarterly) with reviews at the delivery points
    Beyond Budgeting.
    Give them more options.
    Training for finance / legal / procurement - how to create agile friendly contracts.

    June 26, 2013

  • Paul S.

    Lean Coffee[masked]

    Some of the topics discussed at the Lean Coffee on the 25/6 are:

    1. Do we have examples of other ways of visualising knowledge work aside from the standard Kanban board?

    This discussion split into to areas. For work in progress usually a Kanban board designed to match your workflow does a good job.

    The second area was regarding visualizing the backlog / ideas area.
    This could be done using :
    Story Mapping. - Depth and Breadth
    Value Tree Backlog

    Visualizing the backlog is not core lean - but done well could communicate remaining work effort to stakeholders.

    June 26, 2013

7 went

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy