Skip to content
← TechEd BoF Session Proposals Voting

Give your votes to session proposals (New proposals will not be taken into the BoF content voting) Vote until October 28th!

TechEd BoF Session Proposals Voting

Categories

(thinking…)

Behaviour Driven Development In The Enterprise

In the majority of enterprises, the development effort is focused upon "value" to be delivered to the various consumers of that development effort. This can be captured as the behaviours to be exhibited by the application in the ubiquitous Given When Then language of Behaviour Driven Development.

BDD is a relative newcomer to our ever-growing collection of three letter acronyms. This session will be a discussion of some of the benefits and issues in implementing it in the enterprise. Such as:

What benefits do we see from "defining done"?
Who writes these features & scenarios?
Are the features/scenarios "living" documents?
What tools exist to facilitate the process?

117 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
AdminINETA Europe (INETA Europe VP, INETA Europe) shared this idea  ·   ·  Report…  ·  Admin →

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Anonymous commented  ·   ·  Report

    Have fun at the conference, but hey, I could easily listen to you singing to the kids too. Hugs, Terry

  • Andy Caddy commented  ·   ·  Report

    If you get this I have some advice about how to getthe right people along for your session.

  • James Easton commented  ·   ·  Report

    To expand on Lances point, from an Infrastructure point of view, to often development doesn't look at what we are current doing or using. A real life example would be that a development piece was done and an SSL cert was required. Rather than looking at our current environment, new SSL certs were created. As a result, work was required to implement the new cert and management going forward, where we could have used the current cert. This ended up as additonal work and management cos the question wasn't asked during the development stage.

    Another consideration would be that if your developement does require infrastruture changes, how long would it take to do this work and when should infrastructure be notified.

  • lance wantenaar commented  ·   ·  Report

    How much security good practice is built into the design? Too many times functionality preceeds this and you then have to fix something after the fact.

  • Steve Wyllie commented  ·   ·  Report

    BDD is a flavour of the old 'V model' approach to development and testing, which starts with each requirement being testable. However, there's real skill (and typically years of experience needed) to define a complete set of requirements that are testable, so I'd suggest you bring along Heath, if possible.

    I'd also ask for you to pay close attention to non-functional requirements (eg response times, confidentiality, etc.) It's a fairly serious gap in our current approach to development and testing.

  • Lyn. commented  ·   ·  Report

    Sounds interesting. Should provoke a lot of discussion.

  • James Mackay commented  ·   ·  Report

    A language that can finally integrate techies with the people who actually want IT systems to do things. That sounds like gold dust.......and gets my vote.