addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrosseditemptyheartfacebookfolderfullheartglobegmailgoogleimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Jun/2014 - Open Space


7:00pm - Food

7:30pm - Generate topics and schedule

8:00pm - Breakout to topic sessions

10:00pm - End

We welcome contributions of drinks and snacks! =)

What is Open Space?

Open Space is a highly collaborative and self-organized meeting where the participants themselves create the agenda and make it happen on the spot. Some of the past topics includes:

- You have scope, budget and delivery date, can I be agile? 
- Critical paths and outside dependencies 
- Effective Retrospective 
- How do you hire a ScrumMaster?
- How to keep retrospective interesting?
- Incentives and encouraging better engineering practices
- Spotify engineering culture video

Getting There

You may look at the following pdf for more information:

Join or login to comment.

  • Farid B.

    Hi everyone. Here are the topics proposed in this meetup:
    - Agile planning?
    - Acceptance testing for your Javascript front-ends, integration in build systems
    - Managing business expectations in cost cutting environment
    - What is a successful SCRUM team?
    - How management can support a team
    - Back to the roots: Complexity + Agile
    - Documentation: Outdated and lacking
    - Modifications to ideal Agile/SCRUM
    - Application Lifecycle Management
    - Factors affecting agile and what to do about them
    - Question of trust
    - PSM vs CSM

    July 7, 2014

  • Douglas H.

    Thanks for your suggestions regarding our need for a simple plan. I drew up up a plan highlighting the macro TODOs of bugs fixes, new features and process improvements. During review, the process improvements were deleted from the plan. If I wanted, I was told, I could put them on my own plan. Should I bother, or should I realign my values with the measures of management?

    July 3, 2014

    • Ng Pan W.

      Hi Douglas, the fact that you now know your manager's opinion on the improvement tasks is a good step. Having a backlog is good first step. The next step is to prioritize the work. Improvement tasks can be prioritized separately by asking, "If we do things differently, can we achieve more?" or "I would be more productive if ...", The team can collaboratively decide how the improvements should be prioritized. However, one should not get carried away with improvements. It should not take up more than 10-20% of your capacity. Instead prioritizing improvements against product enhancements and bug fixes, we prioritize within allocated capacity. Thus, you have 80% capacity for you to do your product related stuff (new features and bugs), 10-20% for other stuff (i.e. improvements). It is much easier to agree on capacity allocations as opposed to individual items in the backlog.

      July 3, 2014

    • Douglas H.

      Thanks Pan Wei! Those are nice rules of thumb to get us started.

      July 3, 2014

  • Pardha

    it was wonderful conversation, thank you Stanly without you open space woudln't there so long..

    1 · July 2, 2014

    • Stanly L.

      Without passionate people like you the Open Space wouldn't be there for so long. =)

      July 3, 2014

  • Etienne

    Thank you Edward for the help and suggestions! :) I settled on CasperJS with Mocha and Chai for my acceptance tests (I'm already using the last two for unit tests). I can now do ATDD with CoffeeScript! :D

    The pieces:
    - CasperJS
    - PhantomJS
    - mocha-casperjs
    - casper-chai

    July 2, 2014

  • Ng Pan W.

    Thanks Farid for leading the session!

    July 2, 2014

  • Mikey C.

    To augment my session on complexity theory and agile, here is one example article that illustrates the relationship between the two (Scrum in particular): (apologies for the need to register if you want to read the whole article). Principles and methods have been borrowed from complexity theory throughout the history of agile and lean, sometimes explicitly and sometimes without knowing.

    Here is also a quick intro video into one of the theories of complexity I mentioned (it's called the Cynefin framework):

    There is also a good article that made the cover of the Harvard Business Review on the same framework and how to apply some of its principles in practice at

    2 · July 1, 2014

    • Ng Pan W.

      It is always good to be supported by a strong theoretical foundation. Thanks for sharing! This (complexity theory) should be something to look into. Agile development borrows heavily from management and social sciences, where sense-making (a.k.a. theory-building) are something which consultants have to be equipped with.

      July 2, 2014

  • GinNee T.

    Interesting session

    July 1, 2014

  • Andrew L.

    Hi, I am looking for an IT company or a freelance IT engineer to develop Real Estate Marketplace portal. Pls email me at andrewlim.icomtech@g­

    June 26, 2014

29 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