Skip to main content

Full Day Workshop: BDD with Cynefin - Liz Keogh


What: Full Day Workshop: BDD with Cynefin - Liz Keogh

When: Wednesday, February 7, 2018, 9:00am to 4:45pm

Where: The King's Centre, King Street, Norwich, NR1 1PH

How much: £130.00

RSVP: https://www.meetup.com/Norfolk-Developers-NorDev/events/245781564/

Behaviour-Driven Development is a practice in which we talk through different examples (scenarios) of how a system might work, from the perspective of its many users. In this unique tutorial we mix BDD with Cynefin, the sensemaking framework that helps makes sense of the world around you and the problems you encounter depending on their predictability.

The course provides thinking and conversational tools to enable teams, product owners and managers to address risk early, develop a deep understanding of requirements at different scales, shorten the time needed to reach that understanding, produce high-quality, innovative solutions, and create human-readable, relevant and memorable tests as a by-product… and it's not just applicable to software!

For each outcome, attendees will demonstrate the skill during interactive exercises in the course.

BDD

  • Explain BDD and its practices
  • Create well-formed scenarios which are relevant to your own domain
  • Use conversational patterns to draw out new scenarios and explore scope
  • Discuss how best to engage Developers, Testers and Analysts or Business Experts in conversations
  • Identify and design mechanisms for quick feedback using single scenarios


Cynefin

  • Explain the Cynefin model and how it relates to BDD and Specification by Example
  • Estimate the level of complexity in different requirements phrased at different scales
  • Predict when an unelaborated requirement is likely to cause conflict or excessive discussion
  • Discuss shortcuts to apply to well-understood requirements to reduce analysis and planning time
  • Differentiate between well-understood, domain-specific, and innovative / uncertain aspects of work through using scenarios in conversations


Capability Red

  • Identify core and incidental stakeholders for a project
  • Generate a map of desired capabilities from lower-level stories and scenarios
  • Identify risk and uncertainty in capability maps
  • Discuss prioritization of long-term plans accordingly
  • Decide whether to engage stakeholders before or only after implementation (educators vs. gatekeepers / checklist)
  • Phrase capability-level problems in problem-space language, without diving into solution-focused features
  • Identify continuous capabilities to which BDD can be applied using monitoring (non-functionals and other non-discrete requirements)
  • Discuss monitoring mechanisms, including manual processes and compliance / governance where applicable.

Please note that automation of scenarios will be mentioned in this course, but is out of scope; this course focuses on the conversational and analytical aspects of BDD.




Comments

Popular posts from this blog

I, Robot

The Foundation series has been my go to for a good, enjoyable read over the last two years, so naturally I moved on to Asimov’s Robot series afterwards. However, the short stories in I, Robot were mostly a disappointment. They feel self indulgent, with too much philosophy and science, Asimov showing off, and not enough story. The most enjoyable moments come from the stories featuring Gregory Powell and Mike Donovan. Their banter and the relationship between them provide some much needed amusement and were easily the highlight of the book for me. However, it did give me food for thought for the current potential issues with the rapid development of AI at the moment, and the many concerns around safety. I wonder if all we need is: An AI may not injure a human being or, through inaction, allow a human being to come to harm. An AI must obey the orders given it by human beings except where such orders would conflict with the First Law. An AI must protect its own existence as long as such p...

It's great to be back at the ACCU Conference 2025!

Last week I was back at the ACCU Conference in Bristol, for the first time since I gave an opening keynote in 2019 . In March 2020, COVID hit the UK and I got out of the habit of attending and speaking at conferences. Plus the ACCU Conference, and the organisation in general, took a big step back towards C++ and that hasn’t been relevant to me for nearly two decades. It’s taken until now, 2025 for me to want to talk again, and I was really pleased to be accepted for the ACCU Conference again. It was just a 20 minute session and I only attended for the day I was speaking. There was enough varied content for it to be interesting to me and I’m hoping to be back for the full conference next year. I really enjoyed attending and it was great to catch up with people I hadn’t seen for years. I felt re-engaged and particularly liked being asked if I’d been to nor(DEV):con . Learning to stop writing code (and why you won't miss it) Daisy Hollman I should have read the summary of the openin...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...