Professional Documents
Culture Documents
Process Area
Verification (VER)
Validation (VAL)
DMSC Checklist Optimized (CMMi-Level 3)
CheckList
1. Is SOW /MSA / Project charter Available with Requirement Providers mentioned or identified and Acceptance
criteria defined
2. Is Q&A sheet available for Reqmt Management and up to date
3. Requirement Traceabiltiy Matrix available and up to date
1. Is Governance documents maintained . i.e PAD, CM Plan, PTR, Skill Gap analysis etc
2. Effort Estimates available
3. Size Estimates available
4. Basis of estimation guidelines available Y or N
5. Assumptions documented during estimation Y or N
6. Detailed Schedule Y or N
7. Risks identified Y or N
8. Kickoff conducted and MOM available Y or N
1. MOM
2. All AI tracked to closure no Past dues.
3. ALL RISK & ISSUES tracked to closure
4. Delivery Review conducted and MOM logged
5. Contract compliance reviewed
6. IP register maintained
7. Mid Term Review / Retrospective conducted
8. RCA conducted and corrective / preventive action identified
9. PHP to be updated every week
N/A
1. All project artifacts reviewed as per the review technique mentioned in PAD & tracked through chorus
2. Defects from reviews are recorded and tracked to closure
3. Is ERA reports maintained?
1
2
3
50
1
2
3
4
5
6
7
8
Are the responsibilities of Virtusa and Client during Acceptance process clearly defined?
Are there any activities for which responsibility is not explicitly assigned to either Virtusa or Client?
Does the acceptance criteria clearly specify exclusions?
Is the acceptance process defined with actors and timeline?
Is the agreed delivery schedule included?
Is the person identified for taking the delivery & acceptance criteria check?
Is the agreed upon problem resolution and correction documented?
Does the defect / review comment classification contains all types of defects / comments?
a or Client?
1
2
3
4
5
6
7
8
Does the physical configuration audit section contain list of all the deliverables that require client sign off?
Is the acceptance criteria defined for EACH deliverable included in physical configuration audit section?
Do the User Acceptance Test Cases cover all the functional and non-functional requirements?
Are specification, versions, quantity, duration, location (as applicable), included for the following resources:
Software
Hardware
Tools
Documentation
Personnel
Test data
Special
Is the defect / review comment classification criteria documented?
Is the product acceptance environment documented with special condition, if any?
Is any Knowledge Management artifact/assset reused during the activity?
Is any artifact contributed to Knowledge Mangement inventory?
Review Boards Description
SQARB Applicable to all projects where Testing phase is virtusa led
RARB
SARB Procedures are not available in GIP 6.0. Hence these can be
DARB removed from PTR
CARB