Summary
Collecting implementable requirements is essential to project success. This module explained how to be effective at leading the collection effort. This effort can involve working with all levels of a customer's organization and helping to cut through any barriers to get a clear and concise specification of the need. The solution architect helps keep the conversation focused on the need rather than supporting the notion that the customer’s current process is the only viable solution to consider.
Key points from this module include:
The solution architect leads requirement collection sessions with the customer's subject matter experts.
The solution architect must be an excellent listener and use open-ended questions to drive toward clear requirements.
When possible, it's best to avoid solving how the need will be implemented and focus on what the business need is instead.
Both functional and non-functional requirements are important.
Getting the requirements right is only one step in the process. From requirements, you move into solution planning, tasks, implementation, maintenance, and more. Getting the requirements right early in the process and being agile along the life of a project will give you a better path to success.