There are several strategies about how to describe the problem and when, during the development process, should it be described.
(1) Volere Template
- A structured natural language template which, by imposing some structure on the problem description, aims to allow the creation of good quality requirements documents.
- It considers traceability between different functional requirements (dependencies), and traceability to the source of the requirement (originator).
- Has a fit criterion for measurability
(2) When is Cheryl’s Birthday? by Peter Norvig
- How the formulation of the problem is close together with its solution.
(3) Customer Interaction Patterns by Linda Rising
- How to create a fruitful relationship with a customer.
- The human and social aspects of requirements engineering.
(4) Crossing Model Driven Engineering and Agility: Preliminary Thought on Benefits and Challenges by Vicent Mahé, Benoît Combemale, and Juan Cavidad
- Discusses the open issues on the integration of model-driven engineering and agile development.
(5) INVEST in good stories, and SMART tasks by Bill Wake
- Presents the qualities of a story: I – Independent, N – Negotiable, V – Valuable, E – Estimable, S – Small, T – Testable
- Presents the qualities of a task: S – Specific, M – Measurable, A – Achievable, R – Relevant, T – Time-boxed