ONLY FOR REFERENCE

A
Main Project Report
On

Applying Six Sigma in Software Project

Development

Submitted for partial fulfillment of requirement for the award of

degree

Of

Post Graduate Diploma in Business Management

Of
Narsee Monjee Institute of Management Studies
Session 2020-2022

Submitted by
 ACKNOWLEDGEMENT
First, I thank my team lead, Mr. Vinu Krishnan, Assistant Manager of Sartorius
Automation team, for continuously providing the support, encouragement and
motivation during this project. His advices, suggestions and feedbacks were helpful
and made this effort an enjoyable one.

I am thankful to Mr. Ashok Purushotham, who is the Manager of system Engineering,

for the support and feedback for this project. I am very much thankful to the Head of
Project management, Mr. Prince Paul, who taught me the basics of Project management
and gave me opportunity to lead some of abroad projects. I am thankful to Rohit Raj,
Project Manager of Sartorius, who had shared tremendous knowledge about Agile
concept and Software project management methodology. He was very cooperative
during the interview and case study and provided us related material on the right time.

ii
 ABSTRACT
Most companies are smoking to keep their product quality at their priority. there are so many quality
improvement techniques are available in market for companies to improve their process as well as product
quality. They need support in these methods to apply on various areas of the process improvement.
6 Sigma and lean approaches very successful in manufacturing industries asset quality
improvement tool. With the help of these techniques many companies created so many success stories. In
software product development companies recommend high level of software quality to ensure that product
will not fail easily. So, most of the companies adapting 6 Sigma any practices in the development and
testing of software. There are no generic software quality solutions are based on six Sigma. but to improve
the process, companies can adapt applicability of Six Sigma.
In this project, we discuss the use of six sigma and lean methods in Sartorius Stedim ‘s automation
Software development.
Keywords: Software Quality, Quality Improvement Tool, Six Sigma and Process Improvement

iii
TABLE OF CONTENTS
Declaration .................................................................................................................................... ii
Acknowledgements ....................................................................................................................... iv
Abstract ......................................................................................................................................... v
Table of contents ........................................................................................................................... vi
List of tables ................................................................................................................................viii
CHAPTER ONE: OBJECTIVES OF THE PROJECT .............................................................. 1
1.1 Background to the study ............................................................................................................ 1
1.1.1 The Concept of Software Development ................................................................................................2
1.1.2 The Concept of Lean .............................................................................................................. 3
1.1.3 The Concept of Six Sigma ...................................................................................................... 4
1.2 Research Problem ..................................................................................................................... 5
1.3 Research Objectives .................................................................................................................. 6
CHAPTER TWO: SCOPE OF THE PROJECT ......................................................................... 7
CHAPTER THREE: EXECUTIVE SUMMARY .........................................................................8
3.1 Overview ....................................................................................................................................8
3.2 Problem Statement .................................................................................................................... 8
3.3 Solution .................................................................................................................................... 8
3.4 Opportunity............................................................................................................................... 8
3.5 Competitive advantages ............................................................................................................ 8
3.6 Model Of the solution ............................................................................................................... 9
3.7 Team......................................................................................................................................... 9
3.8 Submission .............................................................................................................................. 9
CHAPTER FOUR: RESEARCH METHODOLOGY............................................................... 10
4.1 Introduction ............................................................................................................................ 10
4.2 Research Design ......................................................................................................................10
4.3 Population of the Study ........................................................................................................... 10
4.4 Sample Design ........................................................................................................................ 10
4.5 Data Collection ....................................................................................................................... 10
4.6 Validity and Reliability ........................................................................................................... 10
4.7 Data Analysis .......................................................................................................................... 11
CHAPTER FIVE: LITERATURE REVIEW ............................................................................ 12
5.1 Introduction ............................................................................................................................ 12
5.2 Theoretical Foundation of the Study .........................................................................................12
5.3 Software Quality ..................................................................................................................... 12
5.4 Lean in Manufacturing Industries ............................................................................................ 14
5.5 Lean in Software Development ................................................................................................ 15
5.6 Six Sigma in Manufacturing .................................................................................................... 18
5.7 Six Sigma in Software Development Life Cycle ...................................................................... 27
CHAPTER SIX: DATA COLLECTION , ANALYSIS AND RESULT ......................... 32
6.1 Introduction ............................................................................................................................ 32
6.2 Existing system ....................................................................................................................... 32
6.3 Case Studies of various Projects .............................................................................................. 33

iv
CHAPTER SEVEN: FINDINGS, CONCLUSION AND SUGGESTIONS
7.1 Introduction ............................................................................................................................ 44
7.2 Summary of the Study .............................................................................................................44
7.3 conclusion ............................................................................................................................... 44
REFERENCES ..............................................................................................................................45
APPENDICES ............................................................................................................................. 52

v
LIST OF FIGURES

Figure 1.1 Relationships between Six Sigma and Quality ............................................................................ 1

Figure 5.1 The distribution of 7 QC tools in Six Sigma .............................................................................. 24
Figure 5.2 Check Sheet .............................................................................................................................. 25
Figure 5.3 Histogram ................................................................................................................................. 26
Figure 5.4 Pareto Chart .................................................................................................................. 26
Figure 5.5 Cause and Effect ....................................................................................................................... 27
Figure 5.6 Stratification ............................................................................................................................. 28
Figure 5.7 Scatter Plot ................................................................................................................... 29
Figure 5.8 Control Chart ................................................................................................................ 29
Figure 5.9 The distribution of other special tools in Six Sigma .................................................................. 30
Figure 5.10 Affinity Diagram..................................................................................................................... 31
Figure 5.11 High level process map ............................................................................................... 31
Figure 5.12 Kano Analysis ............................................................................................................ 33
Figure 5.13 SDLC CYCLE ............................................................................................................. 33
Figure 5.13 Critical to Quality ........................................................................................................ 34
Figure 6.1 Project Charter ............................................................................................................. 43
Figure 6.2 Process Mapping .......................................................................................................... 43
Figure 6.3 Process Flow ................................................................................................................ 44
Figure 6.4. Sipoc Diagram .............................................................................................................49
Figure 6.5 Cause and Effect Diagram .......................................................................................... 50
Figure 6.6 Improvement Targets .................................................................................................. 51
Figure 6.7 Pareto diagram ............................................................................................................. 51

vi
CHAPTER ONE
OBJECTIVES OF THE PROJECT
This chapter mainly discuss the motive to select the topic of Six sigma for the main project
and actions to done in the field. It has four parts- Motivation, Aims and Objectives and
the outline of the project report also mentioned.

1.1 Background to the Study

The companies and organization around the world are interested in quality of the product.
Six sigma approach is invented by Motorola, to improve the product quality by statistical analytic techniques.
Earlier this methodology is used by manufacturing companies like Ford, Toyota and GE. But recent
innovations state that Six sigma methodology can be implemented in Software Project Management. In this
report, we suggest the techniques to implement six sigma in software development Cycle of Industrial
Automation Project in Sartorius.
Our work can help to debunk the misconceptions about the applicability of Six Sigma in software
companies. And provide steps for software companies to implement Six Sigma.The scope of
this paper is demonstrated in Figure 1.1 which shows the relationship between Quality and Six
Sigma.

Quality

Software Quality
Quality

Six Sigma Process

(Motorola 1986) Improvement

Six Sigma ?

Figure 1.1 Relationships between Six Sigma and Quality.

1.1.1 The Concept of Software Development

Most of the software companies follows the (SDLC) as a standard practice for software
development. It has five components such as Requirement, Design, Development, testing
and Deployment and maintenance.

7
Requirement

Requirement gathering involves the analysis to determine the need of the software user.
Designing a new software requires a lot of information from customer to satisfy their
needs. It has been divided into two components requirement gathering which collects the
data and requirement analysis which analyses the requirement. In this stage the
requirement translates to software capabilities and product features into document. This
includes various use cases called user stories. User stories contains all the features of the
software to tackle the first.

Design

In this state, software engineers identify the technical component required to

deliver on requirements. The team decides software elements need to integrate with the
overall architecture of the System. Database to store new data, the designs of the user
interface and other technical details included in design phase.

Development

The ideal approach here is to use working exploded views. Tasks are typically
documented on a digital card with SDLC software and assigned to the appropriate
software developer. The developer is working on a task and sends the code to the
repository when the needs are over. This repository contains all the code of the developers
of the system or app you are building.

Testing

Testing is essential part of the software lifecycle. This is to identify the errors and fix it
which causes anything to damage the software. A software is the combination of several
components such as user interface and application program interface. If the complexity
increases mistakes will also increases.

Deployment and Maintenance

Once the software testing over it needs to implement for actual use. This phase is called
software launch. This will allow users to know the new features and what is changed with
the existing one. If any issues occurred after the launch of the software such as the
compatibility requirements, regular security updates or any bugs need to be corrected
from the product developer. It just ensures that the software provided is maintained well.
8
 The software development lifecycle will be improved by adapting and changing the
methodologies used. Agile practices, Kanban, waterfall, and lean Models are examples of
various SDLC practices. The implementation of Six sigma and Lean in the software
development will improve the productivity of overall performance.

1.1.2 Lean

Lean is a set of management practices to improve the efficiency and effectiveness by eliminating
waste. The main principle of lean is to reduce and eliminate non-value adding activities and waste.
This concept was introduced by American researchers from, MIT formalized and implemented by
Toyota. Lean techniques will be implemented in production as well as enterprises operation.

The steps to follow Lean.

Identify Value

This is to identify what value does the company follows. Also, it can be the solution of
a particular problem or feature to the product. When it comes to Sartorius it provides
Pharmaceutical equipment to produce vaccines. Any other activity which does not add value to the
organization then its waste.

Value Stream mapping

All the workflow of the organization will be mapped at this point. It must include all
actions and people involved in delivering the product to the customer. In this phase, the process
which does not bring value will be identified and enable them to reduce the waste.

Create Continuous Workflow

The value streams are measured then the next phases are to make sure that each teams workflow
is smooth. In order to avoid the critical situations. Each team’s work is divided to into small
batches and visualize the workflow.

Create a pull System

In order to stabilize the workflow, make sure to create a pull system in lean methodology. This
means that the work is pulled only if there is at high demand.

Continuous improvement
It’s a method to improve the overall system performance by correcting the problem and improve
the overall performance. There are different techniques to encourage continuous improvement.

9
The eight types of waste identified by the lean concept.
a) Defects
b) Over production
c) Waiting
d) Non utilized talent
e) Transportation
f) Inventory
g) Motion
h) Extra Processing

1.1.3 The Concept of Six Sigma

Six Sigma is a methodology to improve the manufacturing process developed by
Motorola. your brain is manufacturing as well as the business process the main agenda was to
reduce the defects and later, they focus more on the strategy of execution.
Six Sigma defined as three levels
a) Metric
Six Sigma symmetric is used to measure the deviation external set of data. the
standard normal distribution also called gaussian distribution.

In six Sigma it is equates to 3.4 defects per million opportunity so as a metric it

focused on reducing the defects. If mentioned here the defects are less than 68% of the
aims, then it is one sigma level. If their defects are 99.9997 seven of am then it is 6
Sigma level which equates to 3.4 DPMO.
b) Methodology
Diffuses methodology to improve the process.
a) managing the customer requirement
b) and learning the process to achieve its acquirement
c) analyzing the data to minimize the variation
d) rapid and sustainable improvement.

10
DMIAC
DMAIC is model to identify and solve quality issues. It is a model map do the real quality
problems and then to solve them.
Define: this race is to define the requirements and expectations of customer .it is to unlearn the
project goals with the customer goals. This can be the project scope the start and stop of the
process.
Measure phase: this is to develop data collection plan for the current process.it will collect the
data for the current process and need to calculate the current performance of the process.
Analyze: this face is to find out the gap between current performance and the goal.it will be
identified by analyze the current data.
Improve: the right solution defines the problem will be identified. the set of solutions to improve
the Sigma performance are selected based on root cause identified in analyze phase.
control: in this phase all solutions will be implemented to improve the performance. Also, the
changes are continuously monitored that the decided change is established for a long-term run.
c) Management system
Six Sigma also used to form business strategy to improve the opportunities of the
organization. This will unless its top down operations and it'll make some positive
changes in the operational activities. The purpose of this project is to implement 6
Sigma and Lynn practices do the existing automation software development in
Sartorius.

1.2 Research problem

Companies spend huge amount of money to invest for developing software. So, it is very
important that the software solution must be risk free. that any kind of malfunctions in
the software could make huge loss to the company. this software can be customer
relationship management software, or ERP software which plays significant role in the
company. these issues would affect the credibility of the organization will be reason to
lose customer. In this case, Sartorius is a pharmaceutical equipment manufacturer who
helps to manufacture vaccines.

this projects mainly focus on the quality issues facing on automation software solutions
and the required changes and techniques to implement in the software development
process.

Companies adapting various software development models based on the

application of the software. But the frequent changes in the requirement, additional
features and unskilled workforce may create software quality issues. So, this research will
11
identify the issues in software development process and to reduce defects caused due to
deviation of process.

1.3 Research Objective

The main aim of this paper is to provide Steps for software companies who want to
implement Six Sigma for process improvement. To achieve that, following objectives
shallbe reached:

 Identify the differences of Six Sigma in manufacturing and software companies.

 Discuss the acceptance of Six Sigma and lean in software product development
 Identify the state-of-art of Six Sigma in software.
 Screen out the suitable Six Sigma tools and techniques to implement in my
organization.
 Discuss the scope of improvement in the process of software development.

12
CHAPTER TWO

SCOPE OF THE PROJECT

Organizations around the world are showing great interest in quality. The growth of
Japanese industries and their success made the world to think about quality issues. This
made the invention of various quality tools. This report will provide the technique of
implementing Six sigma and Lean practices in software development.

Project scope. This Project requires the error history of previous projects and the complaints
raised from customer after the delivery. The cause of error, quality issues and other external factors
will be investigated, and the feedback will be given to the team members.

Deliverables Deliverables for the project will include a well-researched, 50-page article to be
delivered no later than November 27, 2021. Five related and linkable articles, expanding on points
in the main article will be delivered on that same deadline.

Acceptance criteria. Relevant examples and case studies must be included to identify the problem.
Also, the improvement techniques must be with the existing system. Not by inventing a completely
new system.

Exclusions. All the confidential data of the organization will not be revealed during. Project will
give suggestions and improvement techniques does not involve any personal harm.

Constraints. The project is restricted to limited samples only and the report is prepared for
academic purpose. All the confidential data from the organization is protected.

13
CHAPTER THREE

EXECUTIVE SUMMARY

3.1 Overview

Software quality is very critical factor in industry. Even though the software products are
designed, developed and tested the actual software faces quality issues either in inhouse
implementation or at the customer site. This creates huge loss of money and breach of data and
security of the organization and will be cause of losing customer. So, software product developers
must improve the quality of their product and way of conducting work.

3.2 Problem Statement

Software quality issues of automation software development and the cause of issues are being
analyzed. This will identify the issues and provide solutions to rectify the software quality issues.

3.3 Solution

Software quality issues can be rectified by understanding the common problems in software
development. Firstly, organization must analyze the requirements from the customer is matching.
Also, how the unnecessary delay and features can be reduced by assessing the common problems.
To implement the changes and analyzing the issues of existing system must be rectified by
implementing the quality practices such as Six sigma and Lean in software development. This
would help to identify the issues and improve the process flow.

3.4 Opportunity

This would open wide range opportunities to reduce the production hours and improve the
software quality. Having a practice of six sigma in software development create a brand name for
the organization and bring more orders. The process itself drive the product in high quality also
these quality standards protect the customer that the requirement is matching with product
features.

3.5 Competitive advantages

Improved performance makes the organization more reliable among customers and consider the
organization as trusted partner. The reduced production hours make the organization more
productive and save the number of man hours. This automatically improve the profit of the

14
organization. If organization faces less complaints from customer, then this improve reliability
of the software and reduce the man hours to solve the issues.

3.6 Model Of the solution

By implementing lean, the organization can identify the waste of resources such as the
additional unnecessary features and frequent changes in the software and the entire design. In
addition, by introduction of six sigma could evaluate all the process and identify the common
issues. This will not only improve the quality of the product but improve the overall efficiency
of the organization.

3.7 Team

The entire automation team can suggest the problems related to the work. These can internal or
with cross functional team. Once the problems are identified in each phase of the software
development then solutions and improvement would be derived from the quality practices.

3.8 Submission

The essence of six sigma and lean will be depicted with this project and its impact in Software
development Life cycle will be analyzed and implemented based on the studies.

15
CHAPTER FOUR
RESEARCH METHODOLOGY
4.1 Introduction
This chapter provides a detailed description of the research approach adopted in this study.
Research design, target population, research instruments, data collection and analysis methods
used were presented in the subsequent sections.
4.2 Research Design
This study used descriptive research. Descriptive research involves gathering data that
describe events and then organizes, depicts, and describes the data
collection. Visual aids such as graphs and charts
to help the reader to understand the data distribution and therefore offered a better
clarification on the quality standards and its necessities and effectiveness in software
development.
4.3 Population of the Study
Some of the recent projects and its errors are analyzed and the case studies of famous software
firms and their methodologies and result will be carefully analyzed to find the conclusion.
Various software development techniques and its pros and cons also will be depicted to implement
the changes.
4.4 Sample Design
Various case studies and research papers for software development is analyzed to find the solution
of the problem. The source of the theories from Textbooks and the research paper of six sigma in
software project management.
4.5 Data Collection
The research made use of primary data, which was collected using structured
questionnaire distributed to the employees of the organizations, and the rest of the data is collected
from the software project managers of various IT industries to collect the practices from their
experience. The administered questionnaires were collected after
completion by the respondents on the same day and their responses used for analysis.
The questionnaire had both open-ended questions to understand the problems in process and
collected relevant data from the other sources about the latest quality practices in software.
4.6 Validity and Reliability
To achieve content validity, questionnaires included a variety of
questions based on project management and software development was distributed and collected
the suggestion from various sources. The internet and various theses on project management and
16
agile practices helped to form a conclusion on this issue. These findings are submitted to the
organization under the supervision of our project team lead and approved the suggestions are
relevant to apply for the continuous improvement.
Reliability can be ensured by minimizing sources of measurement error like data
collector bias. Data collector bias was minimized by the researcher’s being the only
one to administer the questionnaires, and standardizing conditions such as exhibiting
similar personal attributes to all respondents, e.g., friendliness and support.
4.7 Data Analysis
The data is analyzed as predictive and qualitative methods to understand the historical data as
well as researched data. Its asses the qualitative approach of raising the concerns of what is the
problem and how the issues are rectified by assessing the quantitative measurements and historical
data of the defect of software. The historical data will be analyzed by predictive methods and
analyzed to form the cause of the defects.

17
CHAPTER FIVE
LITERATURE REVIEW
5.1 Introduction
This chapter provides, through selective reference to some of the literature, a clearer
understanding of software quality and Quality practices. It also outlines previous research findings
on the quality in software development.
5.2 Theoretical Foundation of the Study
The demand of software product in market and its quality got paramount importance in
this sector. Companies develop of purchase software for wide variety application so the quality of
the product could always create a positive impact in the way of doing business. Any bugs or
software issues could create a huge loss for company. This will also lead to legal disputes and
create very bad impression to the developers. in this project, the quality practices of Six sigma and
Lean has adapted to improve the quality of automation software. The master thesis of Adnan
Rafiq and Long Zhang on the topic of "Applying Six sigma in software companies" referred to
form the theoretical foundation for the project. The thesis of Ljubomir Lazica, SIEMENS on
Software Testing Process Management by Applying Six Sigma is also referred for the practical
implementation six sigma in Sartorius.

It has been suggested that the various techniques to identify the issues in the process and the
common problems raised due to lack of knowledge. This would also improve the process as well
as the product to achieve success. Six sigma and Lean are basically used in manufacturing
industries to reduce the defects but its application in the process improvement helps to software
companies to adapt these methodologies to identify waste and improve the overall efficiency.

5.3 Software Quality

Software quality Engineering is an approach with every aspects of the software development
process. It is Set off systematic activities providing the evidence of the ability of the software
process to produce a software product that is fit for use. it also provides the assurance that the
product performs as specified is the role of product assurance. SQE has the assurance approach to
three attributes of SDP. quality process and management leading to these SQE components.

18
In software development the process is divided into 5 faces suggested requirement analysis
planning Cody testing releasing and maintenance. this face is commonly called SDLC. within
each project phase, it ensures that, the goal of each phases is achieved.
The Attributes of software quality.
a) Functional stability
This attribute Determine that the actual requirements and specifications are matching with
the software. Most software testing professionals view this is very important for the
application. In software test, this all the functionalities and the requirements will be tested
to ensure that all the customer requirements are matching with the software.
b) Reliability
Reliability is an attribute of the systems use for the ability to continue to operate at the
predefined conditions. It ensures that system can connect with the external elements such
as the database and the network connections.
c) Interoperability
This is the ability of the system to communicate to another system solve certain task. This
involves information transfer and controllability of the system with another system. The
software tester must understand and test these features.
d) Performance efficiency
This shows the response of the system to perform certain actions for a certain period. The
performance will be calculated by latency and channel capacity.
Latency is the time spent on responding to an event
Channel capacity is the number of events that occur at certain point of time.
e) Security
Security is a must feature to reduce the malicious or accidental actions as well as the
possibility of theft or loss of information. Several measures are used to protect systems
such as encryption and audit.
f) Compatibility
it measures the compatibility of the operating system and other default features such as
internet and media connectivity. It analyzes
g) Maintainability
It means the maintainability of the software. The software will be tested to analyze that the
software will be maintained by updating the features and its operability of other systems or
application.

19
 h) Transferability
The ability of the software to migrate for useful activities. This involves upgrading for the
highest version or to work for different platforms.

5.4 Lean in Manufacturing Industries

Lean is known as a methodology to reduce the lead time and operating costs and improved
product quality. It’s based on reducing the wastes in manufacturing operation. It gives the
indication that the waste is something which doesn’t add value that the customer is willing to pay.
So, this technique eliminate waste by continually improve a process. This deliver process
improvements; lean manufacturing sustainably delivers value to the customer. There several types
of wastes hindering the organizations performance. This includes process, activities, products or
services that require time, money and skill but does not create a value for the customer. These are
underused talent, excess inventories and wasteful process.
The benefits of lean
Eliminate Waste: Waste is considered as negative factor for cost, deadlines and resources. It does
not add any value to products or services.
Improve Quality: quality improvement makes the company to stay competitive and meet the
changing needs and wants of customers. The process must be designed to keep the quality
improvement at the forefront.
Reducing Costs: Over production and underutilization of materials than creates high storage costs,
which can be reduced through better processes and materials management.
Reducing Time: Inefficient work practices while more efficient practices create shorter lead times
and allow for goods and services to be delivered faster.

Mura: These are waste raised due to the change of customer requirement or change in work
process. The mistakes of design documents and change in process are the cause of these wastes.

Muri: This waste raised due to over burden of work allocated to employees. The proper resource
allocation and amount of workload must be determined. Time can be wasted as people switch
tasks or even lose motivation due to being overburdened.

Muda: This is a process related waste. It can be considered unnecessary waste of time due to
meetings and unwanted discussion. Example manually claiming the expenses or bill and
unnecessary approval to pass orders and bills are process waste.

20
Advantages and Disadvantages

Lean manufacturing carries several advantages and disadvantages.

Advantages:
1. Saves Time and Money

Efficiency in workflow, resource allocation, production and storage can benefit businesses
regardless of size or output. Also, this would reduce the cost of production. Once the time and cost
are reduced it make the product available on time.

2. Environmentally Friendly

Reducing waste and improved process would save the costs in energy and fuel use. This would
save the environment by not getting polluted by the over production. Electricity and water are
valuable resources which must be protected to utilize.

3. Improved Customer Satisfaction

If the delivery time is reduced customers would be happy. This is essential to business success as
happy customers are more likely to return or recommend your product or service to others.

5.5 Lean in Software Development

Lean development is the application of lean principles to software development. other than
manufacturing industries lean can also be applicable in software development.it provides a way to
optimize the production line to minimize waste and maximum value to the customer.
manufacturing and software development are not similar operations. lean is perfectly suitable for
manufacturing plant due to the repetitive work and similar products manufacturing. this will help
the organization to identify the major waste generation from the manufacturing process. but in
software development it is completely belongs to the developer’s mind. it is a creative task which
it needs immense focus and creativity. Knowledge in the programming language and the features
of the software must be analyzed to develop a software product. Applying lean principles this
after development request how the value and waste can be identified during the process.

21
Seven Lean development principles
1) Eliminate waste
The key element of clean is to eliminate the waste. that means that two does not add any
value to the customer.
In software development these wastes are identified by Different methods.
a) Unnecessary code or functionality
This means unnecessary features of software which consumes more time the code and
it doesn't help to add as a feature based on customers requirement.
b) Starting more than that can be completed: this means the unnecessary complications
over the system put yourself in contact switching handoff delays and other
impediments to flow.
c) Waiting: The more time waiting for requirements or approval means wasted utilization
of software developers.
d) Decentralized development team: centralizing the team members is it best away to
reduce the time of contacting them through mail, call and conference call. email is not
considered as the most efficient communication tool to solve problems.so face to face
interaction is better to communicate effectively within the team members.
e) Gold plating: if the software development team spends too much time and effort to
develop a special feature which it doesn't add value to the customer, then it's a waste of
time. this is called gold plating.
f) Underutilizing available toolsets or platform: code generators are used in software
generation to develop the software much efficient way. but there are cases that the code
generation tool not fully utilized to generate the code. this will create in completed
codes which make the programmer to identify the issues and errors in the generated
code. this is considered a waste of time also the tool is not properly utilized. the
organization provides training do use tools to generate the code more effectively.
g) Partially done work: partially completed work does it make any value to the customer.
it also makes the developer or tester to put more effort to identify the uncompleted
tasks in the project.
2) Build Quality
It seems every team has to develop her build quality into their work .in trying to ensure
the quality many teams actually create waste through execute testing or excessive logging
of defects .In order to build quality the certain methods are developed in the software
development process.

22
 a) Pair programming: in order to avoid the quality issues, the program will be developed
by two developers instead of one.
b) Test driven development: it's a criterion for code before writing the code to ensure that
the business requirements are matching.
c) Incremental development and constant feedback
d) Minimize wait states: Diffuse to reduce the contact switching knowledge gap and lack
of focus.
e) Automation: the use of automation in software development is to reduce the repetitive
work and to avoid the human error.
3) Create knowledge
Knowledge sharing is part of lean development. this principle increases the team to
provide infrastructure to properly document and retain valuable learning. this can be done
by using various tools.
a) pair programming
b) code reviews
c) documentation
d) thoroughly command codes
e) knowledge sharing sessions
f) training
these are best methods to create knowledge and share with the team members.
4) Defer commitment
this principle is to increase the team to demonstrate responsibility by keeping their
options open and continuously collecting information rather than making decisions without
enough data.
a) Not plan for months in advance
b) avoid committing to projects or ideas we thought understanding the business
requirement.
c) constantly be collecting and analyzing information regarding decisions
5) Deliver Fast
Fast delivery is very important in projects. but the focus of Lean principle is not to focus
on the fast delivery but to understand the reasons to slows them down.
a) Advanced thinking for the future requirements
b) blockers that are not responded to with urgency
c) over engineered solutions and business requirements.

23
 6) Respect people
This emphasis affective communication with all the team members to understand various
philosophes he's off to developments and aspects of the operation of team, and the way of
communication and how to handle the conflict. onboarding new team members and train
them if very important in the team development.
a) Communicating proactively and efficiently
b) encourage healthy conflict
c) surfacing any work-related issues as a team
d) Empowering the team members to do their best work
7) Optimize the whole
Optimization is an issue in software Development. if the developer is pressurized to deliver the
project. then it may not make the quality requirement. this increase the complexity of the codebase
resulting more defects. If the defects are more there is more work to do putting more pressure on
developers to deliver quickly. The second issue is with the testing when the testes are overloaded
integrates a long cycle time between the developers the code and the testers to give the feedback.
This makes the developers to write the code continuously which may or may not be a defective
code which results in creating more defects so requires more testing.

5.6 Six Sigma in Manufacturing

Six Sigma is an approach invented by adopting so many quality tools for the process
improvement. in addition to that it has invented its own tools and techniques based on the quality
requirement. So, the seven quality control tools are depicted here. These tools are applied in each
phase of the 6 Sigma.

Cause-effect Diagram Flow Chart Flow Chart Scatter Plot Control Chart
Pareto Chart Histogram Pareto Chart Control Chart Flow Chart
Check Sheet Cause-effect Diagram
Histogram
Control Chart

Figure 5.1 The distribution of 7 QC tools in Six Sigma

1) Seven Quality Control Tool

a) Check Sheet

24
 This method is used to collect data the required characteristics of the process. If the data
collection is wrong, it will lead to a failure. This tool is using in the measure phase which is
represented in tabular form.

Figure 5.2 Check Sheet

b) Histogram
It is used in the analyze phase. This tool is helped to learn about the distribution of the data
collected in the measure phase. The collected data at this phase will be huge. So, the data can be
divided into different class or intervals. So, the area of each rectangle is proportional to the
number of observations within each intervals or class. If we sum the area of all rectangle is equal
to total number of observations. 50 readings are required to get a good shape of distribution.

25
 Figure 5.3 Histogram
Pareto Chart
This chart would give the idea that which problems need to be addressed. It is related to the 80/20
rule found in business economics. This chart has two main functions. The first in the define phase
it helps in the selection of the appropriate problem. Secondly it will assess the causes lead to so
many problems.

Figure 5.4 Pareto Chart

26
Cause and Effect Diagram
Cause and effect diagram are known as fishbone diagram. Cause and effect diagram used to find
all the possible cause of a problem. It’s the first step of solving a quality problem by listing all the
possible causes. The reason behind the name of Fishbone Diagram is that it looks like a Skelton of
fish. The head of the fish is considered as a problem and the main causes are the ribs and the
detailed causes are the small bones.

Figure 5.5 Cause and Effect

Stratification
This is used to divide the collected data into subgroups. The special cause of variation in data
would be identified using subgroups. This tool is used very less compare to the other quality tools
and it is used as to improve the phase. The collected data will be stratified in different groups.

27
 Figure 5.6 Stratification

Scatter Plot
This is to define the relationship between two factors, and this will enable to identify the
correlation pattern. The main function is to identify the correlation pattern. The correlation pattern
would help to understand the relationship between two factors. In this tool the input variables are
plotted on the X axis and the output variable is placed on the y axis. The values of the scattered
points would provide the details of the process can be improved.

28
 Figure 5.7 Scatter Plot
Control Chart
The control charts are known as Statistical Process Control. In six sigma methodology it is used
in analysis, improve and control phase. In analyze Phase Control Chart is helpful to identify that
the process is predictable or not. Special cause of variation will be identified by improvement
phase. And the process performance will be verified by the control phases. The two main
purposes of control chart are the creation of a process with stable variation and the second is to
detect the change in the process.

Figure 5.8 Control Chart

29
Special Tools Used in Six Sigma

Brainstorming Spreadsheet Process Mapping Project Management Methods ANOVA

Affinity Diagram MSA Kano Analysis FEMA Correlation and Regression
SIPOC Diagram VOC Method Stakeholders Analysis DOE
Process Documentation

Figure 5.9 The distribution of other special tools in Six Sigma

Brainstorming
It is a technique for a group to find a solution for a specific problem by amassing all the ideas
spontaneously by its members. This technique is used to find ideas related to specific problem as
many as possible. This technique motivates people to generate new ideas based on their opinion.
This would make the environment more comfortable and participant feel free to announce their
minds it will produce more creative ideas.
It must follow certain steps.
a) First step is to define the problem which you want to solve. The problem must be clear to
generate best ideas. It must not have any misleading factor.
b) Time limit and idea limit is important in the meeting. Also, the size of the team and
criticality of ideas decide the limits.
c) Everyone’s ideas must be noted down and it must not have any criticism.
d) The best ideas will be selected after the time limit.
e) The criteria of the of selecting the ideas must be clarified.
f) Score points for the idea must be added
g) The highest scored idea will have the best solution for the problem.

Affinity Diagram
This is used to organize large number of data into logical categories. in this diagram they
used to refine the ideas generated in brainstorming which needs more clarity. the ideas must be
sorted from the brainstorming's sets and create groups of related ideas.
a) ideas will be grouped based on their common objective.
b) ideas will be clarified by using questions
c) the white characteristics of ideas will be copied to more than one affinity set.
d) combine similar affinity sets into one and breakdown the complex sets.

30
 Figure 5.10 Affinity Diagram
High level process map
This Diagram is a 6 Sigma tool used to identify all the process elements. the factors must be
predefined for not forgetting anything which influence the process improvement.

Figure 5.11 High level process map

31
Measurement system analysis
this is called measurement capability analysis which is used to assess the capability of process
measurement systems by using experimental and mathematical methods. the main purpose of this
tool is to improve the measurement system and to ensure that unbiased results must be provided.
The factors that influence the measurement systems are
a) cycle time
b) cost
c) stability
d) bias
e) linearity
f) responds to control, variable correlation and autocorrelation
g) Gage R&R (repeatability and reproducibility)
Voice of the customer
this method is to identify customers requirement for high quality product. customers backgrounds
will be different and their common customers, suppliers, product uses partners. the customers are
employees from different departments. so, in this case there are several ways to analyze the voice
of customer. the requirements of the customer will be taken by interviews, so this, observations,
customer specification complaint logs.

Kano Analysis
This quality tool is to prioritize customer requirements based on their satisfaction. All the
identified requirements are not equally important, so this tool help to rank criticality of the
requirements.

Must be these needs are basic needs which no need to discuss. Example a selling a laptop with a
power adapter.
Delighters: There needs which provides unexpectedly with customer. So, customer will get happy
with this feature. It can be gift voucher after the purchase. An additional security tool with the
purchase of a software.
One dimensional: These are the needs which need to be discussed and negotiated such as price. If
any of the features are added or any discounts from the price is considered as one-dimensional
features.

32
 High

Delighters
One Dimensional

Poor Good

implementation
Must-Be

Low
Figure 5.12 Kano Analysis

5.7 Six Sigma in Software Development Life Cycle

Figure 5.13 SDLC CYCLE

33
a) Requirement gathering and Analysis
In software requirement management is very important. Companies uses various software
Development model in the field of software. The primary goal of six sigma is to align customer
requirement and objectives. The DMAIC phases are focused to meet the expectation of
customer.
Using the Voice of Customer
The voice of the customer is six sigma technique which is used to understand the customer needs.
The project team would collect the data from customer reactively and proactively. Direct and
indirect meetings with the customer is important to assess the customer requirement. These are
the main practices in Six sigma and Agile methodologies. Using VOC, the internal team meeting
to review the project would be more effective. The objective of these meeting is to review and
prioritize the functionality to be developed.
Steps for collecting VOC
1. Identify all direct and indirect customers affected by the upcoming review meetings.
2. Prepare targeted Questionnaire for each group.
3. Answers for all the questions must be collected through direct conversation.
4. Review all the existing points and issues to rectify or giving clarification.
5. Prepare the review meeting with all the additional customer needs.
Building a Critical to Quality tree
Critical to quality tree helps to translate customer requirements to measurable characteristics for
the final product. The project team must convert the requirements into specific features in the
product. In CTQ tree the customer requirement will be expressed in non-product terms and
specific features that can be developed.
Sample of CTQ tree

Figure 5.14 Critical to Quality

34
Failure Mode and Effects Analysis for Design
FMEA is a tool required to understand the risk of requirement gathering from customer. In this
case the development team will analyze the potential failure point of the requirements. The team
evaluate the failure mode, the potential failure effect, the possibility of occurrence and the risk.
This would lead a cost benefit discussion with the customer and potentially avoid costly
implementation with little value. This lead to keep the team aware about the risk factors.

Design

Software design is to create the architecture of the software. It says about the requirement and
necessary features of the software. The overall structure of the software will be designed in this
field. So, the developer must program the software based on these requirements. Analysis phase of
Six sigma is used in this phase. The overall software requirements and features will be analyzed
and documented in this phase.

Flow charts

Flow charts are used to analyses the process of the software structure. The priority of the software
code creation and the structure of the software process will be defined in this phase. The actions
required for each phase or the decision and conditions of each section will be defined in this.

Cause and Effect

The requirements from the customer and the reason of the change and its impact will be defined
here. So, the cause and effect of systems will be analyzed in this phase. So, any cascading effect of
the software changes will be identified and analyzed at this phase.

Kano analysis

The necessary features and required changes will be analyzed in this phase. In this phase the basic
requirements, add on features and the negotiable features of the systems will be analyzed.

Software Development
The developer translates the design features into source codes. They create codes based on the
software design document and convert it into codes which will be utilized to develop the actual
software. This is the improvement phase of Six sigma. All the requirement and additional features

35
will be implemented by translating to source codes. In this phase, various improvement techniques
can be used to enhance the software. The quality of the software will be improved by proper
training giving to the developers and the improvement points from the previous projects must be
taken.

Project Management methods

Project management tools such as Pert, and Gant charts analysis is used to allocate resource and
the time required to finish software projects.
Failure Mode and Effects Analysis for development
This tool asses the risk associated with the development. The time required for additional features
and the cascading effect of the changes and the possibility of occurrence of the risk. The
development of certain software required different hardware and software configuration. This risk
needs to assess during the development.

Software Testing
Software will be tested after the development. In this case all the requirements and features will
assessed by the tester. All the defects of the software will be tested during this test. If any defects
found are assigned to be fixed. Retesting and regression testing is done until the point at which the
software is defect free. This is an implementation phase where all the features will be tested to
match the requirements from customer. The necessary changes to enhance the software quality
will be added.

Design of experiment
This is used for software testing; this would reduce large amount of time and cost. various users in
automotive, telecommunication and defense industries made Improvements in testing methods.
1) Focus attention on the usage of software
2)Mathematically sound way to spend the entire operating domain with the minimum set of test
cases
In this way the tester will try to break this after at every possible way to make it defect free.

The way of identifying problem is categories to three levels.

1. Detect and isolate all single mode faults. A single mode fault is a constant problem with
the presence of issues with the single parameter.
2. Detect all double mode fault. If any two parameters are wrong in the program, then
recreates consistent problems in different levels of system this is called double mode faults

36
 3. Multimode faults are the issues raised by multiple faults detected by the testing.
Deployment
Once the software is error free it will be implemented in the customer premises. In this stage all
actual condition will be assessed and tested. All the requirements of the software will be tested.
This is also implemented and the control phases. VOC and kano analysis will used to match the
requirement and additional features of the software.

Maintenance
The manufacturer of the software is responsible to provide support to the software till it used with
the customer. Updates of the software and integration with other systems. Software bug
rectification are certain points where the manufacturer responsible to do. In this control phase, all
the required conditions and changes are constantly monitoring to ensure that software running
smoothly.
Various tools of the six sigma can be used in software development Life cycle to reduce
error and create value to customer. It can define the requirements and measure the possibilities and
asses the preconditions to implement the changes and control the overall process. This would
make the Software manufacturer to identify issues and risk factors on each phase and rectify them.

37
CHAPTER SIX
DATA COLLECTION , ANALYSIS AND RESULT
6.1 Introduction
Ensuring software quality has paramount importance in software industry Firstly, the companies
must follow a software development model and should not deviate the process. There are number
of reasons to change process and deviate from the original requirement, but this would cause of n
number of bugs which affect the quality. Another reason is to change in the requirement from
customer. This cannot be denied by the manufacturer. But some requirement changes cause a huge
change in the structure of software which needs to reprogram. The cascading effect of these
changes cannot be predicted. So, these changes are a big threat to the software quality.
6.2 Primary Data
The primary data is collected from the project team leads and manger of the automation
department to understand the process flow.
. Existing system
Automation Software provides to integrate with the
Biopharmaceutical equipment. So, software error finally affects the vaccine manufacturing
Software Design
The existing automation software development in Saturdays follows the SDLC cycle. In the
design phase, all the necessary documents such as P and ID diagram, process flow diagram and
electrical schematics will be cross checked to understand the requirement. customers will have
different requirements based on their product and different standards will be used. this will create
an impact in the software design and the architecture of the system. The electrical and mechanical
components of the system will vary projects to project so the controlling parameters also will
change depends on customer. Some customers recommend only single systems with no external
communication and some needs to interface with other system. This would change the electrical
components and process. this all changes and requirements will be taken into the design
documents.
Automation Software Development
Once the design documents are released it would go for software development. The
development team will assess the design documents and they will start coding. The basic structure
of the software will be generated by the code generator and necessary changes and modifications
will be done by the software developer. If any changes in the process can be identified by the
software developer and change according to the process.

38
Software Test
The software will be tested by the testing team by analyzing the requirements from the
customer and with the software design documents. The defects and bugs of the software will be
identified and rectified at this phase. the process of the systems and it's interfacing with other
systems also will be tested at this phase.

Software Bench Test with Customer

The tested software will be presented to customer. The customer will analyze the functionalities
and features of the software. This includes the process of the system and the features of the
software and functionalities. The basic functionalities and features of the software cannot be
modified. Customer can suggest additional features which will be discussed to implement. Also,
the process of the actual system will be analyzed by the customer with the actual requirement. If
the requirements are not meeting or need to modified customer would raise the concern. These
additional changes and requirements will be discussed and implemented.

FAT (FACTORY ACCEPTED TEST)

The software will be integrated with the bioprocess equipment and the actual system will be
controlled by the software. It has various control elements such as valves and motors which will
be controlled by the software by monitoring process measurements of sensors and the required
process sequences. The changes from this actual will be analyzed and implemented.

SAT (SITE ACCEPTED TEST)

The system will be implemented in the actual customer functionality and test with the actual
parameters. The slight changes due to the actual functionalities will be analyzed and implemented
at this phase.

MAINTENANCE
Any issues related to the software will be rectified by the software team. This can be report,
security policies and system crash or hardware crash. The software development team must be
fully aware of these extreme conditions and do the precautionary actions.

6.3 Case Studies of various Projects

The data from various projects will be taken by direct interview from the software developer,
testers and Design team.

39
Introduction to Company
Sartorius Stedim is a biopharmaceutical equipment manufacturing company which provide
mechanical equipment’s controlled by automation software. The requirement of the system s
will vary based on customer needs, but the basic functionalities are similar. Company provide
standard software which will be modified with the customer requirement.

Case study of Project-ABC

Introduction of Interviewee

The interviewee is a software developer in sartorius for 5 years and has also worked in similar
companies. He has identified various problems found during the development and even after the
deployment.

Interview Execution
A questionnaire was designed to conduct the interview. The questionnaire was consisted of both
open-ended and closed-ended questions. Furthermore, the questions are validated by the author
for proper answers. For the complete questionnaire see Appendix 2.

The basic of the quality concept and essence of the research has shown to the interviewee to
understand the concept. This helped the interviewee to get the idea of the thesis. The interviewee
was provided sufficient time to answer the questions.

Interview Analysis
The motivation of interview was to implement six sigmas to improve the software quality.

Project Analysis - ABC

The initial proposal of the project starts with comparatively less requirement. All the design phase
is completed, and the project execution is started. Once after the software is developed there were
additional requirements from the customer which needed to implement during software testing.
This raised quality issues with the software. In addition to that, customer was kept on asking
changes in the process and project team agrees to the changes eve it is not correct. But all these
changes needed to revert to the previous stage once after actual process running fails. It’s a clear
case of not understanding the exact requirements from the customer.
Case study of Project-YBD
Introduction of Interviewee

The interviewee is a software Tester in sartorius for 3 years and has also worked in similar

40
companies. He has identified various problems found during the testing and even after the
deployment.

Interview Execution
A questionnaire was designed to conduct the interview. The questionnaire was consisted of both
open-ended and closed-ended questions. Furthermore, the questions are validated by the author
for proper answers. For the complete questionnaire see Appendix 2.

The basic of the quality concept and essence of the research has shown to the interviewee to
understand the concept. This helped the interviewee to get the idea of the thesis. The interviewee
was provided sufficient time to answer the questions.

Interview Analysis
The motivation of interview was to implement six sigma to improve the software quality by
analyzing Issues in software development.

Project Analysis - YBD

It is a project with multiple systems integrated together to a common server. The scope
of the project is high, and it will have communication with different systems to finish the
actual process. the design documents are created based on requirements and the project is
a duplication from the old one. But certain additional features add addict which is not
included in the design documents. this created confusion in software development and
doesn't meet the requirements from the customer. Also, this integration it's implemented
in a new software and components which is not so like the existing one. the number of
defects and bugs from this software development was high. this is due to the lack of
knowledge in the requirements as well as the software was not familiar with the
development team. This information has been collected from the software tester to
understand the root cause of the problem.
Case study of Project-TPL
Introduction of Interviewee

The interviewee is a software designer in sartorius for 7 years and has also worked in
process as well as a software developer. He has identified various problems found during
the testing and even after the deployment.

Interview Execution
A questionnaire was designed to conduct the interview. The questionnaire was consisted
41
of both open-ended and closed-ended questions. Furthermore, the questions are validated
by the author.

Project Analysis - TPL

The issues raised at this project is due to the change in requirements from the customer
team. the scope of the project was already defined, and the design phase is already
completed. But during the software testing the customers asked for changes in the system
which ultimately changes the in this structure of the program. it made the software
designer as well as the developer to recreate everything from the scratch and retest the
software. because of the short time duration, the quality of the software became so poor.so
this is a management failure to understand the exact requirements from customer and to
ensure with them that there are no additional changes after this scope of the project is
declared.
A) Define Phase
The first phase of Six sigma is define phase. This would clearly define the general goals,
requirements and scope of the project. This would get analyzed at the beginning of the project.
a) Identify the customer and the critical to quality requirement.
In this phase all the relevant requirement of the projects is identified. Also, all the possible
questions raised from the customer are prepared to solve at the initial phase.
1) What are the basic requirements of the system?
2) What are the basic features provided to the system?
3) What additional features customer can ask at the later stage?
4) What is the objective of this project from the customer end?
5) Ensure that any additional change in requirement would affect the project plan and
quality?
6) What are the main threats to the quality?
b) Critical to quality with the software
1) Security: the basic security features of the software. The rights of the users are clearly
defined and authorized at the software level. These are clearly defined at earliest stage of
the project.
2) Software reliability and maintainability: the ease of software will be understood and
modified. Software maintainability and the features of the software will be depicted here.

42
c) Create the project Charter

Figure 6.1 Project Charter

By implementing project Charter in projects. The scope of the projects is well defined, and the
milestones of the projects can be clearly identified. The start and end dates of the projects and the
other important dates and events regarding the project will be mentioned to clarify team members.

Process Maps
Process maps are implemented to identify the inputs and outputs pf the project. This would
clearly define the strength and weakness of existing process.
it’s a graphical representation with illustrative descriptions. This reduce the cycle time and defects
in the process and
enhance its
productivity.

Figure 6.2 Process Mapping

43
Process Flow

Figure 6.3 Process Flow

By implementing these techniques, the project team got a clear picture of the start and end date of
the projects and the challenges and decisions needed to take in the process. This reduces the waste
of the projects. Most of the technical discussion will be planned based on these conditions. This
shows the challenges in the project flow.

B) Measure Phase
The goal of this phase is to reduce the number mistakes from the design and development phase.
In order to reduce the errors, the requirements from the customer must be clearly defined.
Define the performance goals or standards
The performance goals and standards must be checked at this phase. The measure phase also
identifies the required time to analyses requirements and the impact of changes from the customer

44
side. In this phase it identifies the errors and bugs from various process from the software life
cycle. It identifies the bugs from the design and development phase. Also measure to find that
how the process result is deviated from the project objectives. It also measures that project
follows the same performance level.
Time Spent on Correcting defects
This phase clearly measures the time required to rectify the errors in the software. If the error
correction time is more it affects the productivity. The changes from the design phase is also
consider as error at this stage and required sufficient time to correct.
The lead Time for defects correction
The error occurring and the correction time is also a measure of performance If the lead time is
more then it affects the overall project performance and a big threat to the software quality.

Data collection: Collect information from the coordinator about the loss of opportunities due to
issues. Also collect the number of man hours lost to correct issues due to the software
development error or due to the wrong input from the design team.
It also collects the errors found after software testing. This is called a problem bank.
Each cycle of the software development must be measured to understand the common issues and
defects occurs.
Control Charts: Use of control charts to measure the process and its deviation. The number of
bugs and defects produced after the development will be measured in this way.

45
C) Analyze Phase
In this phase the root cause of the defects and problems will be analyzed.
Identify the source – with the help of cause and effect diagram the problems in the current process
were analyzed. The various problems of the development such as Design issues, no proper
resource allocation or training, new methods in the programming. These are problems need to be
identified and analyzed at this phase.

Refine Process capability

The data collected from the measure phase will be converted to several available standards of six
sigma measures of capability.
Refine Improvement goals
If the success rate of the project is 90 percentage but if it achieves 70 percent. So, the six-sigma
implementation must be little high to tighten the gap.
Identify significant data Segments /Pattern
Similar kind of defects from the software will be clubbed to find the root cause of the problems.
The route cause can be not properly allotted time, the lack of training for the software developer or
due to the constant changes from the design team.
Refine the financial benefit forecast
The financial benefits of the software projects will be forecasted and refined at this stage. The
number of defects and the number of man hours are increased then the financial benefit will be
reduced. Due to the excess defects and changes the number of man hours for each project will be

46
increased. This would make certain loss to the company and delay the resource allocation for other
projects.

D) Improve phases
In improve phase, the solutions of the problems will be identified and implemented. The root
cause of the defects such as late requirements and changes, context switching and multitasking,
overproduction and long wait times will be identified, and the solutions will be implemented.
1) Identify solution alternatives
a) Train all the responsible people for project planning on best practices. this will be
technical training, technical documentation and various diagnostics methods.
b) Assign mentors or coaches from the project office to review all the plans to bring
out the best practices.
c) Use the combination of these options.
2) Select /Refine the solution
Evaluate each solution with respect to the applicable effectiveness criteria. The cost of each
option, its effectiveness, lead time required implement. will be considered, analyzed and
implement.
1) reduce the number of changes in the design documents.
2) Train the software developers to understand the requirements from the design document.
3) Conduct discussions about to reduce the number of errors in software.
4) Conduct training sessions for new software and programming methods.
3) Pilot test or implement the solution
These solutions will be compared with the historical data of the issues and effects and unless that
any improvement is occurred due to the implementation of these solutions. They will conduct
meetings occasionally to implement various solutions on different problems.

F) Control Phase
the purpose of control phase is to make sure that the improvements are properly implemented and
make value to the organization. the improvement in the field of software design, software
development and software testing would be considered as an advantage off 6 Sigma in this cycle.

1) The control plan needs to be developed.

This will be creation of SOP or training sessions for relevant topics. Reduce the waste from
the SDLC cycle is very important.

47
 A) Use lean concept to identify the waste generation from the process. create an action
plan to reduce the bugs in the software generation.
B) Conduct training sessions for newly joined employees
C) Conduct regular meetings to identify the weak points in the development cycle.
D) Identify the strength and weakness of each employee and allot work based on their
capacity.
2) Determine improved process capability
Define the improvement of each cycle of the software generation. In the design phase it could
be find out all the requirements and document it to translates to the software codes.
In the development it is to reduce the number of man hours and reduce the defects in
development. By analyzing the
Software tester must implement all the possible criteria do identify the bucks from the
software. they can add or modify the existing criteria to make the software error free.

3) Implement process control

All the relevant changes in the process will be implemented and reduce the defects from
each phase of the software development
4) Close the projects
After implementing 6 Sigma the projects will get closed and transferred to the customer.

Findings
Define
By assigning the project goals and by understanding the requirement. Requirement changes
reduced drastically. No more process or design changes are identified unless any error occurs. The
company also define the common errors in the software and in design documents. These errors are
addressed and corrected.

SIPOC
SIPOC diagram is a high-level map of the process of an organization which shows its basic steps.
The SIPOC diagram is prepared to identify the supplier, input , process , output and customer.

48
 Figure 6.4. Sipoc Diagram

Measure
Data is collected to compare the changes in future. Based on the data analysis the quality of
process improved with a smaller number of errors. As per the measurement all the milestones of
the quality improvement are achieved. Process and product maturity are achieved, and the number
of reworks reduced.
Analysis
The number of defects decreased, and number of reworks also decreased. So, the cost of the
rework and additional man hours also decreased.
Cause and effect
Cause and effect diagram is prepared to analyze the quality issues in Software.

49
 Figure 6.5 Cause and Effect Diagram
Improvement
Common errors and bad practices are identified. All the team members are sufficiently trained to
understand the requirement and the software coding. Innovative ideas to reduce the defects are
promoted.

Action Description Owner Function Root Causes

1 Standardization of Design team Design Team Number of changes

requirement lead Management and error

2 Proper & on time Project manager Project Lack of proper

Client management communication
communication.

3 Finalization of Project manager Project Lack of proper

scope. management communication

4 Suitable talent for Team Leads Software Excess number of

particular projects For software developer team projects
developer

5 Test the software fix Software test Software testing Lack of experience,
to the timing feature team lead team Time issue, Urgent
on the planning delivery
system

50
 6 Change of process Project manager Software design Lack of experience
in actual team and training
Software design
team lead

Figure 6.6 Improvement Targets

Control
The number of defects is carefully monitored to analyze the reason behind the defects.
Development team conducts meetings to analyze the defects.
After implementing all these changes, the number of defects is decreased, and the cause of
errors are identified. The system itself has controlling over the defects which make the developer
and tester knows how the defects are formed and how it can be reduced. This is great achievement
at the initial stage of Six sigma implementation. Also, the six sigma methodologies are continually
implemented to identify the weak areas to strengthen them.

Pareto diagram
The diagram shows the reduction of defects after the implementation of Six sigma. The number
of defects reduced less than 50 errors. The changes are continuously monitoring and controlling.

Figure 6.7 Pareto diagram

51
CHAPTER SEVEN
FINDINGS, CONCLUSION AND SUGGESTIONS
7.1 Introduction
This chapter presents summary of findings, conclusion and recommendations of the
study in line with the objectives of the study.
7.2 Summary of the Study
This clearly define that 6 Sigma can be used to identify problems software development and good
to improve the overall practices in software project management. Make the project team to
identify do requirements or the problems and to measure the impact these requirements or the
changes. And analyze with the quality tools on the white scope of these issues. the improvement
in the overall process will be taken place. and the improvement is also monitored and controlled
by the team to achieve the maximum success.
7.3 Conclusion
The objective of this study is to understand the quality principles and its implementation in the
software project management to reduce the defects and improve the quality. the implementation of
6 Sigma shows how important if the quality of a product and how the existing system can be
improved with the help of this quality tools. this emphasis the improvement of overall process
quality by identifying the defects and issues from each process of the software development.
7.4 Suggestions
Agile Sigma-Software companies now days implemented Agile Sigma for complex projects.
This will have all the characteristics of Lean and Six sigma. It also changes the complete SDLC
cycle that a normal company follows. The project will be splited as Sprint and the requirements
will be constantly monitored and tested with software. If each section of the project is completed.
Then it will be tested and reviewed with the requirement. The software quality will be improved,
and the project team can submit project on time. These cycle repeats till the project is finished.

52
BIBLIOGRAPHY
1. J. A. Whittaker and J. M. Voas, "50 years of software: key principles for quality," IT
Professional, vol. 4, pp. 28-35, 2002.
2. Y. Park, H. Park, H. Choi, and J. Baik, "A Study on the Application of Six Sigma
Tools to PSP/TSP for Process Improvement," 5th IEEE/ACIS International
Conference on Computer and Information Science and 1st IEEE/ACIS International
Workshop on Component-Based Software Engineering, Software Architecture and
Reuse (ICIS-COMSAR'06), pp. 174-179, 2006.

3. M. Diaz and J. Sligo, "How Software Process Improvement Helped Motorola,"

Software, IEEE, vol. 14, pp. 75-81, 1997.

4. C. B. Tayntor, Six Sigma Software Development: CRC Press, 2002.

5. J. W. Creswell, Research Design: Qualitative, Quantitative, and Mixed Method

Approaches: Sage Publications Inc, 2003.

6. C. Redzic and J. Baik, "Six Sigma Approach in Software Quality Improvement," in

Fourth International Conference on Software Engineering Research, Management
and Applications 2006, pp. 396-406.

7. Z. Pan, H. Ryu, and J. Baik, "A Case Study: CRM Adoption Success Factor Analysis
and Six Sigma DMAIC Application," Software Engineering Research,Management
& Applications, 2007. SERA 2007. 5th ACIS International Conference,pp. 828-838,
2007.

8. M. Murugappan and G. Keeni, "Quality Improvement - the Six Sigma way," Quality
Software, Proceedings of First Asia-Pacific Conference, pp. 248-257 2000.

9. C. Wohlin and A. Wesslen, Experimentation in Software Engineering: An

Introduction: Springer, 2000.

10. B. Klefsjö and B. Bergman, Quality from Customer Needs to Customer Satisfaction:
Studentlitteratur, 2004.

11. W. A. Shewhart, Economic Control of Quality of Manufactured Product: ASQQuality

Press, 1980.

12. P. B. Crosby Quality Is Free: The Art of Making Quality Certain: Mentor Books, 1980.

13. W. E. Deming, Out of the Crisis: MIT Press, 1986.

14. C. A. Reeves and D. A. Bednar, "Defining Quality: Alternatives and Implications,"

The Academy of Management Review, vol. 19, pp. 419-445, 1994.

15. D. A. Garvin, "What does product quality really mean," Sloan Management Review,
vol. 26, pp. 25-43, 1984.

53
16. B. B. Flynna, R. G. Schroederb, and S. Sakakibarac, "A framework for quality
management research and an associated measurement instrument," Journal of
Operations Management, vol. 11, pp. 339-366, March 1994.

17. B. A. Spencer, "Models of Organization and Total Quality Management: A

Comparison and Critical Evaluation," The Academy of Management Review, vol. 19,
No. 3, pp. 446-471, July 1994.

18. B. Dale and H. Bunney, Total Quality Management Blueprint: Blackwell Publishers,
1999.

19. B. Kitchenham and S. L. Pfleeger, "Software quality: the elusive target [special issues
section]," Software, IEEE, vol. 13, pp. 12-21, 1996.

20. B. Barry, C. Sunita, V. June, and W. Bernard, "Fifth Workshop on Software Quality,"
in ICSE 2007 Companion 29th International Conference, 2007, pp. 131- 132.
21. F. Xing, P. Guo, and M. R. Lyu, "A novel method for early software qualityprediction
based on support vector machine," Software Reliability Engineering - 16th IEEE
International Symposium, p. 10, 2005.

22. K. Akingbehin, "A Quantitative Supplement to the Definition of Software Quality,"

in Software Engineering Research, Management and Applications - Third ACIS
International Conference, 2005, pp. 348-352.

23. IS0 9001 Quality Systems - Model for Quality Assurance in Design/Development,
Production, Installation, and Servicing: International Organization for
Standardization, 1994.

24. M. C. Paulk, B. Curtis, M. B. Chrissis, and C. V. Weber, "Capability maturity model,

version 1.1," Software, IEEE, vol. 10, pp. 18-27, 1993.

25. M. C. Paulk, "How ISO 9001 compares with the CMM," Software, IEEE, vol. 12, pp.
74-83, 1995.

26. W. R. Duncan, "PMBOK - A Guide to the Project Management Body of Knowledge,"

ZDA: Project Management Institute (PMI), 1996.

27. "ANSI/IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering

Terminology," IEEE Standard Office, 1991.
28. D. Jacobs, Accelerating Process Improvement Using Agile Techniques. New York:
Auerbach, 2006.
29. "Free Six Sigma Lessons," Motorola University, 2008.
http://www.motorola.com/content.jsp?globalObjectId=3069-5787.
30. "The History of Six Sigma," iSix Sigma LLC, 2008.
http://software.isixsigma.com/library/content/c020815a.asp.
31. "What is Six Sigma? ," Motorola University, 2008.
http://www.motorola.com/content.jsp?globalObjectId=3088.
32. "Normal distribution," Wikipedia, 2008.
http://en.wikipedia.org/wiki/Normal_distribution.

54
33. R. V. Binder, "Can a manufacturing quality model work for software?," IEEE
Software, vol. 14, pp. 101-102, 105, 1997.
34. R. E. Biehl, "Six Sigma for Software," Software, IEEE, vol. 21, pp. 68-70, 2004.
35. "Related Process Models - The Six Sigma Methodology," ITIL, ITSM & security
services, 2008. http://www.itil-itsm-world.com/sigma.htm.
36. G. Y. Hong and T. N. Goh, "Six Sigma in software quality," The TQM Magazine,
vol. 15, pp. 364-373, 2003.
37. "Six Sigma Table," Westgard QC, 2001. http://www.westgard.com/sixsigtable.html.
38. "The Six Sigma Calculators," Westgard QC, 2003.
http://www.westgard.com/SixSigCalc.htm.
39. A. C. Tonini, M. d. M. Spinola, and F. J. B. Laurindo, "Six Sigma and Software
Development Process: DMAIC Improvements," Technology Management for the
Global Future, PICMET 2006, vol. 6, pp. 2815-2823 2006.
40. Z. Pan, H. Park, J. Baik, and H. Choi, "A Six Sigma Framework for Software Process
Improvements and its Implementation," Proceedings of the 14th Asia- Pacific
Software Engineering Conference (APSEC'07), pp. 446-453, 2007.
41. "DMAIC Versus DMADV," iSixSigma LLC, 2008.
http://software.isixsigma.com/library/content/c001211a.asp.
42. "Six Sigma," Wikipedia, 2008. http://en.wikipedia.org/wiki/Six_Sigma.
43. L. Burge, M. Garuba, and C. Brent, "Improving retention of minority freshmen in
engineering by applying the six sigma methodology," The Proceedings ofInformation
Technology: Coding and Computing, 2004 (ITCC), vol. 1, pp. 723-728, 2004.
44. K. Ishikawa, Guide to Quality Control: Asian Productivity Organization Tokyo, 1976.
45. H. M. Wadsworth, K. S. Stephens, and A. B. Godfrey, Modern methods for quality
control and improvement: Wiley New York, 1986.
46. S. Mizuno, Management for Quality Improvement: The Seven New QC Tools:
Productivity Press, 1988.
47. K. Magnusson, D. Kroslid, and B. Bergman, Six Sigma - The Pragmatic Approach:
Studentlitteratur, 2000.

48. "Six Sigma Quality Tools and Templates," iSixSigma, 2008.

http://www.isixsigma.com/tt/.
49. "Cause and effect diagrams," HCi Library, 2008.
http://hci.com.au/hcisite5/library/materials/Cause%20and%20effect%20diagrams.ht
m.
50. T. Rickards and B. L. Freedman, "Procedures for managers in idea-deficient
situations: examination of brainstorming approaches," Journal of Management
Studies, vol. 15, pp. 43-55, 1978.
51. J. Baumgartner, "The Step by Step Guide to Brainstorming," Bwiti BVBA, 2008.

55
 http://www.jpb.com/creative/brainstorming.html.
52. J. Kawakita, "The Original KJ Method," Tokyo: Kawakita Research Institute, 1991.
53. K. Niles, "Characterizing the Measurement Process," iSixSigma, 2008.
http://www.isixsigma.com/library/content/c020527a.asp.
54. W. H. Woodall, "Controversies and contradictions in statistical process control,"
Journal of Quality Technology, vol. 32, pp. 341-50, 2000.
55. N. Kano, N. Seraku, F. Takahashi, and S. Tsuji, "Attractive quality and must-be
quality," The Journal of the Japanese Society for Quality Control, vol. 14, pp. 39-48,
1984.
56. T. Pyzdek and P. A. Keller, Quality Engineering Handbook: CRC Press, 2003.
57. J. Krupar, "Six Sigma for Sales: Truth About the Customers' Needs," iSixSigma,
2008. http://www.isixsigma.com/library/content/c040112a.asp.
58. P. Davis, "QFD-A Structured Approach to Understanding the Voice of the Customer,"
IEEE Applied Power Electronics Conference, vol. 1, pp. 245-251, 1995.
59. L. Westfall, "Software requirements engineering: What, why, who, when and how,"
SQP, 2005.
60. P. S. Pande, R. P. Neuman, and R. R. Cavanagh, The Six Sigma Way: How GE,
Motorola, and Other Top Companies are Honing Their Performance: McGraw-Hill,
2000.
61. M. J. Harry and R. Schroeder, Six sigma: the breakthrough management strategy
revolutionizing the world's top corporations: Currency, 2000.
62. F. W. Breyfogle, Implementing Six Sigma: Smarter Solutions Using Statistical
Methods: Wiley, 2003.
63. R. W. Hoerl, "Six Sigma and the Future of the Quality Profession," Quality progress,
vol. 31, pp. 35-42, 1998.
64. I. Sommerville and P. Sawyer, Requirements Engineering: A Good Practice Guide:
John Wiley & Sons, Inc. New York, NY, USA, 1997.
65. D. H. Stamatis, Six SIGMA Fundamentals: A Complete Guide to the System,
Methods and Tools: Productivity Press, 2003.
66. K. Melymuka, "GE's Quality Gamble," Computerworld, vol. 32, 1998.
67. J. Antony and C. Fergusson, "Six Sigma in the software industry: results from a pilot
study," Managerial Auditing Journal, vol. 19, pp. 1025-1032, 2004.
68. G. Tennant, Six SIGMA: SPC and TQM in Manufacturing and Services: Gower
Publishing, Ltd., 2001.
69. M. Murugappan and G. Keeni, "Blending CMM and Six Sigma to meet business
goals," IEEE Software, vol. 20, pp. 42-48, 2003.
70. R. Mahanti, "Six Sigma for software," Software Quality Professional, vol. 8, p. 1,
2005.

56
71. A. C. Gillies, Software Quality: Theory and Management: Chapman & Hall, Ltd.
London, UK, UK, 1992.
72. A. Bhatia, "Need for Six Sigma in the Age of Information Technology," 2008.
http://software.isixsigma.com/library/content/c070718b.asp.
73. W. S. Humphrey, Managing the software process: Addison-Wesley Longman
Publishing Co., Inc. Boston, MA, USA, 1989.
74. J. Barnes, "Half a century of programming and not much progress," Software Focus,
vol. 2, pp. 15-20, 2001.

75. N. Andrews, "Software bug cost millions at airline," New York Times, 1988.
76. SEM, "Company Profile," Samsung Electro-Mechanics, 2008.
http://www.sem.samsung.com/en/indexMain.jsp.
77. D. L. Hallowell, "Remove Obstacles for Six Sigma Within Agile Development,"
iSixSigma, 2008. http://software.isixsigma.com/library/content/c080409a.asp.
78. Y. Ahmed, "Using Six Sigma Tools in an Agile Softwarse Project," iSixSigma, 2008.
http://software.isixsigma.com/library/content/c060927b.asp.
79. D. L. Hallowell, "DFSS Meets Agile Development - Friend or Foe?," iSixSigma,2008.
http://www.isixsigma.com/library/content/c041124b.asp.
80. G. Gordon Schulmeyer, et al, The Handbook of Software Quality Assurance (Upper Saddle
River, NJ: Prentice Hall PTR, 1998), p. 9.
81. Ljubomir Lazić. Software Testing Methodology, YUINFO’96, Brezovica, Serbia&Montenegro,
1996. [82] Ljubomir Lazić, D. Velasević. Integrated and optimized software testing process
based on modeling, simulation and design of experiment”, 8th JISA Conference, Herceg Novi,
Serbia&Montenegro, June 9-13, 2003.
82. Ljubomir Lazić, D. Velasević, N. Mastorakis. A framework of integrated and optimized
software testing process, WSEAS TRANSACTIONS on COMPUTERS, Issue 1, Volume 2,
January 2003.
83. Ljubomir Lazić, D. Velasević. Applying simulation to the embedded software testing process,
Software Testing, Verification & Reliability, Wiley, 2003, submitted for publishing.
84. [ Ljubomir Lazić, M. Medan. SOFTWARE QUALITY ENGINEERING versus SOFTWARE
TESTING PROCESS, TELFOR 2003, 23-26 November, Beograd
85. Ljubomir Lazić, D. Velasević, N. Mastorakis. The Oracles-Based Software Testing: problems
and solutions, WSEAS Multiconference program, Salzburg, Austria, February 13-15, 3rd
WSEAS Int.Conf. on SOFTWARE ENGINEERING, PARALLEL & DISTRIBUTED
SYSTEMS (SEPADS 2004), 2004.
86. Kai-Yuan Cai. Optimal software testing and adaptive software testing in the context of
software cybernetics, Information and Software Technology, 2002; 44:841-855.

57
87. H. Ziv and D.J. Richardson, Constructing Bayesian-network Models of Software Testing and
Maintenance Uncertainties, International Conference on Software Maintenance, Bari, Italy,
September 1997.
88. GE's DMAIC Approach, http://www.ge.com/capital/vendor/dmaic.htm, URLs cited were
accurate as of April 2002.
89. K. H. Moeuller and D. J. Paulish, "Software Metrics: A Practitioner’s Guide to Improved
Product Development, Chapman & Hall, 1992.
90. R. B. Grady, D. L. Caswell, "Software Metrics: Establishing a Company-wide Program",
Prentice Hall , 1987, ISBN 0-13-821844-7.
91. V. R. Basili, G. Caldiera, H. D. Rombach, ‘The Goal Question Metric Approach’,
Encyclopedia of
92. Software Engineering, volume 1, John Wiley & Sons, 1994, pp. 528-532
93. M. C. Paulk, C. V. Weber, B. Curtis, M. B. Chrissis, "The Capability Maturity Model:
Guidelines for Improving the Software Process", Addison-Wesley Publishing Company,
1995, ISBN 0-201-54664-7.
94. David L. Hallowell, Six Sigma Evolution for Software Systems, http://www.6siga.com, URLs
cited were accurate as of April 2003.
95. Mark C. Paulk, Dennis Goldenson, and David M. White:”The 1999 Survey of High Maturity
Organisations”, Tech. Rep. CMU/SEI-2000-SR-002, Software Engineering Institute, Feb.
2000.
96. Lionel C. Briand, Bernd Freimut, Oliver Laitenberger, Guenther Ruhe, and Brigitte Klein:
“Quality Assurance Technologies for the EURO Conversion – Industrial Experience at
Allianz Life Assurance”, in Proceedings of the 2nd International Software Quality Week
Europe, 1998.
97. Thomas J. Ostrand and Elaine J. Weyuker:” Collecting and Categorizing Software Error
Data in an Industrial Environment”, Journal of Systems and Software, vol. 4, pp. 289--300,
1984.
98. Barbara Hirsh, Robert Bleck, and Steven Wood:” A Comprehensive Defect Prevention
Program Using the ODC Methodology”, in Proceedings of the 10th International Symposium
on Software Reliability Engineering (Fast Abstracts and Industrial Practices), pp. 61--81,
1999.
99. Institute of Electrical and Electronics Engineers, IEEE Standard Classification for Software
Anomalies, IEEE Std. 1044-1993, 1994.
100. Ram Chillarege, Inderpal S. Bhandari, Jarir K. Chaar, Michael J. Halliday, DianeS. Moebus,
Bonnie K. Ray, and Man-Yuen Wong: “Orthogonal Defect Classification -- A concept for in-
process measurements”, IEEE Transactions on Software Engineering, vol. 18, pp. 943--956,
Nov. 1992.

58
101. Marek Leszak, Dewayne E. Perry, and Dieter Stoll: “A case study in root cause defect
analysis”, in Proceedings of the 22nd International Conference on Software Engineering, pp.
428-437, 2000.
102. Pfleeger, S. Lawrence: “Software Engineering: Theory and Practice”,NJ Prentice-Hall, 1998
103. Mays,R. at all : “ Experiences with Defect Prevention”, IBM Systems Journal, 29(1), January
(4-32),1990.
104. www.bds.com, URLs cited were accurate as of February 2004.

59
APPENDIX 1. INTERVIEW QUESTIONS WITH Automation
Department

Interviewee Introduction

1. What is your name?

2. Which department u were working while implementing new practices?
3. What i s y o u r roles and responsibilities?
4. What is your educational background?
5. What are the common quality issues are you facing?
6. What kind of issues did you experience?

The interview questions are related to Six Sigma and the focus in each question
is specific for Software Companies.
Organization structure:

7. Does software companies can adopt six sigma?

8. How the process structure will be altered by six sigma?
9. Is there any Six Sigma training? How is it?
10. How six sigma can adapt with the cross functional team?

Six Sigma Daily Works DMAIC Phases:

11. Tell me how you identify the problems specific to software which need to be
improved?

12. Who will be involved when deal with a specific problem? How to distribute roles
and responsibilities?

13. Tell me how you measure the problem conditions? (Measure phase)

14. Tell me how you analyze and plan to solve the problem specific to software?

15. Which tools are frequently used specific for software’s? Which Six Sigma tool you
are using? Why choose them?

60
16. How to estimate change in cost? Which factors will influence the decision?

17. Tell me how you implement the plan? Is there critical issues?

18. How to implement the six sigma methodologies in management?

19. H ow to analyze the results?

20. how to manage and store Six Sigma software data?

21. How to measure the improvement in systems after six sigma?

22. What are the hurdles of six sigma in software companies?

61
62
63