Cyay6k8m704jos1judhc
SkillsCast

Two Sides of the Story

22nd November 2013 in London at The Crypt, St James Church Clerkenwell

There are 5 other SkillsCasts available from Agile Testing & BDD eXchange 2013

Please log in to watch this conference skillscast.

455926096 640x360

In this talk, David and Bri will debate the pros and cons of using stories and discuss practices and techniques for improving them. We are going to tackle concerns that trouble many agile teams, such as: What is the right level of detail for specifying user stories?

User Stories are a widely adopted technique for agile teams. But opinion is divided on the value and usefulness of Stories. Are they a godsend for quality? A convenient and precise shorthand? Waterfall requirements in agile clothes? A necessary evil? A pernicious cancer infecting team creativity and product owner freedom?

Are stories really the key ingredient that allows an agile team to get valuable stuff done and tested faster, or are they just a placebo, providing reassurance that at least we "sound agile"?

Should we stick to the standard template? How do we ensure we don't lose sight of the big picture? Is it OK to have technical stories? Should we use cards or a system?

YOU MAY ALSO LIKE:

Thanks to our sponsors

Two Sides of the Story

David Evans

David Evans is an independent agile consultant, coach and trainer. He is an evangelist on agile testing, TDD, BDD and Specification by Example, and is a regular speaker at international conferences and seminars.

Brindusa Axon

Brindusa is a passionate agile consultant and coach. She works with ambitious companies across Europe to facilitate the kind of organizational change that has great impact on the individuals and the bottom line.

SkillsCast

Please log in to watch this conference skillscast.

455926096 640x360

In this talk, David and Bri will debate the pros and cons of using stories and discuss practices and techniques for improving them. We are going to tackle concerns that trouble many agile teams, such as: What is the right level of detail for specifying user stories?

User Stories are a widely adopted technique for agile teams. But opinion is divided on the value and usefulness of Stories. Are they a godsend for quality? A convenient and precise shorthand? Waterfall requirements in agile clothes? A necessary evil? A pernicious cancer infecting team creativity and product owner freedom?

Are stories really the key ingredient that allows an agile team to get valuable stuff done and tested faster, or are they just a placebo, providing reassurance that at least we "sound agile"?

Should we stick to the standard template? How do we ensure we don't lose sight of the big picture? Is it OK to have technical stories? Should we use cards or a system?

YOU MAY ALSO LIKE:

Thanks to our sponsors

About the Speakers

Two Sides of the Story

David Evans

David Evans is an independent agile consultant, coach and trainer. He is an evangelist on agile testing, TDD, BDD and Specification by Example, and is a regular speaker at international conferences and seminars.

Brindusa Axon

Brindusa is a passionate agile consultant and coach. She works with ambitious companies across Europe to facilitate the kind of organizational change that has great impact on the individuals and the bottom line.