Archive

Posts Tagged ‘Audits’

Mapping SCRUM Methodology with ISO 9001:2008 standard

September 3, 2010 7 comments

There is always a question in the forum, is it SCRUM methodology practices can be mapped to ISO 9001:2000 standard. The answer to the question is yes, we can. The mapping of the SCRUM Methodology to ISO 9001:2008 is as below (please correct me if am wrong in the mapping):

Role Duties Artifacts ISO 9001:2008
Product Owner Sprint Planning

Sprint Review

Product Backlog

User stories

Clauses: 4.2.3, 4.2.4, 5.2, 7.1, 7.2, 8.3, 8.5.2 & 8.5.3
SCRUM Master Sprint Planning

Daily Standup Meeting

Sprint Review

Retrospective Meeting

Sprint Backlog

Burn-down Chart

Clauses: 4.2.3, 4.2.4, 5.5.1 5.5.3, 7.1, 7.3.5, 8.2.1, 8.2.3,8.2.4,  8.3, 8.4 & 8.5
SCRUM Team Sprint Planning

Daily Standup Meeting

Sprint Review

Retrospective Meeting

Sprint Backlog

Burn-Down Chart

Clauses: 4.2.3, 4.2.4, 5.5.3, 7.1, 7.3, 8.2.1, 8.2.3, 8.2.4, 8.3, 8.4, 8.5.2 & 8.5.3
Advertisements

Implementation of QMS (Part4)

October 3, 2009 Leave a comment

Learn From Others & Share Your Experiences

As it was trail or test ride, implement the same across the organization at full fledge, since the procedures / process is matured one now. For implementation of the procedures / process to the full fledge the existing team which is already had used, need to spend time to share their experience with others and help them to get learned.

Quality is a team work rather than individual one.

Functional Audit vs Physical Audit

December 16, 2008 2 comments
 

Functional Audit

Physical Audit

 

Objective: To provide an independent evaluation of software products, verifying that its configuration items’ actual functionality and performance is consistent with the requirement specifications.

 

 

Objective: To provide an independent evaluation of a software product configuration item to confirm that components in the built version map to their specifications.

 

Audit Requirements:

 

1. Software Requirements Specification (SRS), System Specification (SS)

2.  Waiver or Deviation List Prepared

3.  Verification Test Procedures Prepared.

4.  Verification Test Procedures Reviewed and Approved.

5.  Verification Test Data and Results Reviewed and Approved

6.  Test Results submitted.

7.  Test Readiness Review completed

8.  Test Readiness Review minutes and open action items from past reviews available

9.  Copy of baseline and database change requests with their associated status accounting records along with all design provided

Audit Requirements:

 

1.  Approved final draft of the configuration item (CI) product specification.

2.  A list delineating both approved and outstanding changes against the configuration item.

3.  Acceptance test procedures and associated test data.

4.  Findings / Status of quality assurance programs.

5.  Manuscript copy of all software CI manuals.

6.  Computer Software Version Description Document.

7.  Current set of listings and updated design descriptions or other means of design portrayal for each software CI.

8.  FCA (Functional Configuration Audit) minutes for each configuration item.

Informal Review Vs Formal Review

April 17, 2008 3 comments

Sl.No

Informal Review

Formal Review

1

Conducted on an as-needed I.e. Informal agenda

Conducted at the end of each life cycle phase I.e. Formal Agenda

2

The date and the time of the agenda for the Informal Review will not be addressed in the Project Plan

The agenda for the formal review must be addressed in the Project Plan

3

The developer chooses a review panel and provides and/or presents the material to be reviewed

The acquirer of the software appoints the formal review panel or board, who may make or affect a go/no-go decision to proceed to the next step of the life cycle.

4

The material may be as informal as a computer listing or hand-written documentation.

 

 

The material must be well prepared.

 

Ex Formal reviews include the Software Requirements Review, the Software Preliminary Design Review, the Software Critical Design Review, and the Software Test Readiness Review.