In the Requirements Meeting
Once you wangle your way into the requirements discussion, you have the opportunity to help the team discover ambiguities, assumptions, and gaps. You can suss out the Nevers and Alwayses for your software (see Never and Always ), and in doing so you can help make sure everyone involved has a clear vision of the inviolate rules of the system as well. Also, many of the same heuristics you use for exploring software implementations can help you frame specific questions about expected behavior using concrete examples of inputs or conditions.
In this section you’ll discover how to apply your exploration skills to discover the core value that the software is intended to provide and the expectations for behavior related ...
Get Explore It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
