Gojko Adzic > Quotes

“Find the most annoying thing, fix it, and repeat”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“Beginners think that there is no documentation in agile, which is not true. It’s about choosing the types of documentation that are useful.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“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

“Sell Specification by Example as a better way to do acceptance testing”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“Adam Geras puts this more eloquently: “Quality is about being prepared for the usual so you have time to tackle the unusual.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“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

“Trusting users to enter correct information led to so many problems in the early days of Internet that most software developers today actually do a good job validating inputs, and preventing silly problems. However, as an industry we still have to learn the lesson of similarly distrusting computers, [..].”
― Gojko Adzic, Humans vs Computers

“Eric Evans argued that agile as a term has lost all meaning because anything can be called agile now.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“The F-16 was successful because the design provided a better and cheaper solution than what the customer asked for.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“Watch out for people who implement more than what was agreed on and specified with examples”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“Digitising a piece of work doesn’t mean there will be no mistakes, but instead guarantees that when mistakes happen, they’ll run at a massive scale.”
― Gojko Adzic, Humans vs Computers

“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

“Inflexible automatons, barely smarter than a fridge, now make life-changing decisions.”
― Gojko Adzic, Humans vs Computers

“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

“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.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“One of Elisabeth Hendrickson’s ideas that we like the most is that people who ask for control often really want visibility.”
― Gojko Adzic, Fifty Quick Ideas To Improve Your User Stories

“Implementing functional test automation will get the team to work closer and prepare the system for the use of executable specifications later.”
― Gojko Adzic, Specification by Example: How Successful Teams Deliver the Right Software

“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.”
― Gojko Adzic, Fifty Quick Ideas To Improve Your Tests

“Never aim to implement the whole map. Instead, find the shortest path through the map to the goal!”
― Gojko Adzic, Impact Mapping: Making a big impact with software products and projects