Q: Can you give us a simple example (or two) of how to quantify requirements? I recall one interesting example you gave when you did training for us at AgileScotland that involved (I think) making online survey forms easier to use ...
Well, the longer answer is available:
http://www.gilb.com/community/tiki-download_file.php?fileId=124 <- Quantifying Quality Paper.
But the main idea is that for a critical improvement (usually 'Quality') attribute - we need to articulate the idea with Numbers.
This involves two steps:
1. Define scale of measure
2. Define some useful numeric points on that scale.
So instead of 'better user friendliness"
we might write:
Usability:
Scale: The average time needed for an average user to correctly perform representative tasks.
Past 10 hours.
Goal [2009] 1 hour.
Most people can quickly pick up on doing this.
When you get stuck there are lots of available Scale patterns to use, and to tailor to your specific purposes.
My favorite teaching example is quantifying 'Love' !
A friend pointed out the Bible, Corintians 1, had the solution! - as I pointed out earlier.
Google them! For example: "Intuitiveness software metric" , if all else fails try Intuitiveness software metric gilb :)
Comments