QuestionQ67

Software Defect Prevention

Your organization has been conducting detailed requirements reviews, but a problem has emerged: the author of the requirements becomes defensive during these reviews. On a couple of occasions, the author felt personally targeted and left the meeting very upset.

What type of review could you implement to help de-personalize the reviews?

  • A Checklist-based reviewing
  • B Ad hoc reviewing
  • C Role-based reviewing
  • D Perspective-based reviewing
Explanation

Role-based reviewing has each reviewer evaluate the requirements document from the standpoint of an assigned stakeholder role (such as end user, developer, tester, or operations) rather than offering personal opinions about the author's work. Because feedback is framed in terms of whether the document meets the needs of that role, rather than as a personal critique of the author, this technique reduces the perception of personal attack and keeps the discussion focused on the content and its fitness for various stakeholder perspectives. This makes it well suited to situations where authors are becoming defensive or feeling singled out during reviews, unlike unstructured ad hoc reviews or checklist-based reviews, which do not inherently address this interpersonal dynamic.

Community Discussion

No comments yet. Be the first to start the discussion!