Home > Author > Gojko Adzic
1 " A common pattern for teams that start with test automation, or development groups that start breaking down silos between testers and developers, is to take existing manual tests and automate them. Unless it’s a training exercise for an automation tool, this is almost always a bad idea. "
― Gojko Adzic , Fifty Quick Ideas To Improve Your Tests
2 " When teams decide to automate a set of existing tests that were previously designed as manual tests, the best way forward is to rewrite and redesign the tests from scratch. Keep the purpose, but throw away pretty much everything else. "
3 " 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
4 " Beginners think that there is no documentation in agile, which is not true. It’s about choosing the types of documentation that are useful. "
5 " Sell Specification by Example as a better way to do acceptance testing "
6 " Find the most annoying thing, fix it, and repeat "
7 " Small, easy wins always get prioritised over difficult tasks. It’s like children choosing between chocolate and broccoli. "
― Gojko Adzic , Fifty Quick Ideas to Improve Your User Stories
8 " Eric Evans argued that agile as a term has lost all meaning because anything can be called agile now. "
9 " Adam Geras puts this more eloquently: “Quality is about being prepared for the usual so you have time to tackle the unusual. "
10 " Implementing functional test automation will get the team to work closer and prepare the system for the use of executable specifications later. "
11 " Watch out for people who implement more than what was agreed on and specified with examples "
12 " The F-16 was successful because the design provided a better and cheaper solution than what the customer asked for. "
13 " 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. "
14 " If a product milestone or project succeeds in delivering the expected business goal, it is a success from a business perspective, even if the delivered scope ends up being different from what was originally envisaged. On the other hand, if it delivers exactly the requested scope but misses the business goal, it is a failure. "
― Gojko Adzic , Impact Mapping: Making a Big Impact with Software Products and Projects
15 " Never aim to implement the whole map. Instead, find the shortest path through the map to the goal! "
