How we build quality software at uSwitch.com
•
6 likes•1,265 views
The document describes uSwitch's process for developing quality software. It outlines how the company has evolved from a traditional waterfall approach to a more agile, test-driven development model focused on: 1. Building quality into software from the start rather than relying on inspection and testing later. 2. Having testers work alongside developers to continuously test software throughout development. 3. Conducting demonstrations and sign-offs on demand from business stakeholders to obtain early feedback. The process emphasizes continuous testing, monitoring of production systems, and breaking work into individually deployable tasks to enable rapid, flexible development and deployment of high quality software.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to How we build quality software at uSwitch.com
Similar to How we build quality software at uSwitch.com (20)
Recently uploaded
Recently uploaded (20)
How we build quality software at uSwitch.com
- 1. How we develop quality software at uSwitch
- 2. Plan Dev Test Deploy
- 3. Plan Dev Test Deploy
- 4. Dev • Hand-over, ping-ponging • Peripheral activities (waste) • Damage already done (toast already burnt) Test
- 5. Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 6. Dev Dev Dev Sign-off Plan Deploy / test Test Test Test 1 day 10 days 2 days 2 days
- 7. • Tasks • TDD • Code complete • CI Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 8. • Tasks • TDD • Code complete • CI Dev Dev Dev Sign-off Plan Deploy / test Test Test Test • Poor • Selenium • Inspection acceptance • Sign-off criteria • QTP
- 9. Backlog In Progress QA Done Task 3 5 1 Task 2 4 6 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 10. Backlog In Progress QA Done Task 1 Task Task 3 5 Task 2 4 Task 6 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 11. Backlog In Progress QA Done Task 1 3 Task Task 5 Task 4 2 Task Task 6 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 12. Backlog In Progress QA Done Task 13 Task Task 5 Task 2 Task 4 Task 6 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 13. Backlog In Progress QA Done Task 5 1 Task3 Task 2 Task 4 Task 6 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 14. Backlog In Progress QA Done Task 3 1 Task 4 2 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 15. Backlog In Progress QA Done Task 3 Task 1 Task 4 Task 2 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 16. Backlog In Progress QA Done Task 1 Task 3 Task 2 Task 4 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 17. Backlog In Progress QA Done Task 1 3 Task Task 4 Task 2 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 18. Backlog In Progress QA Done Task 3 Task 1 Task 4 Task 2 Dev Dev Dev Sign-off Plan Deploy / test Test Test Test
- 19. Dev Dev Dev Sign-off Plan Deploy / test Test Test Test • Tasks • Wall • Mass testing/sign-off • Deployments (“Fat-er wall”)
- 20. Dev Dev Dev Sign-off Plan Deploy / test Test Test Test Time to integrate! Whole-team “agile” testing
- 21. Dev Dev Dev Sign-off Plan Deploy / test Test Test Test 1. Wall 2. Deployments 3. Tasks 4. Mass testing/sign-off
- 22. 1. Wall “Cease dependence on inspection to achieve quality. Eliminate the need for inspection on a mass basis by building quality into the product in the first place.” Dr. W. Edward Deming
- 23. 1. Wall Sign-off Plan Dev Dev Dev Deploy / test • Developers focus on quality • Testers started developing • Right testing in the right places
- 24. 1. Wall Sign-off Plan Dev Dev Dev Deploy / test • Developers focus on quality • Testers started developing • Right testing in the right places
- 25. 1. Wall Backlog In Progress QA Done Done Done-done • Developers focus on quality • Testers started developing • Right testing in the right places
- 26. 1. Wall Backlog In Progress Done Done-done • Developers focus on quality • Testers started developing • Right testing in the right places
- 27. 2. Deployments Sign-off Plan Dev Dev Dev Deploy / test • Contribution from Ops
- 28. 2. Deployments Sign-off Plan Dev Dev Dev Deploy / test • Contribution from Ops
- 29. 3. Tasks Sign-off Plan Dev Dev Dev Deploy / test • Reflect user value • Individually deployable • Definition of done
- 30. 3. Tasks Sign-off Plan Dev Dev Dev Deploy / test • Reflect user value • Individually deployable • Definition of done
- 32. Acceptance criteria: Use r story: Given.. Things to think about When.. o that.. for acceptance / where S bugs can lurk Then.. As a.. I want.. Input Happy path / sad path State Does it do what we want it to do? Environment Does it do what we don’t want it to do? Data
- 33. Acceptance criteria: User story: Given.. So that.. When.. As a.. Then.. Things to think about for acceptance / where I want.. bugs can lurk Happy path / sad path Input Does it do what we want it to do? Does it do what we don’t want it to do? State Environment Data
- 34. Acceptance criteria: User story: Given.. So that.. When.. As a.. Then.. Things to think about for acceptance / where I want.. bugs can lurk Happy path / sad path Input Does it do what we want it to do? Does it do what we don’t want it to do? State Environment Apply Data foresi g ht
- 35. 4. Mass sign-off/testing Sign-off Plan Dev Dev Dev Deploy / test • Continuously running tests • Continuous monitoring of production • Demo workshops on demand
- 36. 4. Mass sign-off/testing Sign-off Plan Dev Dev Dev Deploy / test • Continuously running tests • Continuous monitoring of production • Demo workshops on demand
- 38. Continuously running tests • Cucumber & Watir (Ruby) • Running continuously in TeamCity
- 39. Continuous monitoring of production
- 40. Continuous monitoring of production • Customer experience tracking • External user simulation • Internal monitoring of web services
- 41. Continuous monitoring of production • Customer experience tracking • External user simulation • Internal monitoring of web services
- 42. Continuous monitoring of production • Customer experience tracking • External user simulation • Internal monitoring of web services
- 43. Business sign-off on demand Sign-off Plan Dev Dev Dev Deploy / test
- 44. Business sign-off on demand Dev Dev Dev Plan Deploy Sign-off Sign-off Sign-off
- 45. Business sign-off on demand Plan Dev Dev Dev Deploy
- 46. Business sign-off on demand Plan Dev Dev Dev Deploy Becoming leaner...
- 47. More on demand Plan Dev Dev Dev Deploy
- 48. More on demand Plan Plan Plan Plan Plan Dev Dev Dev Dev Dev Deploy Deploy Deploy Deploy Deploy
- 49. More on demand 2 hours Plan Plan Plan Plan Plan 4 days Dev Dev Dev Dev Dev 2 hours Deploy Deploy Deploy Deploy Deploy
- 50. More on demand Plan Plan Plan Plan Plan Dev Dev Dev Dev Dev Deploy Deploy Deploy Deploy Deploy Continuous running tests Continuous monitoring of production
- 51. Current process Ready Backlog In Progress Done Inventory Done-done Done
- 52. Current process Ready In Progress Inventory Done
- 57. Current process Ready In Progress Inventory Done 1 Story 3 Story 4 2
- 58. Current process Ready In Progress Inventory Done Story 3 Story 1 Story 4 Story 2
- 59. Current process Ready In Progress Inventory Done Story 3 Story 1 Story 4 Story 2
- 60. Current process Ready In Progress Inventory Done Story 13 Story Story 4 2
- 61. Current process Ready In Progress Inventory Done Story 13 Story Story 4 2
- 62. Ready So that.. As a.. I want..
- 63. Ready So that.. As a.. I want..
- 64. Ready • Specification-workshop So that.. As a.. I want..
- 65. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want..
- 66. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want..
- 67. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want..
- 68. Ready • Specification-workshop • Acceptance criteria So that.. Given.. As a.. When.. I want.. Given.. Then.. When.. Given.. Then.. When.. Then.. In Progress
- 69. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 70. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 71. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 72. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 73. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 74. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. Given.. When.. Given.. Then.. When.. Then.. In Progress Given.. When.. Then..
- 75. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. In Progress Given.. Given.. When.. Given.. When.. Then.. When.. Then.. Then..
- 76. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. • Acceptance tests In Progress Given.. Given.. When.. Given.. When.. Then.. When.. Then.. Then..
- 77. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. • Acceptance tests • Unit tests In Progress Given.. Given.. When.. Given.. When.. Then.. When.. Then.. Then..
- 78. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. • Acceptance tests • Unit tests • Demo-ed In Progress Given.. Given.. When.. Given.. When.. Then.. When.. Then.. Then..
- 79. Ready • Specification-workshop • Acceptance criteria So that.. As a.. I want.. • Acceptance tests • Unit tests Inventory • Demo-ed In Progress Given.. Given.. When.. Given.. When.. Then.. When.. Then.. Then..
- 80. Ready • Specification-workshop • Acceptance criteria • Acceptance tests • Unit tests Inventory • Demo-ed In Progress Given.. Given.. So that.. When.. Given.. When.. Then.. a.. As When.. Then.. I want.. Then..
- 81. Ready • Specification-workshop • Acceptance criteria Done • Acceptance tests • Unit tests Inventory • Demo-ed In Progress Given.. Given.. So that.. When.. Given.. When.. Then.. a.. As When.. Then.. I want.. Then..
- 82. Ready • Specification-workshop • Acceptance criteria Done So that.. As a.. I want.. • Acceptance tests • Unit tests Inventory • Demo-ed In Progress
- 83. Ready • Specification-workshop • Acceptance criteria Done So that.. As a.. • Acceptance tests ++ I want.. • Unit tests ++ Inventory In Progress
- 84. Quotes from the team •“Is there a better way to test this?” • “How are we going to test this?” • “We can’t keep up!”
- 85. What if.. • Our code could ship self-testing? • We could reduce the life expectancy of a bug even more? • We used a test-first approach, whether agile or not?
- 86. What if.. • We don’t call it ‘Agile’ testing, but just testing? • We don’t call it testing, but developing?
- 87. uSwitchers @markdurrand, @damonmorgan, @markholdsworth, @jasonneylon, @drewmacqu, @stephen_lloyd, @mbaldry, @jon_neale, @barisbalic, @lordloverocket, @tonyto85, @hemalkuntawala (@mikewagg, @zkhan, @jwilliamson83, @paulsharrington) http://testerhemal.wordpress.com
- 88. gojko@neuri.com
- 90. Thanks for listening :)
- 91. Thanks for listening :)
Editor's Notes
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- This is what our wall looked like. uBu, BAU, early Energy. Done doesn’t mean live, that’s a whole more effort. “Quality police”. Uses of QTP, Selenium, manual exploratory testing.
- Remove the wall.. integrate Testing, make Testing a focus for developers.
- Remove the wall.. integrate Testing, make Testing a focus for developers.
- Remove the wall.. integrate Testing, make Testing a focus for developers.
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- Because we still faced the same issues with the wall, we integrated testing into the development phase, it wasn’t ‘Done’ if it wasn’t fully tested and signed off.. Refine tasks to User Stories.
- Because we still faced the same issues with the wall, we integrated testing into the development phase, it wasn’t ‘Done’ if it wasn’t fully tested and signed off.. Refine tasks to User Stories.
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).
- 2 stages.. Developers helped with testing. Selenium scripts to lock down feature, developers help test features. Developers gain an understanding of testing effort BDD on a code level, but no formal definition of acceptance criteria - Define what we were to develop upfront before development begins - Good user stories but no Acceptance Criteria.. created a cheat sheet to gather these from planning sessions. Did these on demand, not upfront. Influences of kanban + lean principles (limited WIP, cycle times - concept to cash times).