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

VanDev: Frequent Releases - The Ultimate Risk Mitigation Strategy

  • Jul 16, 2009 · 7:00 PM
  • This location is shown only to members

In July we've lined up Owen Rogers of Pulse Energy to present on the benefits of making frequent releases. Part of the
Agile Manifesto is to
"Deliver working software frequently" but our intuition suggests that releasing too often will drown us in overhead. Join us as Owen shows us that we can structure our processes to minimize the overhead and realize astonishing benefits by releasing software frequently. Following the presentation we'll have a door prize draw, round-the-room introductions, and then open networking. This is a networking event so be sure to bring your business/contact cards and a story or two to share.
About the Presentation: "There are risks and costs to a program of action, but they are far less than the long-range risks and costs of comfortable inaction." - JFK Deploying software releases to production every week, every day or even many times per day seems crazy to most IT groups. However this is exactly what many of the highest traffic sites consistently do. In fact, frequent releases are a key competitive advantage for these companies precisely because, contrary to expectation, releasing frequently tends to reduce risk rather than elevate it. The processes, tools and technologies adopted by these teams represents a sea change in the software industry. This session highlights many ways in which frequent releases serves to reduce the risk of software systems and is, in many ways, a more conservative strategy than traditional longer release cycles.
About the Speaker:
Owen Rogers is a developer at
Pulse Energy, where his team has been deploying releases to production every week for the past year. He is formerly an Agile coach and consultant with
ThoughtWorks helping teams make the transition to Agile methods in Sweden, UK, India, China and Canada. He is a regular speaker at Agile conferences and is one of the organizers of
Agile Vancouver. He has been the project lead for a number of open source tools including CruiseControl.NET, dbdeploy.net and NMock.

Join or login to comment.

  • A former member
    A former member

    The presentation itself was well-delivered and raised interesting philosophical points but the ideas therein were only applicable to a small portion of the software realm. Nonetheless, the discussion afterward was worthwhile to attend.

    July 21, 2009

  • Casey

    I was thinking that a company doing a 3D game could automatically download a new GPU upgrade to computers using that new GPU and say this upgrade will function for 30 days, after that $.
    One would offer a switch to change between the old version and the new for comparison purposes during the 30 days.

    July 17, 2009

  • A former member
    A former member

    A bit long, great speaker! but I'd have preferred more specific examples and less theory.

    July 17, 2009

  • A former member
    A former member

    I thought Owen was a great speaker

    July 17, 2009

  • A former member
    A former member

    Great networking afterwards, lots of interesting people.

    July 17, 2009

  • A former member
    A former member

    It was a good talk but heavily theoretical. I hope there will be a follow-up by Owen to address practical aspects of frequent releases. It would be nice to know exactly what tools and processes his company uses to achieve weekly releases.

    July 17, 2009

  • Jason H.

    Moving from "ship at next major version" to "be able to ship anytime" requires rethinking some assumptions and some processes but the trade off for many software products is appears to be more feedback, more control, and a better model of the customers and the market. Doesn't a payoff require work? What are you afraid of?

    PDFTron Systems is looking for Jr Software Developers with C++ experience.

    July 17, 2009

  • A former member
    A former member

    It is a wonderful meeting, I know some companies have aggressive strategy to release software in daily base. It is also a good chance to know other people

    July 17, 2009

  • Joe

    Seems similar to open source's concept of release often. There are some advantages when working at a more abstract layer, a little more difficult when you are closer to the hardware layer since hardware can change and require different things for different hardware.

    July 16, 2009

  • Casey

    Ahhhhhhhh!
    Mitigation without Litigation!
    :)

    July 16, 2009

57 went

Voluntary Donation

CAD10.00 any time you like

This covers: Meetup Fees, Name Badges, Equipment (Video camera when/if enough is donated)

Payment is accepted using:

  • PayPal
  • Cash or check - “At a meeting via cash/check, or via paypal.

Refunds are not offered for this Meetup.

Our Sponsors

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