Defining review using Wh Questions

Review is one of the methods for verifying an artefact. (Another method forverification of source code is unit testing). A proper review provides answers to all the ‘wh’ questions.(Refer 15 Points to be taken care during review of a work-product). In fact review itself can be defined using the ‘wh’ questions

Picture

  • Which
    • This answers which artefact needs to be reviewed. It could be atechnical document or a managerial document or even some reference documents.
  • Why
    • This answers why review is to be done. Sometimes review is to detect defects and n some cases it could be even for self-understanding.
  • Where
    • This answers from where the artefact for review needs to be taken. Normally it will be kept under configuration control labelled as ready for review.
  • What
    • This answers the focus of review – Focus of review could be to detect logical defects or to detect standard defects or escaped defects from higher level documents.
    • This answers the type of review – Review could be of different types like formal review semiformal review, informal review etc. (Refer more on type of review in 3 Critical aspects in Review of a work-product)
    • This answer the steps involved in review – The steps involved varies depending on the type of review. If it is a formal review, it will have all the steps like planning, orientation, preparation, review meeting, rework and verification.
    • This answers the goals for review.  There can be goals for review speed, review coverage etc.
  • Who
    • This answers who is going to be involved in review- Some times review may be done by a peer level person or an expert or it could be a joint review between project team and customer as recommended by the process standard ASPICE
  • When
    • This answers the schedule of review – by when the review needs to be started and stopped. There could be entry and exit criteria for starting and ending of review. Also there could be criteria for doing re-review.
  • How
    • Finally this answers how the review data is going to be analysed – Defects may trigger a root cause analysis, review speed may trigger an efficiency based analysis, review coverage and review defect density may trigger an effectiveness based analysis.

About

The author is a Quality Assurance professional by experience. Part Quantitative data analyst, part consultant for quality and information security practices, part software tester, she is a writer by passion and blogs at https://wordsandnotion.wordpress.com and http://qualitynotion.com/.

You may also like...

Leave a Reply