bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic [2016/10/12 13:02] – [Bridging the Communication Gap: Specification by Example and Agile Acceptance Testing - Gojko Adzic.] hpsamios | bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic [2020/06/10 12:50] (current) – ↷ Links adapted because of a move operation hans | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== " | ====== " | ||
| - | ====== Reference ====== | ||
| - | |||
| - | [[http:// | ||
| ====== Review and Notes ====== | ====== Review and Notes ====== | ||
| - | If you are having troubles collaborating with all stakeholders on user stories, if you find you are not clear on requirements, | + | If you are having troubles collaborating with all stakeholders on user stories, if you find you are not clear on requirements, |
| One of the ideas that we push with agile development is the idea that we should move away from requirements documents and move to face-to-face communication to ensure that we are all on the same page. When teams start to do this, they often find that there has not been clear communication of requirements or something has been forgotten in the thinking process and so we feel like we are constantly re-visiting work that "if we only had a requirements document" | One of the ideas that we push with agile development is the idea that we should move away from requirements documents and move to face-to-face communication to ensure that we are all on the same page. When teams start to do this, they often find that there has not been clear communication of requirements or something has been forgotten in the thinking process and so we feel like we are constantly re-visiting work that "if we only had a requirements document" | ||
| Line 40: | Line 37: | ||
| * Tester: "You can influence the development process and stop developers from making the same mistakes over and over. You will have a much better understanding of the domain. You’ll delegate a lot of dull work to developers, who will collaborate with you on automating the verifications. You can build in quality from the start by raising concerns about possible problems before the development starts. You’ll be able to verify business rules with a touch of a button. You will have a lot more time for exploratory testing. You will be able to build better relationships with developers and business people and get their respect." | * Tester: "You can influence the development process and stop developers from making the same mistakes over and over. You will have a much better understanding of the domain. You’ll delegate a lot of dull work to developers, who will collaborate with you on automating the verifications. You can build in quality from the start by raising concerns about possible problems before the development starts. You’ll be able to verify business rules with a touch of a button. You will have a lot more time for exploratory testing. You will be able to build better relationships with developers and business people and get their respect." | ||
| + | ====== Want to Know More? ====== | ||
| + | |||
| + | * [[http:// | ||
| - | {{tag> | + | {{tag> |
| - | ~~LINKBACK~~ | ||
| - | ~~DISCUSSION~~ | ||
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/bridging_the_communication_gap_-_specification_by_example_and_agile_acceptance_testing_-_gojko_adzic.1476302541.txt.gz · Last modified: 2020/06/02 14:22 (external edit)