14
CASE STUDY Software Industry Information & Technology Six Sigma DMAIC Project Presentation GB Name : Mr A with Mr B, C and D GB Project Title : Reduction in Project Delays. Domain : Information Technology Organization : ABC Soft

Case Study 3 Software Industry IT Six Sigma Project

Embed Size (px)

Citation preview

Page 1: Case Study 3 Software Industry IT Six Sigma Project

CASE STUDY

Software IndustryInformation & Technology

Six Sigma DMAIC Project Presentation

GB Name : Mr A with Mr B, C and DGB Project Title : Reduction in Project Delays.Domain : Information TechnologyOrganization : ABC Soft

Page 2: Case Study 3 Software Industry IT Six Sigma Project

Project No.:

Date:

Date:

Green Belt :Sponsor:Process Owner:Six Sigma Leader:Black Belt:

Team Members/Support Resources:Resource Plan:

Problem Statement

Goal Statement

Scope

Customer CTQ’s

Functional Manager/Process Owner

Black/Green Belt:

Sponsor:

Six Sigma Leader

Project Name:

Validation

Text

Text

TextText

Estimate Financial Opportunities

Text

High Level Project Milestone

Text

Date:

Date:

Date:

Date:

Financial Analyst::

Other:

DMAIC Project CharterText

ABC Soft is facing many angry customers for the past 6 months. More than 40% of their projects are delayed.

to reduce the schedule variance from 40% to less than 10%.

This will save the company an estimated USD 500,000 every year.

In scope:All the projects received from US in the Pune office.

Out scope: everything other than the above.

Mr A, B, C and DResources: Internet ,

schedule variance

Define:18th june.Measure:29th june.Analyse:9th july.Improve:24th july.Control:14th august.

Page 3: Case Study 3 Software Industry IT Six Sigma Project

NotesMake any notes here:

.

Tip: First start with Outputs and Customers. Next set process boundaries and do the process map steps and then list inputs and suppliers

Start

End

Design and development

Coding

Testing

Analysing the requirements

Promotion

Maintenance and updating

SIPOCINPUTSSUPPLIERS PROCESS OUTPUTS CUSTOMERS

Critical to Client MetricCritical to Client MetricRegion : Product :Number of processes : Process : FTE :

1. Org 12. Org 23. Org 3

4. Org 4.

*Interviews with the clients,Mails and Supporting

docs by the client.•Requirement Specification.• The software

with forms and the requirement specification.

•The software, Requirement specifications,

supporting documents and

Technical documents.

•Software with content,Client

mails mentioning the competitors.

•Software/application,

content/functions to be updated,

re-Analysis reports.

Completed softwares

1. Org 52. Org 63. Org 7.

Page 4: Case Study 3 Software Industry IT Six Sigma Project

Process Name:

Who

Step

Elapsed Time

As-Is Process Map

Analysing the requirements

1st week 2nd week 3rd week 4th week 5th week 6th week 7th week

1

2 Design and development

3 Coding

4 Testing

5 Promotion

6 Maintenance and updating

Page 5: Case Study 3 Software Industry IT Six Sigma Project

Effect

Measurement

Methods

People

unable employee Untrained employee

Lack of training

Inefficient trainer

Mistakes in

estimating

Severity problems

Narrative data

Problem in the method of data

analysis

The method is not suitable with the data category

The method is not working with the system perfectly

Lack of knowledge about the

system

Lack of knowledge about the method

Page 6: Case Study 3 Software Industry IT Six Sigma Project

Moments of Truth (MOT):Any time a customer draws a critical judgement, positive or negative, about the service, based upon a service experience (or lack of it).Value-Added (VA):• Is the customer willing to pay for it?• Is it done right the first time?• Essential work that moves one step closer to the

final product.Value-Add Enabler: step that is required to do VA

Non-Value Add (NVA):Steps considered non-essential to produce and deliver the product or service to meet the customer’s requirements. The customer is NOT willing to pay for the step.

“As-Is” Process Map Analysis1 2 3 5 6 74

%TotalTotal

%Steps

Process Step

Discussing with the customer about the require-ments

Complete analysis

Specification building

Designing

Developing

Understanding the design(by programmer)

Writing the Codes (by technical writer)

Page 7: Case Study 3 Software Industry IT Six Sigma Project

Moments of Truth (MOT):Any time a customer draws a critical judgement, positive or negative, about the service, based upon a service experience (or lack of it).Value-Added (VA):• Is the customer willing to pay for it?• Is it done right the first time?• Essential work that moves one step closer to the

final product.Value-Add Enabler: step that is required to do VA

Non-Value Add (NVA):Steps considered non-essential to produce and deliver the product or service to meet the customer’s requirements. The customer is NOT willing to pay for the step.

“As-Is” Process Map Analysis8 9 10 12 1

314 1511

%TotalTotal

%Steps

Process Step Intensive testing

Complete testing Making

an advertising campaign

Making an Attractive website as to show models of software

Providing maintenance

Frequent updating

Reanalysis reports

Refreshing the website with the new updates

Page 8: Case Study 3 Software Industry IT Six Sigma Project

Moments of Truth (MOT):Any time a customer draws a critical judgement, positive or negative, about the service, based upon a service experience (or lack of it).Value-Added (VA):• Is the customer willing to pay for it?• Is it done right the first time?• Essential work that moves one step closer to the final product.Value-Add Enabler: step that is required to do VA

Non-Value Add (NVA):Steps considered non-essential to produce and deliver the product or service to meet the customer’s requirements. The customer is NOT willing to pay for the step.

Avg. Time (Mins)

Value-Added

Nonvalue-Added

– Failure Int. / Ext.

– Control/Inspection

– Delay

– Prep/Set-Up

– Move

Total

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Total%Total

%Steps

Page 9: Case Study 3 Software Industry IT Six Sigma Project
Page 10: Case Study 3 Software Industry IT Six Sigma Project

ROOT CAUSE ANALYSIS Estimation method not used. No training provided for Estimations.

QUANTIFYING THE GAP/OPPORTUNITY The opportunity that the problem is going to happen (92) because of Estimation method is not used. The opportunity that the problem is going to happen (74) because there is No training provided for Estimations.

Analyze Tollgate Review

Page 11: Case Study 3 Software Industry IT Six Sigma Project

Criteria are the requirements that you want your solution to meet. Some criteria are “must” criteria. Any solution that does not meet even one of the “must” criteria must be eliminated

Conclusions:

Solution Selection Matrix Select among Possible Using Objective Criteria

Criteria Weight Solution A Solution B Solution C

ScoreWeighted

ScoreScore

Weighted Score

ScoreWeighted

Score1 Cheap solution 2 3 6 2 4 5 102 Quick to impliment 4 7 28 6 24 7 283 High impact on CTQs 9 8 72 5 45 6 544 Complaint 8 6 48 6 48 8 645 0 0 06 0 0 0

TOTAL 154 121 156

Where weight and scores on following scale : High = 9, Medium = 3 and Low = 1.

• Solution A = Estimation methods should be tested and calibrated to our organization using our own past projects and determining the methods’ accuracy level. • Solution B = Provide training as well as Motivate and educate our estimators about how important is the training for estimations.• Solution C = Accuracy is correlated with training and the ability to see results, not development experience.

Page 12: Case Study 3 Software Industry IT Six Sigma Project

The methods are primarily based on data from past projects. Researchers studied project data and determined equations and formulas that best matched the existing data points. Some of the formulas are extremely simple, others are complex. None are totally accurate with all of the past projects, nor should you expect them to be with their predictions for future projects. Instead, they predict, based on their formulas (which are primarily based upon their data set), Estimators estimate the same project using the different estimation methods and models. Their results vary widely, depending on their definition of the project, their assumptions, and the models used. Finally we should use three things :-• Expert opinion with analogy .• Algorithmic models .• expert opinions by experts with different project experiences and responsibilities .

The methods are primarily based on data from past projects. Researchers studied project data and determined equations and formulas that best matched the existing data points. Some of the formulas are extremely simple, others are complex. None are totally accurate with all of the past projects, nor should you expect them to be with their predictions for future projects. Instead, they predict, based on their formulas (which are primarily based upon their data set), Estimators estimate the same project using the different estimation methods and models. Their results vary widely, depending on their definition of the project, their assumptions, and the models used. Finally we should use three things :-• Expert opinion with analogy .• Algorithmic models .• expert opinions by experts with different project experiences and responsibilities .

Page 13: Case Study 3 Software Industry IT Six Sigma Project
Page 14: Case Study 3 Software Industry IT Six Sigma Project

Improving your estimation skills, processes, and how you communicate your estimations will help you avoid the difficulties inherent in estimation; however, your ability to estimate well will always be limited by the extent of your projects‘ uncertainty.