Specification by Examples - Writing executable specification

This is a workshop to build product while practicing impact mapping, feature writing, specification by examples and applying test first approach. Workshop will practices that will help in translating product vision to product increment and living documents. Facilitator will demonstrate how to convert specifications in code by using test first approach.​​ Facilitator will help in crafting product vision, coming up with product features, how to write examples for features and use examples to write production code. Session will demonstrate how to convert specification into product increment, living documents and build test automation.

 
1 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Introduction

What is product

Preparing initial product backlog by impact mapping (Hands-on sessions for participants)

Splitting features into smaller stories (Hands-on session for participants)

Writing examples for stories (Hands-on session for participants)

Converting examples into test using tools (Demo by facilitator)

Writing code to satisfy tests (Demo by facilitator)

Importance of living documents 

Q&A

Learning Outcome

Learn how to prepare product backlog from product vision

Learn to how to split features 

Learn how to write examples for specification

Learn how to generate test out of examples

Learn to prepare living documents

Target Audience

Everyone

schedule Submitted 7 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  6 months ago
    reply Reply

    Hi Naveen,

       Thanks for the submission. This looks pretty introductory though you mark it as intermediate.  What am I missing that makes this intermediate?  

    In the past, there have been BDD sessions at Agile India - even led by Aslok - which I believe, if I recall correctly, were lightly attended. I'm concerned that even if this session were great, it would follow similar fates.  What is your experience?

    Best,

    Joel

    • Naveen Kumar Singh
      By Naveen Kumar Singh  ~  6 months ago
      reply Reply

      Hi Joel,

      It was suppose to be a beginner so changed it. Regarding attendance, not sure why people didn't attend Aslok workshop. But I presented this in Global Scrum Gathering this year and room was full and people were standing even.

      Naveen  


  • Liked Satisha Venkataramaiah
    keyboard_arrow_down

    Extended Impact Mapping: Identifying the real problems that your product should solve.

    Satisha Venkataramaiah
    Satisha Venkataramaiah
    schedule 7 months ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    People are the reasons why we build Products. Products are meant to solve a problem for the people. For example, if we are building a Car-pooling application in Bengaluru, we are trying to solve the problem of traffic jams. The car-pooling app won’t solve that problem but people do. The car-pooling app has to address the constraint that people face in pooling the car. One of the reasons why people may not car pool could be the issue of safety. If car-pooling app can’t address it people don’t car pool and vision can’t be achieved. Extended impact-mapping helps in understanding those constraints to help Product teams in helping the products features to address those constraints.

     

  • Liked Satisha Venkataramaiah
    keyboard_arrow_down

    Change Canvas – A technique to create a Shared Need for Organization Agility

    Satisha Venkataramaiah
    Satisha Venkataramaiah
    schedule 7 months ago
    Sold Out!
    90 mins
    Workshop
    Advanced

    If someone says we want to adopt Scrum or some other framework, there is always a problem that Scrum can solve for them. Many a time, people at the helm of helping Organizations solve that problem lose the focus on the problem and Scrum becomes their main goal. Change Canvas is a way to help everyone involved in Organization transformation stay focused on solving the underlying problem that Organization thought Scrum could solve. This technique uses 5 HOWs, Change mapping and Contributor Quadrant to build the canvas. This helps in using Scrum as an Organizational transformation framework rather than just a delivery framework. 

    In this 90-minute workshop, Satisha will help you build a Canvas for your problem.