Scrum + Behavior Driven Development (BDD) - Colombo
Download as PPTX, PDF5 likes1,996 views
This document discusses how to integrate Scrum and Behavior Driven Development (BDD). It recommends starting with refining the product backlog by splitting user stories, defining acceptance criteria through examples, and collaborating with stakeholders. Examples show how to write specifications using the Given-When-Then format. The document emphasizes starting each sprint by writing automated tests based on the specifications before writing code. This ensures the team builds the right product by focusing on delivering value through small, testable increments.
Scrum + Behavior Driven Development (BDD) - Colombo
- 1. SCRUM + BEHAVIOR DRIVEN DEVELOPMENT Naveen Kumar Singh @naveenhome
- 2. ABOUT ME 20 Years of experience in Software Development. Scrum and XP coach. Love talking about scaling scrum and system thinking. PMI-ACP, PMP Write to me at naveenhome@gmail.com Call me on +91 9810547500 Ping me on Twitter @naveenhome
- 3. DON’T BLAME WATERFALL. WE HAVE NEVER PRACTICED IT PROPERLY. Requirement •Billing Design •Billing Development •Assumption Testing •Bug report Deploy •Blame game
- 4. IS THIS WORKING? Specification Coding Test cases Testing Deploy Rewor k
- 5. SO WHAT TO DO? Max 2 suggestions per team 10 Mins
- 6. WHAT WILL COVER HERE? Impact Mapping Goal Impact Story MappingDeliverable s User Activities Feature s Specification by Examples/BDD User Stories Acceptance Criteria Examples Test First Source Code
- 7. BUT OUR TOPIC SAY SCRUM + BDD SO WHERE IS SCRUM?
- 8. WHAT’S NEEDED TO START SCRUM? Problem Statement – Traffic jam in Colombo during pick hours You as stakeholder - What can you do beside blaming government? Simple solution - Are you Okay with Car Pooling? What stopping you?
- 9. GOAL Let’s develop Car Pool Application Registratio n Share Ride Book Ride Payment Review
- 10. CAN START DEVELOPMENT? Too big to develop and requirement is not yet clear? So what Next? Refinement Registratio n Share Ride Book Ride Payment Review
- 11. PRODUCT BACKLOG REFINEMENT When we refine? Couple of time before 1st sprint and then continuous. Who do that? Product Owner and Development Team What we do? Understand, Split, Estimate and Order How to spilt? Is INVEST enough?
- 12. SOME SPLITTING TECHNIQUE Split based on WORKFLOW Registratio n Signup Verification Login Login Manage Profile Logout
- 13. SOME SPLITTING TECHNIQUE Split based on OPERATION Share Ride Publish New Ride View and Confirm Modify Ride Search all My ride Delete Ride View Only
- 14. SOME SPLITTING TECHNIQUE Split based on RULES Signup No Rules Only 18+ Only IT People Only Colombo People
- 15. SOME SPLITTING TECHNIQUE Split based on DATA TYPE Payment Return Favor Credit Card Cash Card Account Transfer Food Coupon
- 16. TRY SPLITTING 2 PER GROUP Signup Verification Manage Profile Publish New Ride Book Ride Review Credit Card Search Ride 10 Mins
- 17. SO CAN WE START SPRINT? We need acceptance criteria. Not more than 3-4 criteria for a story.
- 18. ACCEPTANCE CRITERIA Feature: Quick Post As a car owner I want to post my ride with minimum requirement so that anyone can register for it.
- 19. ACCEPTANCE CRITERIA – WHY? Define boundaries Provide values to feature Shared understanding Help in derive tests Help in knowing when to stop
- 20. ACCEPTANCE CRITERIA Source:______________ Destination:________________ Time:________________ #Seat available:_____________ Name:_______________ Email:______________________ Phone:_______________ Cancel Submit Share Your Ride
- 21. ACCEPTANCE CRITERIA Feature: Quick Post As a car owner I want to post my ride with minimum requirement so that anyone can register for it. Data must be searchable Ensure only valid data getting saved Cancel should clear data so user can add new ride Successful submission will redirect user on home page
- 22. DISCUSSION OF ACCEPTANCE CRITERIA If(user==“new” { object = user } Else error We should encourage patient to update vitals Login -> Click on “New” and enter test data and then Result &%$^&
- 23. COLLABORATION OF 3 AMIGOS Technical Feasibility Happy Path Exceptions, Test Data, Boundary Conditions Developer Business Tester
- 24. BUILDING RIGHT OR RIGHT PRODUCT? Business Failure Useless Stuff Business Success Technical Debts Specification By Example Build it Right Build the Right Things
- 25. WHAT ARE SPECIFICATIONS BY EXAMPLE Thin Slices of System Behavior That Deliver Business Value Described as concrete examples That are potentially automatable To create executable specifications Captured in live documentation
- 27. WHAT ARE SPECIFICATIONS BY EXAMPLE Given_________________ When_________________ Then__________________ Gherkin Given “Naveen” enter source “Office” and destination “Airport” and time “5.30pm” with 2 seats available And he provides his mail id “naveenhome@gmail.com” and phone number “9810547500” When Click on “Submit” Then Display message “Ride Share” with “OK” button And take “Naveen” to “home” page on click on “OK” And his ride should be shown on top
- 28. ACCEPTANCE CRITERIA Feature: Quick Post Successful submission will redirect user on home page Given “Naveen” enter source “Office” and destination “Airport” and time “5.30pm” with 2 seats available And he provides his mail id “naveenhome@gmail.com” and phone number “9810547500” When Click on “Submit” Then Display message “Ride Share” with “OK” button And take “Naveen” to “home” page on click on “OK” And his ride should be shown on top
- 29. GHERKIN Feature – Name of feature Scenario – Behavior to be developed Given – Pre-conditions When – Actions to be performed Then – Expected Result And – Use for multiple Given, When & Then But – Describe exception cases Scenario Outline – Define multiple scenarios Examples – Multiple Scenarios Background – Avoid repeated Given
- 30. CAN WE START SPRINT NOW? Why not? We have testable specification so let’s start Let’s make a rule for team to have examples for every specification If examples not available then specification will not get picked up for sprint Convert examples in test is our first activity Write enough code to pass those tests
- 32. BEHAVIOR DRIVEN DEVELOPMENT BDD Given Scenario Then Expected Outcome When Perform Action
- 33. LET’S GET STARTED Write Feature to describe scenario in Gherkin Eclipse, Java, Cucumber, Selenium, Junit Create Test Runner class file Generate Steps file Write code to pass test
- 34. BDD - CHARACTERISTICS A testable story (it should be the smallest unit that fits in an iteration) The title should describe an activity The narrative should include a role, a feature, and a benefit The scenario title should say what's different The scenario should be described in terms of Givens, Events, and Outcomes The givens should define all of, and no more than, the required context The event should describe the feature
- 35. BDD - LIFECYCLE 3 5 Your Project Features Scenarios Steps Your System Automation Library Support Code Step Definitions Technology Facing Business Facing
- 36. THANK YOU! Reach out to me if today session was helpful I Facilitate below workshop. naveenhome@gmail.com Certified Scrum Developer (CSD) Workshop Product Discovery and Requirement Analysis Test Driven Development (TDD) Behavior Driven Development (BDD) Agile Testing and Test Automation Agile and Scrum Foundation DevOps Foundation Agile Coaching and Facilitation