- Number of defects?
- Customer happiness?
- Money earned?
- Developer smiles?
BDD and Agile Testing Exchange in London
Gojko Adzic
Gojko Adzic - Wikipedia, the free encyclopedia
His book, "Specification by Example",[1] presented the idea of moving to 'living documentation' and 'active specification'. It has prompted debate about whether it is a scalable approach[4] and been used on projects and proven to work[5].
In addition to his own books, he is also the co-author with David de Florinier of an eBook called "The Secret Ninja Cucumber Scrolls"[6].Cucumber is a testing tool that, along with FitNesse, he uses to support his approach to agile testing and development.
He has been interviewed by others in the profession[7] and is a prolific speaker at development and testing conferences.
Adzic runs the UK Agile Testing[8] group and keeps a website under his own name and with the subtitle of 'building software that matters'.[9]
We tend to ignore information
We are used to ignore automatic alarms, even fire alarms:
we just don’t care, but we care when a person tells us about an issue or is
shouting « fire in the building! ».
Gloves on the Boardroom Table
- As in the story of the Gloves on the Boardroom Table, making the problem tangible and visible help trigger reactions.
- Sharing information is not enough,
- a company is like an elephant, you don’t really drive it, you motivate it to go where you’d like to go. So visualization can help there.
Best Practices Change Over Time
- what may seem nonsense today may be the next best practice tomorrow.
Absence of bugs ≠ Presence of quality
The absence of bugs is completely different than the presence of quality. Twitter has lots of bugs but most people are happy with it so it has quality; on the other hand, Nokia phones have no bug, yet if nobody likes them they have no quality either.
3 levels (the 3 P’s):
- Process effectiveness
- Product status
- Production performance
Each of the first two is just a proxy for the next, and only the last is the real one
Test coverage is crap
- risk coverage, that is the amount of testing compared to the associated risk.
- This metrics helps identify where you need to test more.
Low Tech Testing Dashboard
You divide your system into high-level subsystems, and for each you monitor the « progress of testing »:
- not yet started,
- half done or
- done,
and the « level of confidence so far » with
3 smileys from happy to anxious.
That’s better than a bug-tracking tool with 500 tickets mixed altogether.
Effect Map
Effect Mapping
Effect Mapping is a game-changing technique for
high level project visualization. It provides stakeholders and sponsors with an excellent level of visibility and helps to drive software projects towards delivering the right product with a high level of quality.
ACC Matrix
VisualisingQuality
