7/31/2019 CI-Assignment

1/5

Competitive IntelligenceePGP-03

Assignment 2

(Problem Definition Methods)

Submitted to

Prof. Mahesh Narayan, IIMK

Prepared by:

Alok Sinha (Roll No :ePGP-03-095)

Parag Vaishnava (Roll No :eMEP-10-052)

Nitin Jaiswal (Roll No: ePGP-03-139)

Sajan Liyon (Roll No :ePGP-03-156)

Sajesh Jyothiprakash (Roll No :ePGP-03-157)

Sharon Selvaraj (Roll No: ePGP-03-167)

7/31/2019 CI-Assignment

2/5

7/31/2019 CI-Assignment

3/5

Competitive IntelligenceePGP-03

Is code review done?

Are the binaries tested individually?

Is the technology used alright?

Root Cause Analysis

We discussed with client as to what they are expecting and then we discussed with various internal

stakeholder using the 5 whys method and the below fishbone came out which depicts the cause of poor

software quality-

7/31/2019 CI-Assignment

4/5

Competitive IntelligenceePGP-03

MECE

After dividing the problem into sub-components we arrived at MECE-

Which when translated in text is as below-

Poor Quality of Software

Why is quality poor? Is management responsible?

Bureaucratic Organization

No tech manager

No ownership

Developers Skills?

Poor communication

Not trained in technology?

Methodology faulty?

What methodology used?

Code review/Unit test not done?

Lack of phase gates?

Machine config. Diff?

Prod env. different?

7/31/2019 CI-Assignment

5/5

Competitive IntelligenceePGP-03

How to improve quality?

Follow Agile?

Is agile the best?

Hire/train developers

Lateral Hires

Training

Better Monitoring?

Hire better managers?

Fail Safing mechanism?

Build Check Lists

Automate tests

SIX THINKING HATS

1. WHITE HAT: we have already gathered facts about the problem in terms of MECE and RCA.

2. YELLOW HAT: Only positive outcome each of the actions we are going to take should take us

one step ahead in the serious business of quality software deliverable.

3. BLACK HAT: Negative outcome if the loss of customer if we dont amend our track record and

loss of revenues.

4. RED HAT: Understand that quality is a big concern and any perception in customers mind aboutpoor quality can have only negative outcomes.

5. GREEN HAT: Think this as an opportunity to improve our processes, build quality check inplace. We should be happy that we have customer who is willing to listen to us and ready to give

us a second chance.

6. BLUE HAT: We need to act fast to set right what has been done wrong, quality improvement is

something which cant be improved overnight, however in short run we can have right set ofpeople with right attitude to engage with customer and try to convince them that poor quality is

thing of past and they will very soon witness a sea change in our deliverables. For long term we

need to act on facts and try to take one step at a time.