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 a More »

Catching defects early reduces cost. Below 15 points explains the things to be taken care during review of a document.

  1. Ensure compliance w.r.t higher level documents. For example, If a design document is reviewed, ensure that all the user needs detailed in requirement document are addressed in the design document too
  2. Ensure spelling and grammar. It has got its own importance especially during translation from one language to another.
  3. Ensure that the document addresses an alternate way of More »

Reviews have been introduced based on Weinberg’s Concept of Egoless Programming Principle. According to this principle, independent teams are established to detect defects. All work products come under the scope of review. It is the responsibility of project manager to identify the work products for review and allocate sufficient time for review. In case 100% review is not feasible, the work products which need not be reviewed shall be identified in the project.

 Review process may vary based on the type of review as well as procedures /steps involved in the review. It has got 3 critical aspects. And it could be summarised as below

14. March 2014 · Write a comment · Categories: CMMI · Tags:

Normally estimates are derived with a 50- 50 confidence.  But  is a fifty-fifty case okay while setting  your goals/targets/specification limits ? People will prefer to have a better confidence while setting their goals. So what should be done.? Some improvements needs to be brought in to the current system . Those improvements needs to be chosen in such a way that it will have a positive impact on the goals.

Now, consider a project scenario. Project A sets their effort estimates as 100 Person Days (PD).  This More »

Further to what you might have read in http://qualitynotion.com/what-control-chart-shall-i-use-3/..

Unlike the C chart, U chart does not require a constant number of sample items, and it does not require any limit to the potential number of defects/nonconformities. Further more for a P- chart of NP chart, the number of non conformities cannot exceed the number of items on a sample, but for a U chart it is acceptable because what is being addressed is not the number of defective items, but the number of defects on the sample. In short,

Attribute Data  charts

 

 

 

 

More »

How can we optimize the time and effort of a full time QA person (process consultant) in a project..? In majority of the cases, at least 50 % of the auditing work done by QA could be automated.. Then how could the QA work be made cost effective..? Post your suggestions.

http://qualitynotion.com/question/how-to-optimize-the-usage-of-a-full-time-qa-in-a-project/