Search
Who is online?
In total there is 1 user online :: 0 Registered, 0 Hidden and 1 Guest None
Most users ever online was 36 on Wed Jan 10, 2018 12:25 am
Reviews and walk-through
Page 1 of 1
Reviews and walk-through
Reviews and walkthroughs are typically peer group discussion activities - without much focus on fault identification and correction, as we have seen. They are usually without the statistical quality improvement, which is an essential part of Inspection. Walkthroughs are generally a training process, and focus on learning about a single document. Reviews focus more on consensus and buy-in to a particular document.
It may be wasteful to do walkthroughs or consensus reviews unless a document has successfully exited from Inspection. Otherwise you may be wasting people's time by giving them documents of unknown quality, which probably contain far too many opportunities for misunderstanding, learning the wrong thing and agreement about the wrong things.
Inspection is not an alternative to wal1cthroughs for training, or to reviews for consensus. In some cases it is a pre-requisite. The difference processes have different purposes. You cannot expect to remove faults effectively with walkthroughs, reviews or distribution of documents for comment. However, in other cases it may be wasteful to Inspect documents, which have not yet 'settled down' technically. Spending time searching for and removing faults in large chucks, which are later discarded, is not a good idea. In this case it may be better to aim for approximate consensus documents. The educational walkthrough could occur either before or after Inspection.
It may be wasteful to do walkthroughs or consensus reviews unless a document has successfully exited from Inspection. Otherwise you may be wasting people's time by giving them documents of unknown quality, which probably contain far too many opportunities for misunderstanding, learning the wrong thing and agreement about the wrong things.
Inspection is not an alternative to wal1cthroughs for training, or to reviews for consensus. In some cases it is a pre-requisite. The difference processes have different purposes. You cannot expect to remove faults effectively with walkthroughs, reviews or distribution of documents for comment. However, in other cases it may be wasteful to Inspect documents, which have not yet 'settled down' technically. Spending time searching for and removing faults in large chucks, which are later discarded, is not a good idea. In this case it may be better to aim for approximate consensus documents. The educational walkthrough could occur either before or after Inspection.
puneet- Posts : 21
Reward Points : 41
Join date : 2010-08-22
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum
Mon Mar 06, 2017 3:29 am by JebaQpt
» Can you say some unavoidable aspects for all Android App Testing Services?
Thu Oct 20, 2016 3:12 am by testbytes
» Can someone say about the things to look for while hiring iPad App Testing Services?
Fri Oct 14, 2016 5:26 am by testbytes
» Can you suggest some top testing frameworks used by Android App Testing Services?
Fri Oct 14, 2016 5:24 am by testbytes
» Can someone say why should hire specialist iPad app testing services?
Fri Oct 14, 2016 5:21 am by testbytes
» Can someone say how Android mobile app testing will become crucial in next 5 years?
Wed Aug 17, 2016 5:44 am by testbytes
» Can you say how iPhone app testing services fare in next few years?
Wed Aug 17, 2016 5:33 am by testbytes
» Can anyone say how different types of Mobile Application Testing improve the credibility of apps?
Wed Aug 17, 2016 5:07 am by testbytes
» Can you say some useful fragmentation tools used by android app testing services?
Mon Jul 25, 2016 1:01 am by testbytes