Quality Issues in IT Industry Pak Gp_Presentation FINAL Aatif 17 APR 12

7/29/2019 Quality Issues in IT Industry Pak Gp_Presentation FINAL Aatif 17 APR 12

http://slidepdf.com/reader/full/quality-issues-in-it-industry-pak-gppresentation-final-aatif-17-apr-12 1/32



GroupFa-2011/M. Sc. EM/018 Muhammad Aatif Saif Khan

Fa-2011/M.Sc. EM/053 Muhammad Bakhsh Sial

Sp-2012/M. Sc. EM/001 Mudassar Ali Fayyaz

QUALITY ISSUES INIT

INDUSTRY OF PAKISTAN



INTRODUCTION

Pakistan’s IT industry’s tremendous promise ismarred by plethora of issues including but notlimited to product, process and quality at thecore level and soft issues like employeesatisfaction and management competence

concerns. According to PSEB, out of approximately 1500

registered companies, only 110 ISO 9001, 23 CMMI and 11 ISO 27001 certified companies

It demands faculties to evaluating key areas thatneed continuous and continual improvements forreducing losses incurred due to poorrequirements capturing, reactive approach to theinherent risks in project management, poorcoding quality directly impacting the employee



SCHEME OF PRESENTATION

• Introduction

• Factors considered

• Data analysis

• Deductions fromFindings

• Conclusion

Muhammad

Aatif Saif Khan

Mudassar AliFayyaz

Col.MuhammadBakhsh Sial



FACTORS

• Processes• Software Development methodologies

• Requirements Gathering

• TQM in Software Development

• Employee Satisfaction

• Role of Management



PROCESSES

• Recipe for quality software resides in thematurity of processes & embracingstandards at organizational level

• Well defined and truly implementedprocesses result in conformance tospecifications & customer satisfaction

• On the contrary, poorly defined

processes, non-existence of QMS,management oversight and lack of business acumen lead to utter disaster interms of reputation & business



SOFTWARE DEVELOPMENTMETHODOLOGIES

• Software industry has gone throughmeteoric changes and many models of software development life cycle (SDLC)

have emerged in last three decades.• Few prefer adopting classical waterfall

model but more aggressive organisationshave moved towards agile developmentcycle (employing self-organizing, cross-functional teams).



SOFTWARE DEVELOPMENTMETHODOLOGIES



REQUIREMENTS GATHERING

Fundamental objective is listening to “Voiceof the Customer” and translating them into

“Voice of the Engineer emanating intoconformance to customer requirements”

It shall happen through qualified business

analysts (BAs) having sound domainknowledge under a “Functional Lead” & inclose consultation with Technical Lead

Unfortunately, in Pakistan, companies try to

save on resource cost by employingsoftware developers for requirementsgathering. It results into half-backed andpartially captured requirements sincetechnical resources seldom correctly



TQM IN SOFTWARE DEVELOPMENTMcCall, Richards, and Walters were the first to

study the concept of software quality in termsof quality factors and quality criteria.

Software firms pay less attention to qualityassurance as it is frequently the first area that

is cut back when deadlines are missed (Miller,2007).

TQM concept represents a fundamental changein the definition and treatment of quality inproduct development. It has redefined thequality as “Everyone’s Business”

Software companies planning to implement

TQM must have critical mass of employees



EMPLOYEE SATISFACTION

Employee satisfaction is often linked tocareer advancement opportunities,challenging nature of work, salary &

other employee benefits, positive workenvironment, flexibility in workschedule / telecommuting, training /educational opportunities and many

more factors.Due to lack of measures at government

level, IT industry has shrunk in last fewyears resulting into cut-downs inemployee salaries



ROLE OF MANAGEMENT

• Management has a principal role in ensuringtime, cost, scope and quality of software,through well-defined processes, team work,and empowerment during the software

development life cycle.• Project management decisions are often

tricky precisely because they involve

tradeoffs based on fuzzy or incompleteknowledge. Furthermore, bad projectmanagement decisions, such as hiring toofew programmers or picking the wrong type

of contract can put an organization in poor”



DATA ANALYSIS



RESEARCH METHODOLOGY

• Software houses in Islamabad were

approached based on convenient samplingtechnique for seeking their inputs.

• Quantitative analysis would be perform inorder to measure the quality issues of IT

industry of Pakistan.

• We could gathering information related to:

• Issues in software quality practices.

• Employee satisfaction effects onsoftware quality.

• Role of Project management on software

quality.



QUESTIONERS

• Questioners included likert scale questions,

ordinal scale and simple Boolean questions• Questions include mostly structured

questions from past research papers and

software metrics, measurement relatedbooks whose references are given at the endof paper

• Metrics and Models in Software Quality

Engineering, 2nd (2002)

• Effectiveness and relevance of softwaredocumentation by Andrew Forward,

University of Ottawa.



SAMPLE DESCRIPTION• 24 organizations agreed to provide access to their

employees. Out of 250 sources requested for filling

survey questionnaire, 100 individuals with varyingservice experience and qualification providedfeedback

• Organizations included small, medium as well as largeIT companies.

• Position of the candidate also varied• From juniors developers with one year experience,

to senior developers more than one yearexperience,

• Project managers,

• Program Manager,

• Software Testing Analyst ,Software QualityAssurance Engineer

• CEOs.

• IT support



SOFTWARE QUALITY PROCESSES

Importance of difference

requirement frequency

Separate department

for software quality

Software Methodologies

frequencies stacked bar chart

Mean Median Mode

Spiral 1.86 1 1

Increment

al

2.13 1 1

RollingWave

2.14 1 1

Waterfall 2.35 1 1

Agile 2.09 1 1

None 2.03 1 1

Legion

1Never

2To someextent

3Not sure4Mostly

5Always



CONTINUEDLegion

1Never

2To some extent

3Not sure

4Mostly

5Always

Frequency of extent to which different best practices are followed in software

development Practices N Mean Median Mode Std.Deviati

on

VarianceValid Missing

Use source control (ie. CVS system) 89 44.11236

5 51.510856

2.282686

Have daily builds 91 22.41573

2 11.608281

2.586568

Maintain a bug database 93 03.4606

74

4 51.6100

27

2.5921

86

Follow any coding standards 88 52.764045

2 11.69908

2.886874

Fix bugs before writing new code 89 42.988764

3 51.627145

2.6476

Keep an up-to-date schedule 92 13.202247

4 41.58243

2.504086

Reviews at appropriate intervals bymanagement

85 8 2 1 11.339946

1.795455

Have a specifications document for your project 91 22.910112

3 11.655847

2.741828

Have new candidates for the developmentteam write code

89 42.640449

2 11.590077

2.528345

Develop test strategy 93 02.966292

3 11.598646

2.555669

Follow the test strategy 90 32.8764

04

3 51.6154

1

2.6095

51

Perform extensive test which includes unit 89 42.41573

2 11.615331

2.609295



PROJECT MANAGEMENT

Manager with

managementrelated education



CONTINUED

Frequencies of importance of project management practices



CONTINUED

Valid MissingMean Median Mode Std.Deviation

Stability of software over new feature fromclient

38 3 2.0526 2.0000 3.00.89887

Importance of process over ad hoc method of development to meet demand

40 2 3.0000 3.0000 3.001.48870

Separate testers over same employeeperforming testing and development

39 2 2.2105 1.0000 1.001.61342

Special training session over developer self-

learning

34 7 3.1176 3.0000 5.001.9031

8

Importance of having experience developer overfresh graduates or less experiences

38 3 2.4737 2.5000 1.001.53758

Commitment towards quality vs. time 37 4 2.5789 3.0000 1.001.5876

5

Frequency of different cases being rated by the managers



EMPLOYEE SATISFACTION

Why employee

chose to stay with

current employers

Employee ratingdifferent aspect

about current

job



DEDUCTIONS FROM

ANALYSIS



LACK OF DIVERSITY

• Male : Female ratio indicates lesserpreference for women folk due tocultural issues

• Male are considered for employment

because of their flexibility for travellingand late sitting option.



LACK OF TRAININGS

• Training of any sort is lacking

• Employees have to learn themselvesmostly

• Large software houses are more likely to

provide trainings to their employees

• Sense of complacency results in lack of touch with emerging trends and

knowledge domains

QUALITY IS NOT GIVEN ITS DUE



QUALITY IS NOT GIVEN ITS DUE

PLACE

• No organisation in totality has graspedthe concept of TQM or QA.

• The near absence of quality in softwaredevelopment results in faulty product

• Tight financial position leading to use of developers as quality control staff

• Lack of realization on part of management

ABSENCE OF RIGHT MAN FOR THE



ABSENCE OF RIGHT MAN FOR THERIGHT JOB

• Software developers are additionallyemployed in the roles of businessanalysts and QA staff.

• Not hiring and employing the qualifiedand experienced staff ultimately resultsin budgetary overshoot, lost time leadingto failed projects

• Large organizations are more likely toaddress this aspect than smallorganizations

WORK ENVIRONMENT & RESOURCE



WORK ENVIRONMENT & RESOURCEACCESS

• Employees satisfaction about resourcesavailable is attributed to:-

• Flexibility in work schedule

• Desk based needs - an IT person onlyneeds a machine, internet and loads of work



SALARY ISSUES

• Dissatisfaction of employees in small –

medium software houses is linked tosalary structures and delayed salariespayments.

• However, in companies with biggerportfolio and running concerns, theemployees were found satisfied aboutpay structure and timely disbursal.

• Employees also notified that they are notcompensated often for their extra workin terms of overtime.



Q & A

"The best way to have agood idea is to have lots

of ideas.“

(Linus Pauling)



WHY SOFTWARE ENGINEERING ?

The problem is complexity Many sources, but size is key:

UNIX contains 4 million lines of

codeWindows 2000 contains 108 lines

of code

Software engineering is aboutmanaging this complexity.



CONCLUSION

Pakistan’s IT industry has to make theirgrounds through focused and continual efforts

for improving quality throughout life of a

software development life cycle. The culture of total quality management would help inreducing costs, improving quality of the

product leading to customer satisfaction, thus

increased returns on investment.

Date post:	04-Apr-2018
Category:	Documents
Upload:	aatifsaif80
View:	215 times
Download:	0 times

Quality Issues in IT Industry Pak Gp_Presentation FINAL Aatif 17 APR 12

Documents