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-circleimageimagesinstagramlinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

50 Shades of Behavior Driven Development

From a software developer’s point of view, come join us for a pop-culture, restaurant and fast food referencing presentation that utilizes behavior driven development to address some of the problems we still face in an agile world.

So your team has made the transition to agile and your work is broken down into user stories. It makes perfect sense to break work down into smaller chunks, but now you're running into problems with estimation and communication. Your team is delivering value but it’s been discovered that user stories are thrashing through the analysis, development and QA processes. What is going on here?

Come a software development process with a deceiving name: behavior driven development. Behavior driven development (BDD) is a process that captures how a software system functions with sets of acceptance criteria. From a developer’s perspective this appears to be test driven development at a higher level with potential automation of those tests. However, if you take a step back and look at the bigger picture, it’s about functioning better as a team to deliver value to your clients.

We will take a look at the process of gathering standardized acceptance criteria from the perspective of the four main stakeholders in a project: the product owner, analyst, developer and QA. Teams involving more stakeholders in the grooming process can experience increased collaboration and better communication. User story estimations can be more accurate and domain specific knowledge and terminology become ubiquitous as user stories move through the development cycle. Standard terminology propagates into software and creates living documentation within the code base. Software developers have increased productivity while creating leaner and better software with the process of TDD. These are a few advantages to BDD and there are more to explore. There are no silver bullets to anything so we will also address the disadvantages as well.

About the Speaker

Richard Yu is a software developer who has been developing software for 8 years. Writing code is a passion, but he also likes to examine some of the social and non-technical aspects of the software development process. He believes that presentations should be informative, engaging and entertaining by utilizing unorthodox approaches when relaying concepts. He currently is employed as a software developer at Robert W. Baird and Company and can be found on twitter @richard_yu.

Please Note: This event is not at the Miller Inn! We will be downtown at Robert W Baird to accommodate a larger audience.

Milwaukee Agile is geared toward both experienced and brand new practitioners. The pizza is sponsored by Redpoint Technologies. Soft drinks, water and the space is sponsored by Robert W. Baird.

Join or login to comment.

  • Mike L.

    Great Meetup. I learned a lot. Thank You.

    February 15, 2013

  • Carl S.

    In case you missed it, a recording of the presentation was posted on YouTube @ http://youtu.be/b70zSQdXWC8

    2 · February 14, 2013

  • Richard Y.

    Great venue and great audience. Thanks everyone for coming out!

    2 · February 13, 2013

  • Dodie K.

    Richard did a great job of keeping the material informative, instructive and entertaining. Great content, efficiently presented and memorable.

    February 13, 2013

  • Dan M.

    Excellent, doing a write-up now for work....

    February 12, 2013

  • Todd N.

    Typically, our presenters start around 6:15 and we're wrapped up by around 7:15. People hang around to network but the formal talk should be over well before 8.

    February 12, 2013

  • Dan M.

    Do we have an estimate of the length of the presentation? 6PM - 8PM? Thanks- Looking forward to it...

    February 12, 2013

  • Carl S.

    IMPORTANT: Do your best to arrive before 5:45pm. The US Bank Building becomes significantly more locked down at 6pm. Details Below.

    The only two entrances to the US Bank Building that are open after 6pm are 1) Cass Street (accessed through the Michigan St. Level) and 2) through the US Bank parking structure (unlocked until 7pm). The elevators will lock at 6pm and will need an employee badge to get to the Galleria floor (where the Vandenberg Room is located).

    Exact location for everyone's convenience:

    Robert W. Baird
    Vandenberg Room – Galleria Level
    777 East Wisconsin Avenue
    Milwaukee, WI 53202

    February 10, 2013

  • Bruce W.

    Looking forward to another good event

    1 · February 2, 2013

  • Brad P.

    Sorry I can't make it, I have my annual eye checkup that takes months to schedule. Maybe they should consider agile/lean concepts ;)

    January 31, 2013

  • Mike L.

    Looking forward to this.

    January 31, 2013

  • Christine D.

    Looking forward to it.

    January 30, 2013

  • Alex A.

    Looking forward on learning how to make my world better.

    January 28, 2013

Our Sponsors

  • Robert W. Baird

    Baird provides organization, a location, and refreshments for meetups.

  • NVISIA

    NVISIA provides food for the sessions and organization assistance.

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