How much detail?
Tips for the right level of detail
for your requirements
Level of detail – example 1
Lots of freedom for
drivers
Level of detail – example 2
Highly controlled
parking
Which is better?
Not detailed• Experienced drivers will manage• Creative use of space is possible• Cars could get blocked in• Space to park a bus
Detailed• Most drivers will manage• How space is used is predefined• Cars can always get in & out• Doesn’t have space for a bus
Which is better? It depends!
What does detail level depend on?
• Many factors influence what the optimal level of detail is.
• Here are just a few…
Factor 1: What is the next step?
Detail level depends on what the next step in the process is.
Compare:– input for the initial business case– basis for COTS software selection– discuss with product owner before the next sprint
Factor 2: Who’s going to use it?
• How much does the recipient know about the business domain?
• How much time will she spend reading them?
• Does he have a different cultural background, and if so: how does that affect the way they interpret your requirements?
Factor 3: When do you need it?
• Requirements will change.• Delay writing the details until they are
needed.
Factor 4: Do stakeholders care?
• Do these details really matter to the stakeholders?
• E.g: requesting a specific colour– Trivial & irrelevant?– Needed to comply with a standard?
Factor 5: What is the impact?
• What could go wrong?
• Is it worse than spending an extra couple of days writing detailed requirements?
Just enough detail
• Enough confidence for the customer • Enough freedom for the supplier
• Level of detail does not have to be the same for all parts– E.g. application interfaces & standards
http://creativecommons.org/licenses/by-sa/3.0/
Recommended
