Home > Work > Specification by Example: How Successful Teams Deliver the Right Software
1 " Like cheap wine, long paper documentation ages rapidly and leaves you with a bad headache if you try to use it a year after it was created. On the other hand, maintaining a system without any documentation also causes headaches. "
― Gojko Adzic , Specification by Example: How Successful Teams Deliver the Right Software
2 " Beginners think that there is no documentation in agile, which is not true. It’s about choosing the types of documentation that are useful. "
3 " Sell Specification by Example as a better way to do acceptance testing "
4 " Find the most annoying thing, fix it, and repeat "
5 " Eric Evans argued that agile as a term has lost all meaning because anything can be called agile now. "
6 " Adam Geras puts this more eloquently: “Quality is about being prepared for the usual so you have time to tackle the unusual. "
7 " Implementing functional test automation will get the team to work closer and prepare the system for the use of executable specifications later. "
8 " Watch out for people who implement more than what was agreed on and specified with examples "
9 " The F-16 was successful because the design provided a better and cheaper solution than what the customer asked for. "
10 " As the data is shared, tests influence each other. People get confused very quickly. This is a premature optimization. Write tests to be data agnostic. "