
Sign up to save your podcasts
Or


A Peer Review is a way to improve quality of work products through having individuals in the group review the product and provide feedback.
A Peer Review can be applied to requirements documents, software code, prototypes, wireframes, technical documents, or anything else for which quality is important.
The added benefit of a Peer Review is that it can help spread knowledge within your group. This is possible because the creator of the work product shares information with the review participants as part of the process. As a result, you share knowledge about upcoming product changes and may discover effective practices.
Because the cost of a defect discovered late in the development cycle is much more costly than something found in the analysis phase, peer reviews can improve quality in the beginning stages and save organizations time and money.
Click Here to Get Your Free Guide to Getting Started with Peer Reviews
No One Size Fits All
There’s no one right way to perform a Peer Review. The type of Peer Review you use depends on your specific needs and the type of feedback that will help you improve the quality of your work product.
Types of Peer Reviews range from quick, ad hoc reviews to formal inspections. For requirements documents, I have found that an approach between formal inspections and walkthroughs provided the biggest benefit.
Role-Based Peer Reviews
A Role-Based Walkthrough is a review in which meeting attendees take of different roles such as tester, developer, sponsor, and various stakeholders. The author then walks through the document and attendees provide feedback based on their assumed role.
This type of walkthrough would be done before reviewing the document with the project team and can be done early in development before the document is complete. This allows the author to make changes early in the process to avoid rework and delays due to further analysis.
Listen to the full episode to learn the benefits of peer reviews, how to avoid common problems, and start a peer review program.
http://traffic.libsyn.com/masteringbusinessanalysis/MBA_062__Peer_Reviews_for_Better_Req.mp3
To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.
Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.
The post MBA062: Peer Reviews for Better Requirements appeared first on Mastering Business Analysis.
By Dave Saboe, CBAP, PMP, CSM | Certified Business Analysis Professional | Agile Coach4.7
8282 ratings
A Peer Review is a way to improve quality of work products through having individuals in the group review the product and provide feedback.
A Peer Review can be applied to requirements documents, software code, prototypes, wireframes, technical documents, or anything else for which quality is important.
The added benefit of a Peer Review is that it can help spread knowledge within your group. This is possible because the creator of the work product shares information with the review participants as part of the process. As a result, you share knowledge about upcoming product changes and may discover effective practices.
Because the cost of a defect discovered late in the development cycle is much more costly than something found in the analysis phase, peer reviews can improve quality in the beginning stages and save organizations time and money.
Click Here to Get Your Free Guide to Getting Started with Peer Reviews
No One Size Fits All
There’s no one right way to perform a Peer Review. The type of Peer Review you use depends on your specific needs and the type of feedback that will help you improve the quality of your work product.
Types of Peer Reviews range from quick, ad hoc reviews to formal inspections. For requirements documents, I have found that an approach between formal inspections and walkthroughs provided the biggest benefit.
Role-Based Peer Reviews
A Role-Based Walkthrough is a review in which meeting attendees take of different roles such as tester, developer, sponsor, and various stakeholders. The author then walks through the document and attendees provide feedback based on their assumed role.
This type of walkthrough would be done before reviewing the document with the project team and can be done early in development before the document is complete. This allows the author to make changes early in the process to avoid rework and delays due to further analysis.
Listen to the full episode to learn the benefits of peer reviews, how to avoid common problems, and start a peer review program.
http://traffic.libsyn.com/masteringbusinessanalysis/MBA_062__Peer_Reviews_for_Better_Req.mp3
To get more valuable content to enhance your skills and advance your career, you can subscribe on iTunes.
Also, reviews on iTunes are highly appreciated! I read each review and it helps keep me motivated to continue to bring you valuable content each week.
The post MBA062: Peer Reviews for Better Requirements appeared first on Mastering Business Analysis.

32,246 Listeners

153,989 Listeners

1,643 Listeners

0 Listeners