• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
JCN12 Behavior-Driven Development
 

JCN12 Behavior-Driven Development

on

  • 568 views

 

Statistics

Views

Total Views
568
Views on SlideShare
567
Embed Views
1

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 1

https://twitter.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    JCN12 Behavior-Driven Development JCN12 Behavior-Driven Development Presentation Transcript

    • INTRODUCING BDD with a happy end.© Aki Salmi, 2012 cc by-sa
    • Who am I
    • Who am I (cont)
    • Who am I (cont.)blipperinto agile since late 2006studying to be supervisoraki.salmi@iki.fi @aksalmi
    • Introducing BDDDoes it mean: BDD BasicsOR How I introduced BDD to my current company?
    • History2008 Acceptancetesting with RobotFramework2009 Acceptancetesting with Cucumber2010 first trials of usingcucumber to collaboratewith the customers. You can buy the book from http://pragprog.com/book/hwcuc/the-cucumber-book
    • Early spring 2011 @ Lindorff I started as Scrum Master for a team of 9. Weekly sprints. Mostly failing to deliver Agile coaches visiting us. Discussions. Every. Single. Morning. “What’s wrong with this all?”
    • I DID WHAT I WAS BEST AT...
    • NOTHING
    • NOTHINGto hinder development effort
    • Where to lead? formation matters
    • Personal Touchlive your dreamtransparencyempathy, careoptimism
    • Minor changesinformative workspace (big kanban wall)new acceptance testing tool easy way to introduce new processcloser cooperation with the business
    • The magic date 1.7.2011“This needs to be done - We require You to complete550 SP by end of this year”
    • Calculus 15SP / 2wk / team 2 teams Estimated total velocity 60SP / monthWork enough until mid- April 2012.
    • which resulted in...
    • “YOU NEED TO MAKE IT HAPPEN!” the business promised to help
    • The End?
    • Now it’s your call!BDD Basics Introducing change!
    • Walk side-by-sidebe always present, but not always visible
    • Feedback loops or how we learned about it
    • Ideas Features CodeMatt Wynne on Refuctoring Your Cukes http://skillsmatter.com/podcast/agile-testing/refuctoring-your-cukes
    • The processor how we experimented it.
    • Release BL
grooming Acceptance
 Criteria Executable
 UAT Specification defer designdemo & review decisions implementation Note: this did or did not work in our context!
    • Release backlog grooming always off-site
    • Dates
 BL AC ES WIP UAT Donehere ChangeSet #
    • Remember: BDD is not about tools!
    • Communicate plans and how we are progressing
    • Challenges we are facingYes, there are some.
    • Communicate plans so far away, no matter how close
    • Exploratory TestingA lot to learnSince for us it’s mostly…
    • ad-hoc testing... aiming to catch bugs flying around?
    • INSTEAD OF…
    • The Goal of ET1. Gain Understanding2. Force to exhibit it’s capabilities3. Find Bugs ref [5]
    • Feedback loopsor how we think about it now
    • Business Process (UAT) Feature (ET) Story (ET) Scenario tests builds TDD pairing
    • What made this possible?700525350 Linear extrapolation Expected progress w/ 100% linear growth175 Expected progress w/ aggressive growth Done + Approved 0 22.6 6.7 20.7 3.8 17.8 31.8 14.9 28.9 12.10 26.10 9.11 23.11 7.12 21.12 4.1. 18.1 1.2 15.2 29.2
    • Story of ‘550’
    • Say what you say - 6 words.
    • Luck,that is your best friend!
    • Sit together, talk together,smile together
    • Build Trust!And help them experiment
    • Thank you!Feedback appreciated!aki.salmi@iki.fi @aksalmi