iso 9000 degree of conformity.

Inspection + Control of defects –> Quality Control

1940s – Statistical Quality Control
Processes with people and technology but without procedures are undisciplined
Processes with procedures and technology but without people are usually amateur
Processes with people and procedures without technology are inefficient

QA team supports Project Mangers with these activities

Attends kickoff
Provides QMS training
Facilitates process implementation
Approves tailoring
Conducts SQA verification
Conducts release verification
Collects metrics for the project
Supports NC closure
Attends closure

QA team supports Group Head and Delivery Group Managers with these activities

Highlights compliance issues in BIMS

Supports product pillar initiatives
Sends monthly Product pillar summary report
Conducts quarterly Knowledge Sharing Sessions (KSS)

The Process Groups will evaluate the changes to Organization level processes like
project management processes and engineering processes.
Periodic external audits are organized for the purpose of third party
certifications.
The QA team collects and summarizes metrics data periodically and helps project
managers analyze the metrics.
Process Performance Baseline (PPB)
Causal analysis help teams to learn better and initiate timely course corrections
when faced with issues.
The decision analysis process helps teams to select the right course of action when
you have multiple alternatives in front of you.
Decision Analysis and Resolution-Proactive Interventions.
process change request template available under QMS.
SSI is an ISO 9001 certified company and has been appraised at level 3 for CMMI for
development.
Capability Maturity Model Integration or CMMI is a process level improvement
training and appraisal program.

Level 1 Characteristics include,

Adhoc and chaotic processes.
No stable environment that support processes.
Success solely depends on the competence of people.
Tendency to over commit.
Processes are abandoned at the point of crisis.
Inability to repeat success.
there are No process areas at this level.
No appraisal or certification for this ‘Initial level’.

Level 2 Characteristics include,

Basic project management discipline is in place. Project Manager plan for the
project and set the processes.
Project processes are followed even during point of stress.
Projects are monitored, controlled and reviewed against the plan.
Projects are evaluated for their adherence to processes.
Deliverables are appropriately controlled and meet standards and requirements.

Level 3 Characteristics include,

Standard Processes Across the Organization to ensure consistency in performance
known as Organization’s Set of Standard Processes.
Projects tailor Organization’s Set of Standard Processes using guidelines to
create Project’s defined process.
Detailed definition of processes and standards.
Elaborate Engineering Processes.

Project management templates and a few engineering templates are available in QMS
however, most engineering templates are to be taken from OUM

Saas projects expected to use True cloud method

SSI QMS documentation has a three tier structure.

PRO<Process Area (3)><Process Serial No. (2)><Associated Doc type (1) ><Associated
Doc Serial No. >

X - General document
D – Delivery Framework
C - Checklist
T - Templates
W - Work Instructions
G - Guidelines
S - Standards
Achieve average ESM rating of 4.5
Defect leakage < 6%

Service level index 99% for P1 tickets and 90% for P2 and P3 tickets

People without procedures leads to Chaos.

Procedures without passion leads to Bureaucracy.

People with procedures and passion leads to Excellence.

Which is the tool/repository where the SSI Organization level processes, templates
and guidelines are stored?
GPA
OUM
QMS
IQA tool

-----------------------------------------------------------------------------------
------------------------------------------------------------------------

Oracle Consulting (OC) receives Request for Proposal (RFP) from Customer and shares
details to SSI Client Engagement Manager (CEM)
This contract is called as ICCPO in SSI.
PM needs to conduct a kickoff meeting along with PMO, QA, KM and QC.

PM gets project information from Bid owner during Bid Transition.

PM will conduct the closure activities.
The PM conducts the project kickoff.
MSPP template
Delivery process guidelines for scheduling
GPA task structure -> Financial management output
Update ETC monthly in BIMS after DBO refreshes effort data
Ensure Reusable/lessons learnt are uploaded into SIL as required.
: sending a release without release verification would make the project status in
BIMS to RED

Close all SQA check findings and internal audit findings within a week of being
raised.
Vertical Traceability
Provides trace from requirements to code and code to requirements.
Horizontal Traceability
Shows the relationship among requirements , objects or Modules. This would help in
impact analysis for any changes.
Bi-directional traceability is when both vertical and horizontal traceability are
present.
In SSI we use the following methods to show traceability. In release notes the list
of related documents are captured in the order of the lifecycle. During Peer
reviews the reviewer ensures that all the requirements are covered. For Saas or
cloud engagements the traceability is built into the accelerator assets.

Ensure all planned revenue has been recovered. ETC should be made to zero. Request
DBO to Close project in GPA
PM needs to update the Closure Report and conduct a closure meeting along with
PMO/DGM, QA, KM and QC.
PMO/QA will update the closure date in BIMS and the project manager needs to change
project status to Closed

For example waterfall, agile & incremental life cycles.

CMMI for Development is based on waterfall model, but adaptable to other life cycle
models

-----------------------------------------------------------------------------------
-------------------------------------------------------------------

ENGAGE, FOCUS, CHOOSE, VISUALIZE, CONFIRM, and, ENABLE

In SSI the following are used for gathering

requirements- RFP, Functional Design,
CIA output, Questionnaire and Configuration
workbook

Once all testing defects have been incorporated the solution can be baselined and
placed in the repository.

In SSI traceability is achieved by

Release notes
Peer reviews
Using accelerator assets for Saas / cloud

QC
Assess adequacy of Quality Control activities (Peer Reviews / Testing) within
project and update RAG status in BIMS (monthly or as per QC / SME calendar)
In Oracle SSI Beehive or GCDP is used as Configuration System.
Configurable Item or CI are any work product which are subjected to Change.
Project Manager is responsible for planning of review for all Configurable Items.

Examples of peer review methods include the following:

Inspections.
Structured walkthroughs.
Pair programming.

RCL is used to log the review comments of code, Engineering documents, project
management documents and Internal Testing defects.
In Deliverable Type do not use “Release Pack” option, this is reserved for QA.

DAR
if the solution is selected Update Decision analysis and resolution Document with
Final Solution Details and Inform Stake Holders
PPQA covers independent review of project processes, work products and services by
Quality Analyst against the applicable process descriptions, standards, and
procedures to ensure process compliance.

Process Product QA Activities in SSI include

SQA checks
Quarterly Internal Quality Audits
Release Verification
PM scorecard

Any non compliance is raised in the Business Information and Management

System(BIMS)Depending on the severity of the Non Compliance the issue is marked in
Red or amber in BIMS as per the RAG criteria.
QA Lead reviews the status of QA activities weekly and Coordinates with Stake
holders through Projects review meeting, mails for resolving escalated issues.

SQA checks
Process Compliance Score (PCS)
SQA findings
PM score

Release verification
RCL with findings

Internal Quality Audits (IQA)

IQA report in BIMS, with Non conformances/ suggestions/ best practices

CM tool is selected (SVN in GCDP is the preferred CM tool) for project repository

There are 2 levels of control- “Managed” and “Controlled”

“Controlled“ documents can be changed only if there is a change request and formal
review and approval is required for baselining
Level of control exercised for "Managed” documents is limited proper identification
through file names or versions. Formal change control is not applicable e.g.
Minutes of Meeting

Quality Champion Responsibilities

Plan Quality control measures along with PM (approach review, deliverable reviews,
audits, testing, tools and QC /SM Reviews) in line with applicable Delivery
Frameworks (DF)
Provide inputs to update Quality control and Configuration Management sections of
PMP
Set project specific naming conventions and development standards
Create/ tailor QC checklist and share with team for reference
Publish QC / SME Review calendar and perform SME Review and/ or validate
identified deliverables and certify quality of releases from projects
Assess adequacy of Quality Control activities (Peer Reviews / Testing) within
project and update RAG status in BIMS (monthly or as per QC / SME calendar)
Coordinate or perform root cause analysis for quality related issues in the project

Collect and share best practices and reusable's within and outside the project

Work Planning and Monitoring

Contains latest Progress Reports sent to the client, PMP, Project schedule, SMP,
Continuity Plans, KTR Metrics Sheets

Knowledge- learning
CAR, DAR, Reusables, Project End Report.

Issue Problem Management

Risk Logs/RAW, Issue log, Incident Log, Service Continuity Records

Release
Releases zip, RCLs, Release mails, Daily/weekly Health Check Reports(Annuity)

Version number of Test Case document and code in release packs is 1.1. This is
because the TC and code is baselined after peer review as 1.0 and updated to 1.1
after updating test results and incorporating code changes
all versions (Draft and Baseline) of the CI’s in the Configuration system

Release pack should contains the following:

Code and objects,
RCL with internal review and testing done and all defects closed,
Release note containing all the details in the pack i.e. Pack name and version
,Listing of all components of the pack in the order of creation, Reference to CR or
defect as applicable, Version number of all deliverables.

If the re-release effort is less than one day the Project lead or Project Manager
reviews the pack and releases else release needs to go through QA review.

Update the change history every time a document/ artifact is changed

Place all WIP and baselined documents in the repository
All configuration items should be checked into the CM Repository as and when the
documents are updated
Place all communication and commercials related communications in the respective
folders
Place status reports and minutes of meeting into the repository right after the
meeting
Ensure that the naming conventions mentioned in the PMP is used for the CI’s placed
in the repository
Move older versions/ draft versions of CI’s into archive folders

Why do we need metrics?

TO PLAN- Resource requirements, Effort and duration required for tasks, Scheduling
tasks.
To predict- Expected ESM, Effort to complete, Expected defects reported by the
client.
TO CONTROL- Assess gap between planned effort usage and actual usage and initiate
corrective action
TO PROVE- Performance (for example, On time delivery %), or
Deliverable quality (for example, Defect Leakage).

Process Metrics : Effort, Size and Schedule related metrics.

Product Metrics : Defect related metrics.
Service Metrics : Time and Effort related metrics or SLA’s.
PM metrics Request tailoring in BIMS
Enter Metric Goals into BIMS

QA Collects metrics from all completed of closed projects and places into
Measurement repository. Metrics Coordinator Consolidate metrics data for the period
(half yearly for dev and quarterly for services) and creates draft Process
Performance Baseline or PPB. Quality manager reviews the org level PPB and provides
review comments. Metrics Coordinator Incorporates any review comments and presents
the PPB to Process group for review. Quality Manager, Process group Coordinator and
Process Group reviews and approves org level PPB. Metrics coordinator publishes PPB
reports. KSS coordinator presents metrics trends to product pillar.
PPBs show the overall organization performance benchmark for the different metrics
used in the organization

Metrics at ssi are as follows

Effort related which include,
Effort Variation, and,
Effort Distribution.
Schedule related which include,
Ontime Delivery %, and,
Schedule Variation.
Quality related which include,
Internal Defect Leakage, and,
Defect Leakage.
Commercials and customer related which include,
Engagement satisfaction Measure, and,
Profitability.
There are also some Delivery Framework Specific metrics like,
EBS Upgrade metrics.

Goal >-8.0% to < +15%

EV% = [TAE-(AE+ETC)]*100 / TAE

TAE = Total approved effort (Original approved effort + Approved CR effort)
AE = Actual effort booked
ETC = Estimate to complete (effort left to complete the project)
ETC to be updated by PM in BIMS monthly

Schedule variance
Goal -4.0% to +4.0%
SV = Slippage * 100/Planned Duration
In actual calculation for slippage and planned duration, weekends are not
considered.

On time delivery is calculated only if there are 10 or more deliverables/milestones

in the project
Data points are from schedule data in metrics sheet and data sources include
project schedule and metrics sheet.
>90%

Defects have the following weightages – Observation=1 , Minor= 3 and Major= 5

Example- if 1 observation ,2 minor defects and 1 major defects were found in review
then
WRD= 1*1 + 2*3 + 5*1 = 12

IDL% = (WTD)*100 / (WRD+WTD)

*WRD = Weighted Review Defects
*WTD = Weighted Testing Defects

Goal - 20% to 40% for non Saas and 10% to 50% for Saas
Goal - less than 6 % for non Saas and less than 18% for Saas

EDL% = (WTDc)*100 / WRD+WTD+WTDc

*WTDc = Weighted defects reported by the client
* WRD = Weighted review defects
* WTD = Weighted testing defects

Data sources for IDL and EDL are RCL and Issue log or issue tracking system and
data points are review defects, testing defects and customer reported defects.

Profit > 25%

Data analysis tools used in SSI are,

BIMS for organization level tracking of Effort Variation, Profitability and ESM.
BIMS has an ESM dashboard providing ESM summaries at product pillar and org levels.
And Metrics data collection sheet is used at project level tracking of Effort
variation, Schedule Variation, On time delivery, Internal Defect leakage, external
defect leakage and effort distribution. The metrics sheet shows the monthly trend
of all metrics except effort distribution.