| | How to deal with changing requirements: agile -- Scrum & XP |
| |
| | Sources for requirements: stakeholders and best practices |
| |
| | Requirements prioritization techniques: MoSCoW Analysis -- Must, Should, Could and Won't be part of the final solution. |
| |
| | User responsibilities in requirements process: requirements articulation and validation |
| |
| | Customer responsibilities in requirements process: requirements gathering and prioritization |
| |
| | Developer responsibilities in requirements process: requirements analysis and definition |
| |
| | Incomplete or incomprehensible requirements: ask for clarification, or approval of a revised version |
| |
