A critical analysis step is a formal review of the requirements. This blog will not cover how to conduct a formal review in detail, but the importance of a formal requirements review vs. a more typical, non-formal review which is common among project teams.
Often project teams do conduct a requirements review, but there is no formal structure behind the review. The review tends to consist of the following:
- The requirements are distributed to the project team for review.
- A 1-2 hour meeting is scheduled to discuss questions and feedback from the team. Hopefully the requirements are reviewed prior to the meeting.
- The Business Analyst (BA) makes necessary updates then re-distributes to the team.
On the surface this sounds good enough. The team had time to review the requirements, have questions answered, and provide feedback to the BA on additional requirements that need to be gathered.
But, there is a major flaw in this type of meeting. The meeting focuses on questions from the team members. There may not be many questions from the team because everyone believes they understand the requirements. Does the entire team have the same understanding of each requirement? For instance, let’s say there is a requirement for a meal order system to validate that the patron selects three balanced meals (breakfast, lunch, and dinner). The BA understands this to be that the meals meet dietary guidelines for a balanced diet. The developer understands this as all of the meals need to weigh the same. Everyone understands the requirement, but they have different interpretations. This may not have been caught until later in the project when the cost to fix the problem increases.
A formal review should be conducted in the following manner:
- Schedule time of participants
- Deliver review materials
- Review of materials by participants prior to the session
- Conduct review session
- Record review notes
- Update material
- Conduct second review session if necessary
In a formal review there are two major advantages over a non-formal review:
- Each requirement is discussed to ensure consistent interpretation of each requirement by the team. The balanced meal requirement would have been clarified.
- Notes are recorded in a consistent manner to help teams reduce the re occurrence of defects in the requirements . This will improve the quality of the requirements over time.
A formal review will take longer than a non-formal review, but we all know it is cheaper to discover and resolve issues earlier in a project than later. Take some extra time to make sure all parties are truly in agreement with the requirements before the solution is being designed and implemented. Over time, the quality of the requirements should improve reducing the time to conduct the requirements review.
Please share your comments on successful and unsuccessful requirement reviews. For more information on formal reviews or to learn how to improve your stakeholder engagement with reviews, check out our Facilitation a Requirements Workshop.
- #AskAnAnalyst Podcast Episode 27: Remote Agile Team Success - March 23, 2017
- #AskAnAnalyst Podcast Episode 26: Are BAs Becoming Obsolete? - February 28, 2017
- #AskAnAnalyst Podcast Episode 25: State of Agile - February 7, 2017
- #AskAnAnalyst Podcast Episode 24: An Agile Mindset - January 27, 2017
- A Monthly Guide to Becoming a Better Business Analysis Professional - January 11, 2017
- #AskAnAnalyst Podcast Episode 22: Business Analysis in 2017 - January 10, 2017
- #AskAnAnalyst Podcast Episode 21: Business Analysis in 2016 - December 8, 2016
- #AskAnAnalyst Podcast Episode 20: Effectively Give and Receive Feedback - November 15, 2016
- #AskAnAnalyst Podcast Episode 19: Live from #BBCCon - November 3, 2016
- #AskAnAnalyst Podcast Episode 18: More Business Analysis Basics - October 4, 2016