How do we effectively manage the requirements at different detail levels?

At just about any point in the requirements lifecycle, you'll probably have to deal with requirements at different levels of detail. Broader requirements (e.g., vision statements) generally have much less detail than business rules. In either case, you're still accountable for making sure that the details are well documented, that they are reviewed by the right stakeholders, and that they are properly handed off for development, validation or testing, and implementation. Naturally, this process can get really tricky as the number of requirements rises.

Log in or Subscribe now to read the full answer...