Getting Clear Requirements (What does clear mean? (What is the purpose?…
Getting Clear Requirements
Speed up the communication
Book a meeting or meet with the person
Send private message
Format of Information
Should we go for Context-Action-Outcome?
Use Given-When-Then format for expressing scenarios with example data, including pre- and post-conditions
specify the externally-visible behaviour of the system
specify each acceptance criteria
timeline - sprint based deliverables
Should be complete at start to save time
Time Limit to wait? Otherwise call the person?
What does clear mean?
Should state Problem and Expected results
What is the purpose?
Focus on problem rather than solution.
Recognize where a requirement is stated as a solution.
Recognize the urgency of the feature.
Who will be the users?
What is the underlying goal?
Help to express the requirement properly.
Is it to maximise, minimise or optimize?
Is there an implied solution?
Understand why a particular solution may be required.
Collect the constraints that lead to the suggested solution.
What services will be affected?
Is there an opportunity improve existing solutions?
What are the risks or impacts?
How will we know if the need has been met?
Make requirements quantifiable and testable.
Give it KISS (Keep it Simple, **) to obtain readability.