Speakers
- Matt Stine
- Brian Sletten
- Ken Sipe
- Nathaniel Schutta
- Mark Richards
- Pratik Patel
- Matthew McCullough
- Neal Ford
- Tim Berglund
- Peter Bell
- Craig Walls
- Venkat Subramaniam
- Jeff Scott Brown
- Hans Dockter
- Oleg Zhurakousky
- Billy Williams
- Johnny Wey
- Chris Wensel
- Jim Webber
- James Ward
- Kai Wähner
- Vaughn Vernon
- John Steven
- Bruce Snyder
- John Smart
- Stuart Sierra
- Alan Shalloway
- Roshan Sequeira
- Brian Sam-Bodden
- Terry Ryan
- Johanna Rothman
- Ian Robinson
- Paul Rayner
- Nilanjan Raychaudhuri
- Matt Raible
- Eric Pugh
- Prasanna Pendse
- Andy Painter
- Peter Niederwieser
- Andrew Lombardi
- Howard Lewis Ship
- Tiffany Lentz
- Scott Leberknight
- Kenneth Kousen
- Kirk Knoernschild
- Paul King
- Frank Kim
- Heath Kesler
- Heinz Kabutz
- Christopher Judd
- Leonid Igolnik
- Jez Humble
- Daniel Hinojosa
- Erik Hatcher
- James Harmon
- Stuart Halloway
- Arun Gupta
- Jerry Gulla
- Jeff Genender
- Raju Gandhi
- Szczepan Faber
- Ben Ellingson
- Todd Ellermann
- Johan Edstrom
- Hamlet D`Arcy
- Esther Derby
- Jeremy Deane
- Luke Daley
- Adrian Cole
- Cliff Click
- Andrey Breslav
- Charles Bradley
- David Bock
- Ola Bini
- Emad Benjamin
- Scott Bain
- Alex Antonov
- Andres Almiray
- Dan Allen
Charles Bradley
Agile and Scrum Coach
Mr Bradley is an experienced Scrum Coach, Certified Scrum Professional, Certified ScrumMaster, and Certified Professional ScrumMaster I. In addition to his Scrum credentials, Mr. Bradley is also a highly capable, full lifecycle experienced, software development team lead that prefers XP for good engineering practices. He is Sun Certified in Java, and has 13 years of experience in J2EE application development across all tiers. More recently he has also picked up some good C# experience as well. In his spare time, he enjoys driving his wife crazy by talking about Scrum, especially when he refers to his “honey do” list as his “personal backlog” and asks his wife to prioritize her requests. He lives in Denver, Colorado, and he is easily found on LinkedIn.
Presentations
Acceptance and Story Testing Patterns
Acceptance Testing, also known as Story Testing, is a practice that can be applied to any software project, Agile or not. However, to achieve the Agile vision of "working software over comprehensive documentation," it's very important that acceptance tests are easily automated, resulting in a phenomenon you may have heard of, called the "Agile Specification."
In this presentation, we'll discuss eight different patterns of expressing acceptance tests so that they are easy to execute and automate. We'll talk about popular patterns like Given/When/Then and Specification by Example, as well other patterns you've probably never seen. Along with delving into the mechanics of each pattern and showing examples, we'll also discuss the most appropriate situations and team contexts to apply each pattern. Attendees will participate in interactive exercises that will teach them how to utilize the patterns, as well as how to pick the patterns most appropriate for the type of requirement being tested.Expressing Acceptance Tests up front, before development begins, is a vital part of Acceptance Driven Development and the executable Agile Specification.
The User Story Lifecycle: Just Enough, Just In Time
The key to User Stories is making sure your related practices are just enough, just in time.
We'll discuss the different levels of the User Story life cycle, as well as the entrance and exit criteria for each level. More importantly, we'll discuss which levels are totally optional(many of them are) and which are absolutely vital to maximizing User Story value. We'll also follow an example story through the entire life cycle as it progresses from the request level to an epic, to themes, and finally to the legacy lifecycle level.