PNSQC 2014 - Jeana McClure
summary
Team switches acceptance criteria to given when then BDD mid-project while rewriting the most complex web transaction, with a roughly four‑to‑five developer team plus QA, BA and Scrum Master. Acceptance rules live on each story, are refined in three story‑time sessions per sprint, and QA automates them (Cucumber / SpecFlow integrations). Result: repeated runs through regression yield zero regression defects on one release and near‑zero on followups, thanks to clearer preconditions, backgrounds and automated scenarios.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:50Welcome
- 1:20Agenda
- 2:45BehaviorDriven Development
- 3:26Regression
- 5:20Scrum
- 6:38Backlog
- 7:20Science Moment
- 7:58Show Hands
- 8:32Acceptance Criteria
- 10:46SelfService Banking
- 12:21Acceptance Tests
- 23:37Regression Testing
- 26:35Agile
- 28:00Stability
- 30:55When thin
- 33:35Translation exercise
- 36:03Product Owner
- 37:29Project Owner
- 40:13Learning Curve
- 41:39Experience with Scrum
- 43:33Personal Commitment
related talks
01h 21mPNSQC 2013 - Michael Mah
49mTest Strategy in a SCRUM Environment
01h 25mPNSQC 2013 - Kathy Iberle
01h 13mPNSQC 2013 - Lee Copeland
53mShift Left Testing for Continuous Collaboration
01h 19mPNSQC 2013 - Capers Jones
34mWriting end to end tests with a smile
24mFighting against technical debt with BDD, DevOps and Sustainability