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

Adapting your Software for Social Distancing by remote BDD with example mapping

Adapting your Software for Social Distancing by remote BDD with example mapping

The current situation in the light of the impact of COVID-19 on the world is unprecedented. While the first priority should remain people’s health and well-being, there are also many challenges to face regarding the economic impact, business continuity and security.

Sharing knowledge is within Xebia’s DNA. And during these challenging times, it is even more important to give something away in order to achieve a bigger goal. That is why we are setting up a series of free webinars to share best practices and give concrete guidelines as an answer to current business questions.

Even though some governments around the world are slowly starting to relax their Corona-related measures, one thing is here to stay: social distancing. This poses all kinds of novel challenges for companies. In this Webinar, we will show you the power of Behaviour-Driven Development and how it can, when combined with Example Mapping, help you to come up with creative solutions to implement this new constraint.

Since we are living in a digital world, most of these businesses will require to change their software for social distancing. Also, these businesses are now discovering how to effectively work remotely. So how can we change our software quickly, timely and reliably to adjust to the new social distancing rules? There are plenty of scenarios that we could think of; how do we know what will work and what not?

Join us in a live remote Example Mapping exercise to showcase how Behaviour-Driven Development with the help of Example Mapping makes you discover and formalise examples and eventually acceptance criteria. We will start with a quick introduction of Behaviour-Driven Development and Example Mapping, followed by a live & remote Example Mapping session. We end the webinar with a number of heuristics and by making the link between BDD and DDD (Domain-Driven Design); one of the methodologies that you can use to create flexible and highly adaptive software.

Kenny Baas-Schwegler

May 01, 2020
Tweet

More Decks by Kenny Baas-Schwegler

Other Decks in Technology

Transcript

  1. Adapting your Software for Social Distancing @kenny_baas by remote BDD

    with example mapping Photo by trail on Unsplash
  2. What are we going to do today? @kenny_baas • State

    of software delivery • Intro into BDD • Dive into our domain by explaining Example Mapping • Live Example Mapping for social distancing • Questions Photo by trail on Unsplash
  3. 6 @kenny_baas Feature Factory: When a software developer friend complained

    that he was “just sitting in the factory, cranking out features, and sending them down the line.” - John Cutler https://cutle.fish/blog/12-signs-youre-working-in-a-feature-factory
  4. 10 It is not the domain experts knowledge that goes

    to production, it is the assumption of the developers that goes to production - Alberto Brandolini @kenny_baas
  5. 13 Stories help you ask the right questions about the

    context and reason for the request. The important part is not about the words on the card but the shared understanding developed in the team. - Seb Rose @kenny_baas https://cucumber.io/blog/bdd/user-stories-are-not-the-same-as-features/
  6. Visualise examples When working remote, use images from the web

    or prepare upfront. Photo by Rifqi Ali Ridho on Unsplash @kenny_baas
  7. Heuristics: @kenny_baas Photo by trail on Unsplash • For remote,

    break and move for at least 2 minutes every 20 min. • Everyone can write down Gherkin, then discuss with the team • Always write down Gherkin, however you don’t need to automate them.
  8. Heuristics: @kenny_baas Photo by trail on Unsplash • Visualise examples

    • Write down examples of intention, not implementation • When working remote, prepare images or visualisations upfront • Write down any future wishes on a red sticky • For domain concepts use the white sticky • Start with a dedicated facilitator • Split business rule above three examples • Use a maximum of 20 minutes per story • Split the story on business rule • For remote, break every 20 min at least 2 min for movement • Everyone can formalise to Gherkin, then share with the team • Always write down Gherkin, however you don’t need to automate them https://www.dddheuristics.com/example-mapping/