SE Radio 604: Karl Wiegers and Candase Hokanson on Software Requirements Essentials

Documentation

Documenting requirements is crucial for effective team communication and project success. Candase Hokanson shares her experience with a modified scaled agile approach, organizing requirements into epics, features, and user stories, which are then grouped into releases using a requirements management tool 1. This centralized repository allows for robust version history and easy access for all team members. Karl Wiegers emphasizes the importance of even rudimentary documentation to avoid misunderstandings and rework, stating, "People's memories simply are not as reliable as everyone likes to think they are" 2.

   

Change Management

Managing changes in requirements is a dynamic process that requires flexibility and clear communication. Candase Hokanson describes a lightweight change control process involving emails and communication tools like Slack, ensuring all changes are tracked in a requirements management tool 3. This approach allows teams to assess the impact of changes and make necessary trade-offs to keep projects on track. Karl Wiegers highlights the importance of structured requirement specifications to prevent rework, noting that "Human memories are imperfect and incomplete" 4.