addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Lean Coffee

  • Mar 27, 2013 · 8:00 AM
  • This location is shown only to members

An opportunity to meet like minded Agile & Lean enthusiasts, to share experiences and learn from others.

Sydney Lean Coffee Blogs

The current Sydney Lean Coffee protocol:

  1. Everyone offers topics they are interested in discussing by writing them on index cards
  2. We vote on each of the topics to prioritise. You can vote for as many topics as you like but only once per topic.
  3. We discuss each topic in turn. Initially, ask the propose to explain the topic, then go round the table to give an opportunity for everyone to provide an initial comment, then open discussion.
  4. When the topic is done, we move on to the next one. Usually we defer to the topic proposer about when the topic is done. If someone disagrees, then s/he can raise a new topic. Typically we discuss 3 topics per Lean Coffee session.
  5. At the end of the overall Lean Coffee session, we run a quick retrospective. What did we like? What didn't we like? What are ideas for improvement?

Join or login to comment.

  • Murray G.

    Good conversation about breaking stories into tasks, when, why, benefits?

    1 · March 27, 2013

    • Peter L.

      Looks like those guys are having the exact same conversation we are having with similar points. Maybe the main thing is to accept both can be useful and focus on the value as opposed to the process. Burndowns aren't specific requirements in scrum anymore and tasks are just referred as work of various size or effort so the team can explain what needs to be done to get the b product increment done. They were changed in the last revision of scrum as they were implementation choices not framework items.

      1 · March 28, 2013

  • michael s.

    Was doing a little more reading on Critical Chain PM. Critical Chain Project management has nearly all the elements of Agile PM with a few minor exceptions. By implementing Agile you will be following most of the principles of Critical chain by default http://youtu.be/7Xf-waj23P8

    1 · March 27, 2013

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