IT项目管理课件11.000.ppt

Quality Review Frequency When to review a process or work product: On a periodic basis: daily, weekly, monthly, quarterly, annually, etc. Audit each major process at least annually When specific events occur, such as : Upon completion of requirements document Upon completion of life cycle phases For each release Only when a serious problem is identified, etc. Quality Review Frequency Could review a predefined percent of a work product, such as 25% of all code designs Could review 100% of them (all) Could perform that review only when directed by QA Management (implies rarely) Quality management plan should identify the scope of QA activities in these terms Extent of these planned activities determines whether QA role is passive or active Review Criteria When performing process assessments, process evaluations, process verifications, and product evaluations, there are many things for which the reviewer could be looking The report describing the results of this review activity should identify which of these review criteria were used Review Criteria Completeness - Extent to which the process is followed through to completion, or the product is free from TBD’s Compliance - Extent to which the product adheres to specified standards (CMM, IEEE, ISO, etc.), regulations, and laws Conformance - Verification that the documented process is used and performed on schedule Review Criteria Consistency - Extent to which the process is consistently used by all members of the affected organization Contractual Requirements - The extent to which the process fulfills the stated contractual project requirements Control - Extent to which the process, documentation, and referenced tools are constrained by a configuration management system Review Criteria Correctness - Extent to which the process is producing correct output, based on peer review and customer evaluation of the output Definition - Extent to which the process is described and documented Editorial Correctness - Extent to whi