Essential Requirements Practices ( Karl Wiegers )
Many big books on software requirements and business analysis recommend dozens and dozens of practices. They’re all useful in appropriate situations, but it’s daunting to try to remember—let alone implement—the whole set consistently. However, every project should perform 20 core requirements activities. These lay a solid foundation for success and help teams efficiently and effectively elicit, analyze, specify, validate, and manage their requirements. These practices are valuable for both traditional and agile projects, regardless of the kind of product you’re building.
This presentation identifies those 20 core practices and drills down into several of them. They can help project and product teams understand the business problem, engage the right participants, articulate effective solutions, communicate information among stakeholders, implement the right functionality in the right sequence, and adapt to change. Do you have to perform all 20 of these on your project? Maybe not, but you’ll feel less pain and get better results if you do.
Register here to attend