QMS Orientation TRNG - Induction Sep07

QMS Orientation
Induction – Sep 2007
Protection notice / Copyright notice

Course Objective
To enable participants understand the SISL Quality

Management System and apply this knowledge to execute
project activities effectively

Page 2 Sep 2007 For Internal Use only P&Q
Why do we need
Process?

The Story of Four Men
This is a story of four people named Everybody, Somebody,
Anybody and Nobody.
There was an important job to be done and Everybody
was sure that Somebody would do it.
Anybody could have done it, but Nobody did it.
Somebody got angry about it, because it was Everybody's

job.
Everybody thought Anybody could do it, but Nobody
realized that Everybody wouldn’t do it.
It ended up that Everybody blamed Somebody when

Nobody did what Anybody could have done.

Sense of Direction
“If we do not know where we are going any road will do”
“If we do not know where we are, a Map won’t help”
– Watts Humphrey
How do I figure out where I want to go?

Quality Management System

Evolution of QMS
Process Handbook (PHB)
from SNI AG, Mch
ISO 9001:1994
Compliant
QMS
SEI/CMM L5
Compliant
QMS Plus
ISO 9001:2000 CMMI

Compliant Compliant
QMSFW QMSFW+
QMS Document Structure
Quality Manual
Policy
Processes Procedures
Templates, Guidelines,
Processes Assets Checklists, Forms
Metrics, Lessons Learned

Processes Database Training Material, Knowledge Manager

SISL Quality Policy
SISL shall endeavour to deliver high

quality solutions and services to its
customers on time and in a consistent
manner. This shall be achieved through
a documented Quality Management
System that supports continual levels of
improvement across all business
processes. SISL shall ensure customer
delight by working and partnering
closely with them; while striving to
develop competencies and improve
employee satisfaction.
Refer Quality Manual

Project Management Process

What is a Project?
• A project consists of a managed set of activities undertaken,

and a clear scope to:
- create a product,
- deliver a service, or
- achieve a business result,
- and to achieve specific objectives and completion criteria
within specific time, cost, and resource constraints
• A project is characterized by:

- clear definition of tasks
- defined duration with an end date
- agreed effort and cost estimation
- clear responsibilities
Refer Procedure for Project Planning

Project Management
Plan documents –
Planning •Project Plan
PQR_Template
Planned Documents (Project, Quality, •Quality Plan
Configuration, Test) •Configuration Management Plan
Project Scheduling & Tracking • Test Plan
•Project Schedule
Risk & Issue Management •Risk Management Plan
Risk Management Plan covering •Tailored Documents

PP_Template
Risk Mitigation and Contingency Planning
PS: Templates for all the planning
documents are available on QMS
Process Tailoring Portal.
Tailoring of QMS processes and documents to suit customer

RiMP_Template and project requirements
Identification of Customer standards and templates (if any) to
be used.
Tailoring Matrix

Project Management Processes
• Requirements Management
• Estimation
• Risk Management
• Project Organization
• Project Quality Planning
• Project Planning
• Project Tracking/Escalation
• Reviews
• Purchasing
• Training
• Handling Customer Complaints
• Measurements

Other Processes
• Configuration Management
• Document & Data Control (Projects & QMS)
• System Administration
• Management Responsibility
• Internal Quality System Audit
• Process Improvement & Maintenance
• Life-Cycle Activities
• Testing
• Acceptance
• Replication, Delivery and Installation

Project Classification
Team size >20 10< Team size <=20 Team size < = 10
Duration > 6 Large Large Medium
Calendar Months
3 Calender months Large Medium Small
<= Duration < = 6
Calender months
Duration < 3 Medium Small Small
Calender months

Process Tailoring – Definitions
OSSP (Organization’s Standard Software Process) :

Inventory of building blocks (process pieces and support
tools)
Tailoring : Creating a process description (PDSP – Project’s

Defined Software Process) by adding, deleting or modifying
the activities of a process, such that the resulting process is
better suited for the project for achieving its goal.
Tailoring Guideline : Permissible rules for changing the

standard process of a project. Evolved to control the
deviation from the OSSP through tailoring.

Project Tailoring & Process Database
Organization’s
Standard Project’s defined
Software Process Tailoring
Guideline Software Process
Project Life Cycle

Metrics
Escalation
Templates
Methods
Project’s Software
Process Database Development
(Processes & Procedures Feedback, Plan
Templates Change Requests
Metrics
Project Data)
Refer Procedure for Process Tailoring,

andProtection
SBU Process
notice /Handbooks
Copyright notice
Estimation
Estimation is a measure to quantify software
• Size Refer Procedure for Estimation
• Effort
• Schedule
• Cost
• Productivity
Estimation is required:
 To determine if planned features are realistic in terms of
 Resources (Effort)
 Schedule, and
 Cost
 To determine resource planning during phases
 To allow project monitoring and controlling
Estimation Model (Historical data) is used to arrive at effort and defect estimation,
based on size input
Risk Management
Risk Management is a proactive approach towards damage control
Under risk management following activities are required to be carried out:
 Identify risks
 Analyze risks
 Plan risk mitigation
 Assess effectiveness of mitigation
Standard risks (Most Likely Risks)
 Functional Coverage/ Scope definition
 Schedule
 Financial (Cash Flow, Budget, Payment)
 Technology/Experience
 Performance
 Manpower
Non-standard risks are project specific
Risk Register is maintained to gather experience across projects, at
Business Unit and Organization level
Refer Procedure for Risk Management
Project Organization & Stakeholders
 Project Organization defines the roles and responsibilities of project

personnel
 SM is responsible for selecting and implementing the Organization Structure
for his project
 Project Manager documents the organization structure in the project plan
based on projects needs and constraints
 Key Stakeholders in the Project are:
External - Customer, Suppliers
Sales, Marketing and Account Management
Project Team – SM, PM, ML, Developer, Designer, Tester, QA, CM
Other Stakeholders – Corporate, SBU-Head, P&Q, F&A, HR, System
Administration
Refer Procedure for Project Organization
Quality Planning
PQP_Template
 Quality Plan acts as the base document for a project
 Assists to plan & conduct quality assurance activities
Project Quality Plan includes:

 Quantitative Quality Goals - Product & Software life cycle
 Tailoring/Deviations in project
 QA Schedule - PES, Review & Audit schedule
 Quality Gates
 Defect Prevention & Lessons Learnt from previous
projects
 Standards to be followed in the project
Protection
Refer Procedure notice / Quality
for Project CopyrightPlanning
notice
Project Goals
linked part of
Business SPI Plan
Project Goals Goals
• Project Goals are tailored from the SBU level goals based on
project needs and constraints
• Goals are defined in the Project Quality Plan and tracked
monthly
• Analysis is carried out by the PQM to plan for actions in
the event of deviations.

Importance of Guidelines/Standards
 Standardizes pattern of coding thus ensures coding consistency by

developers
 Reduces coding time
 Helps in maintainability of code
 Lessons learnt from past experience goes into the guidelines –
prevents coding defects and helps code optimization.
 Improves readability and thus decreases review time
 Org. Level guidelines & Project Level guidelines --- Tailored to suit
project specific requirements (incorporating the client specific / project
specific requirements)

Quiz
Q1 The organization level goals are defined in:
b) Software Process Improvement Plan
c) Quality Mgmnt plan
d) Procedure for Process Database
Q2 Project Quality Plan includes:

 Quantitative Quality Goals - Product & Software life cycle
 Tailoring/ Deviations
 Both the above
Q3 Some standard risks are related to:

 Resource
 Performance
 Both the above
Project Tracking

Project Management - Reporting
Customer
PR
SBU Head P&Q Head
CQR
System System Technical

PPR
Manager Manager … Controller PQR
Project Project Project

Config. Test
Manager Manager … Quality
Manager Manager
Manager
Project
Teams Refer Procedure for Escalation
Project Tracking - PES
PES is a milestone decision meeting
PES committee consists of SM, TC, FC & PQM. Any other person who can add value to
the PES may also be included, like HR and System Admin representative.
PES involves the following decisions by PES committee:
 determining the status of the results and deciding on acceptance of the finished
process steps
 checking planning and deciding on release of the planned process steps.
Four types of PES are:
 Start, Status, Acceptance and End
 Start & End PES are mandatory
Aligned with Quality Gates

 Start PES – QG2, End PES – QG5
Protection
Refer noticefor
Procedure / Copyright
Project notice
Tracking
What is a Quality Gate?
A Quality Gate in simple terms is a checkpoint performed at defined
milestones within a project to ensure that the (interim) results of the
milestone are achieved as per the plan.
The results are assessed with regard to the quality and completeness,
to make decisions on the next steps.
ReferProtection
Procedure for/ Copyright
notice Project Tracking
notice
Benefits of Quality Gates
Quality gates:
 Enable a structured quality assessment of the work products
 Highlight any non-conformances
 Indicate risks upfront
 Trigger actions required to address lacunae
 Force the initiation of preventive measures

Prior to Contract
QG1
Acceptance
Contract Acceptance
Page 30
Start Prior to Project
Planning for QG
QG2
PES Plan Approval Requirements
Sep 2007
Design
Prior to Start of QG3 Coding & UT

Independent Testing
For Internal Use only

Integration Testing
Positioning of Quality Gates
System Testing
Prior to Shipment
QG4
End Prior to Project Acceptance Testing

QG5
PES Closure
P&Q
Configuration Management

Configuration Management
Configuration Management is the art of identifying, organizing and controlling

modifications to the software and its work products being built
Key components of Configuration Management Plan:
• Software work products to be placed under configuration library –
Configurable Items (CI)
• Process for entering and checking out any object from the Project
Library
• Project Baselines
• Change Control Strategy
• Backup & Restoration Process
• Release Management Release Notes
• Configuration Audit Schedule

Refer Procedure for Configuration Management
Incorporating a Change into the
Current Configuration Baseline
Change Requests
Impact New Version of

Analysis System Baseline
Approval of Change No Rejected

Request from CCB
Regression Tested
Yes Components
Approved
Change
Design &
Regression
Implement
Testing
Changes

Life Cycle Models

Life Cycle Activities
A software life cycle is the period of time that begins when a software
product is conceived and ends when the software is no longer available
for use
Software Life Cycle Model - The set of generic development activities
to be used on software projects and the order in which they are applied.
Life Cycle Models

WATERFALL
V Model
Incremental
Agile

Quality Audits

Quality Audits
Check conformance of practices w.r.t defined QMS standards

Verify effectiveness of Quality system in meeting quality objectives
Identify areas of Improvement / Strengths
Project Audits
–Process Audits – Bi-annual
–Internal Audits - Bi-annual
–External/Surveillance Audits – Bi-annual
Other Audits
–Config audits by PQM
–Audit of System Administration, Purchasing, Training etc.
–Risk Audit, Audit by Senior Management
Refer Procedure for Internal
Protection notice Quality System
/ Copyright notice Aud
Yearly
Page 37audit plan is2007
Sep available on QMS Portal
For Internal Use only P&Q
Completion Phase

Project Closure
 Project Closure is an important phase of the project

 It signifies completion and needs to be done in a structured way
 Activities performed during Project Closure

– Acceptance Certificate from customer
– Customer Feedback
– Capture of project related experience and information, in the form of
Lessons Learnt
– Transfer of Project team to new assignments
– Return of Project assets to owners
– Updation of Organization Process Database (lessons learnt, DAR
reports, Project Metrics, Project Risks, etc)
– Closure of contractual matters, if required
– Archiving of project assets
– End PES is held
Lessons Learnt
Project Information
================
Project Name
Domain
Project Type (Prototype /Enhancement / Development /Maintenance)
Duration of the Project
Project Start Date
Project End Date:
Customer Information
==================
Name of the Customer
Customer Category (New / Existing)
Lessons Learnt during the Project Execution

=====================================
No. of Risks identified at the initial stage

No. of Risks Encountered
Problems Encountered (Apart from Risks)
Solutions Offered to the problems
Open Points / Issues (Where solution not found)
Customer’s Support towards the project
Achievements of the Project Team (Including Customer Satisfaction)
Recommendations of the Project Manager

Continuous Process Improvement

Process Performance
What is Process Performance?

 It indicates the stability and capability of processes within an organization
Process Performance involves:

 Identification of Quantitative metrics for monitoring quality and process
performance at the SBU Level
 Identification of Sub process monitoring at project level for statistical
analysis
PCBs (Process Capability Baselines) are generated to analyze

process behavior of completed projects

Process Performance Improvement
What can be improved ?

 Reducing Development Cycle (Control Time, Cost, Quality)
 Improving Productivity through Reduced Effort/Cost
 Reducing Variation by stabilizing processes
 Reducing slippage in defects
 Increasing Resource Utilization
What are Methods ?

 Use of Tools and Technology
 Statistical analysis and action planning
 Causal Analysis and Resolution – Preventive measures
 Innovative Training Methods
 Initiatives

Process Change Triggers
Business Need
SMS SLC
QSIT (FDA)
Others
Initiatives
FIT4More
ISO 20K PM@Siemen
s
ISO 27001
Tools
P-CMM CAR (Corrective Action
Request) is raised to initiate Technologie
CMMI s
process change in QMS
Standards
Feedbacks
Project QA
Employee
Feedback
Refer Procedure for Process Improvement Protection notice / Copyright notice
Metrics, Audit
Page 44 & Maintenance
Sep 2007 For Internal Use only P&Q
How to use the QMS
 Templates for Technical documents

 Procedures for guidance
 List of Deficiencies (LOD) and Review Report
 Document Guidelines
 Coding Guidelines and Standards
 Raising Corrective Action Requests (CAR)
 Viewing the status of NCs
 Project Documents
 Knowledge Repository, Metrics Repository
 Estimation Model
 Lessons Learnt
 Training details and training material for self learning

Quiz
Q1 The CAR mechanism is defined in the following procedure:
b) Software Process Improvement Plan
c) Procedure fro Defect Prevention
d) Procedure for Process Database
Q2 Frequency of surveillance audits is:

 Once a year
 Once in two years
 Once in 6 months
Q3 Quality Gates are aligned to:

 PES meetings
 Project Review meetings
 Board meetings
QMS Site Demo
QMS Site:
http://132.186.193.50/
http://intranet.sisl-
qms.siemens.co.in/
Contents for QMS Site Demo
a: Login / Registration / Password/profile update

b. Accessing procedures and process assets
c. Updating project catalogues / repository
d. Knowledge database
(Car/Checklists/Coding Guidelines / Planning and tracking
guidelines)
e. Training related

QMS Portal – Home Page

Any Questions?

Thank you for your attention!


QMS Orientation TRNG - Induction Sep07

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

QMS Orientation TRNG - Induction Sep07

Încărcat de

Drepturi de autor:

Formate disponibile

QMS Orientation

Induction – Sep 2007

Protection notice / Copyright notice

To enable participants understand the SISL Quality

Protection notice / Copyright notice

Protection notice / Copyright notice

Somebody got angry about it, because it was Everybody's

It ended up that Everybody blamed Somebody when

Protection notice / Copyright notice

How do I figure out where I want to go?

Protection notice / Copyright notice

ISO 9001:2000 CMMI

Metrics, Lessons Learned

Protection notice / Copyright notice

SISL shall endeavour to deliver high

Refer Quality Manual

Protection notice / Copyright notice

• A project consists of a managed set of activities undertaken,

• A project is characterized by:

Refer Procedure for Project Planning

Risk & Issue Management •Risk Management Plan

Risk Management Plan covering •Tailored Documents

Tailoring of QMS processes and documents to suit customer

Protection notice / Copyright notice

Protection notice / Copyright notice

Protection notice / Copyright notice

Protection notice / Copyright notice

OSSP (Organization’s Standard Software Process) :

Tailoring : Creating a process description (PDSP – Project’s

Tailoring Guideline : Permissible rules for changing the

Protection notice / Copyright notice

Project Life Cycle

Refer Procedure for Process Tailoring,

 Project Organization defines the roles and responsibilities of project

Project Quality Plan includes:

Protection notice / Copyright notice

 Standardizes pattern of coding thus ensures coding consistency by

Protection notice / Copyright notice

Q2 Project Quality Plan includes:

Q3 Some standard risks are related to:

Protection notice / Copyright notice

System System Technical

Project Project Project

 Start & End PES are mandatory

Aligned with Quality Gates

 Enable a structured quality assessment of the work products

 Highlight any non-conformances

 Indicate risks upfront

 Trigger actions required to address lacunae

 Force the initiation of preventive measures

Protection notice / Copyright notice

Prior to Start of QG3 Coding & UT

For Internal Use only

End Prior to Project Acceptance Testing

Protection notice / Copyright notice

Configuration Management is the art of identifying, organizing and controlling

• Configuration Audit Schedule

Impact New Version of

Approval of Change No Rejected

Protection notice / Copyright notice

Protection notice / Copyright notice

Life Cycle Models