Finding the Sweet Spot, the Art of Writing Scenarios
Does your team ever write scenarios that seem implementation heavy? How about scenarios that feel too vague? This session will take attendees through the art of decomposing user stories into well formed automatable acceptance criteria, from the point of view of a developer and a product owner. Together we will explore the gherkin syntax (given/ when/ then), the trades offs that exists when we change the words we use, and how this can affect the software you build. Attendees will walk away from this session armed with information to help them write better gherkin and make better informed decisions around the words they use.
Outline/structure of the Session
Some presentation/ some interactive with audience participation.
Concepts will backed up with audience participation as we work together to refactor an example together.
Attendees will walk away from this session armed with information to help them write better gherkin and make better informed decisions around the words they use.
People on agile teams! (Product Owners, Business Analyst, Quality Assurance, Developers)
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Technical Practices through a Kanban LensNayan Hajratwala
schedule 1 year agoSold Out!
People in organizations that are learning Kanban quickly understand the relationship of WIP, Cycle Time and Throughput. However, when teams start doing things like Pair Programming, they tend to hold fast to the idea that “you’d get more done if you worked separately!”
High performing software teams use a variety of modern technical practices including Test Driven Development, Pair/Mob Programming, Refactoring, Evolutionary Design, and Continuous Integration & Delivery.
How do these practices fit into the Kanban context? Whether through improving collaboratively, evolving experimentally, or implementing feedback loops, learn how these technical practices are supported by Kanban's four Foundational Principles and six Core Practices, which in turn make Kanban more powerful.