Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Ten reasons that BDD won’t save your development process

Ten reasons that BDD won’t save your development process

(and a couple of ways it might help)

Steve Tooke

May 01, 2019
Tweet

More Decks by Steve Tooke

Other Decks in Technology

Transcript

  1. Ten reasons that BDD won’t save your development process (and

    a couple of ways it might help) Steve Tooke
 @tooky
  2. – Frederick P. Brooks, Jr There is no single development,

    in either technology or management technique, which by itself promises even one order-of-magnitude improvement within a decade in productivity, in reliability, in simplicity.
  3. – Gojko Adzic I am getting more and more convinced

    every day that communication is, in fact, what makes or breaks software projects. Programming tools, practices and methods are definitely important, but if the communication fails then the rest is just painting the corpse. Complex projects simply have no chance of success without effective communication.
  4. – Jessica Kerr In our symmathesy we need to grow

    the flow of mutual learning… we have to work with people who have different sets of knowledge
  5. – Seb Rose and Gáspár Nagy, The BDD Books -

    Discovery Discovery – a structured, collaborative activity that uses concrete examples to uncover the ambiguities and misunderstandings that traditionally derail software projects.
  6. Allocate booked seats Do not book more than 70% of

    seats in a carriage Don’t split bookings across carriages
  7. Allocate booked seats Do not book more than 70% of

    seats in a carriage Don’t split bookings across carriages
  8. Allocate booked seats Do not book more than 70% of

    seats in a carriage Don’t split bookings across carriages Book 2 seats
  9. Allocate booked seats Do not book more than 70% of

    seats in a carriage Don’t split bookings across carriages Book 2 seats Book 1 seats
  10. Allocate booked seats Do not book more than 70% of

    seats in a carriage Don’t split bookings across carriages Book 2 seats Book 3 seats Book 1 seats
  11. Allocate booked seats Ideally, do not book more than 70%

    of seats in a carriage Book 3 seats Don’t split bookings across carriages Don’t book more than 70% of the available seats on the train Book 2 seats Book 3 seats Book 1 seats
  12. Allocate booked seats Ideally, do not book more than 70%

    of seats in a carriage Book 3 seats Don’t split bookings across carriages Don’t book more than 70% of the available seats on the train Book 2 seats Is there a preference for choosing carriages when there is an option? Book 3 seats Book 1 seats
  13. Allocate booked seats Ideally, do not book more than 70%

    of seats in a carriage Book 3 seats Don’t split bookings across carriages Don’t book more than 70% of the available seats on the train Book 2 seats Is there a preference for choosing carriages when there is an option? Book 4 seats Book 3 seats Book 1 seats
  14. – Ron Jeffries and Chet Hendrickson Example-Based Planning, Building and

    Review to give the team, and all stakeholders full visibility into the outcomes of the team’s work using a consistent set of real working examples
  15. or

  16. Allocate booked seats Ideally, do not book more than 70%

    of seats in a carriage Book 3 seats Don’t split bookings across carriages Don’t book more than 70% of the available seats on the train Book 2 seats Is there a preference for choosing carriages when there is an option? Book 4 seats Book 3 seats Book 1 seats
  17. – Liz Keogh having conversations is more important than capturing

    conversations is more important than automating conversations