suresh- final viva07122010

7/29/2019 Suresh- Final Viva07122010

1/31

SERVICE QUALITY OF HEALTH

CARE DELIVERY OF PUBLICSECTOR HOSPITALS IN SRILANKA A Case Study Based on

Western Province of Sri Lanka

Presenter-: Gunasekara G.S.P.(MBA/MOT/9015)

Supervisor-: Prof: S.W.S.B. Dasanayake

2/14/2013 1


2/31

Agenda Introduction Problem StatementAim of the Research Research Objectives

Literature Review Research Methodology & Data Collection Situational Analysis

Data Analysis Conclusion Recommendations Suggested Future Studies Limitations 2/14/2013 2


3/31

Introduction

Public Health Sector is serving the Nation as the majorcontributor

Most of the developed countries are looking for

developing educated countries to outsource softwaredevelopment.

This study is based on special interest of those who are

involved in software development with Agilemethodology SCRUM.

2/14/2013 3


4/31

2/14/2013 4

The Software Exporters Association (SEA) hastargeted to achieve total exports of US$ 1.0 billion in2012 and their growth plan is as follows.

Source-: Software Exporters Association (SEA)


5/31

Significance of the study

Software development firms are now moving totraditional development methods to agile SCRUMdevelopment methodology.

Most of the software companies are now applyingsoftware quality with SCRUM, thus timely relevant.

The cost of software production is a main factor ofmarket competition since project performance isimportant.

This study will help to identify interrelationship amongquality factors and project performance in agile SCRUM

environment.

2/14/2013 5


6/31

Research Problem

The way of software quality factors and SCRUMsoftware development performance are co-aligned eachother the manner these quality factors affects projectperformance is the main research problem beinginvestigated through this study.

2/14/2013 6


7/31

Research Objectives To identify different quality factors applied for SCRUM

projects.

To test the derived conceptual framework for validityand reliability.

To analyze the relationship between software qualityfactors and SCRUM software project performance in thederived framework.

To identify and recommend strategies which ensuringsoftware quality in SCRUM projects, that will alsoimprove project performance.

2/14/2013 7


8/31

Literature Review

The quality of software is estimated by many of itsattributes such as reliability, integrity, maintainability,enhanceability (extensibility), usability, portability, andreusability. These are referred to as the ilities of

software (Yang, 2001).

Crosby (1979) is a clear on conformance tospecification quality definition adherer.

Deming (1988) strongest point was quality must bedefined in terms of customer satisfaction which is a

much wider concept than the conformance tospecification definition of quality.

2/14/2013 8


9/31

Literature Review Cont

Dromey (1995) is focused on the relationship betweenthe quality attributes and the sub-attributes, as well asattempting to connect software product properties withsoftware quality attributes.

Feigenbaum (1983) essentially points out that quality

must be defined in terms of customer satisfaction, thatquality is multidimensional.

Ishikawa (1985) mentions that quality is a dynamicconcept as the needs, the requirements and the

expectations of a customer continuously change.

2/14/2013 9


10/31


The first references in the literature to the term 'Scrum'point to the article of Takeuchi and Nonaka (1986) inwhich an adaptive, quick, self-organizing productdevelopment process originating from Japan ispresented (Schwaber and Beedle 2002).

Project performance measures Project effort,Productivity, Project duration, Schedule predictability,Requirements completion ratio, and Post-release defectdensity in the software development context (Kasunic,

1998).

2/14/2013 10


11/31


2/14/2013 11

ISO 9126 proposes a standard which species six areas of importance, i.e. quality factors


12/31

Research Methodology Research framework which includes conceptual

model and statement of hypothesis. Operationalization of variables

Construction of questionnaire

Data collection

Descriptive analysis

Statistical analysis

2/14/2013 12


13/31

Conceptual Model

2/14/2013 13


14/31

Hypothesis

H1: There is a significant positive relationship between

degree ofFunctionality and the project performance.

H2: There is a significant positive relationship betweendegree ofReliability and the project performance.

H3: There is a significant positive relationship betweendegree ofUsability and the project performance.

H4: There is a significant positive relationship betweendegree ofEfficiency and the project performance.

H5: There is a significant positive relationship betweendegree ofMaintainability and the project performance.

H6: There is a significant positive relationship between

degree ofPortability and the project performance.2/14/2013 14


15/31

Sample & Data Collection Sri Lanka Association of Software Industry (SLASI), Sri

Lanka Association of Software, and Service Companies(SLASSCOM) there are approximately 65 offshoreservice providers.

This study includes 19 SCRUM practicing companies

which will cover entire SCRUM practicing population forthis study.

Random selection of 3 SCRUM projects from eachorganization.

The questionnaire was distributed to a sample consistedof 3 large-scale companies, 4 medium scale companiesand 12 small-scale companies.

2/14/2013 15


16/31

Data Analysis

Data analysis process of this research includingdescriptive analysis of observed data, checking validityand reliability of constructs, and finally statisticalanalysis to test the research hypothesis.

2/14/2013 16


17/31

Descriptive Findings

Majority of the respondents were males (88%).

Majority of respondents belongs to age between 25 to35 years.

The education levels of respondents were represents

79% of Degree holders and 21% Postgraduate Degreeholders.

Experience level of the respondents consist majority of(75%) having total experience between 5 to 10 years inthe industry while only 11% has 10 to 15 years ofexperience and only 3% having more than 15 years ofexperience.

SCRUM software projects vary from 3 weeks to 2 yearsduration projects.

2/14/2013 17


18/31

Descriptive Findings Cont...

Most of the respondents were Project Managers,Technical Leads and QA Managers.

Most of offshore project in the sample has beenoriginated at USA (42%), Sweden 11%, Australia 9%and UAE, UK, Norway approximately have equal stakein the market.

Most of companies deal with web based (74%)development projects with SCRUM methodology.

Minimum team size of the project has been 3 and themaximum team size has been 84.

Most of the SCRUM teams were consists 5 or 6members per team.

2/14/2013 18


19/31

Descriptive Findings Cont...

Average duration of the SCRUM development project isapproximately 6 months.

Sample consists of SCRUM software projects from 2sprints to 24 sprints.

The average sprints of the SCRUM development projectwas 5.

2/14/2013 19


20/31

Any type of SCRUM project, importance conclude asfollows

2/14/2013 20

Weights given by industry expertise

Quality Factor WeightsFunctionality 0.25Usability 0.20Efficiency 0.15Reliability 0.15Portability 0.13Maintainability 0.12Total 1.00


21/31

Validity & Reliability Analysis

2/14/2013 21

Table A

Table B


22/31

Pearson Correlation Analysis All quality factors to project performance were

significant because of for all p values < 0.05. Highest internal relationship is between

Functionality and Efficiency which is about .907and least correlation between internal quality

factors is 0.438 which is between usability andmaintainability.

Highest relationship to the project performance isefficiency quality factor which is 0.849 and leastrelationship quality factor to the projectperformance is portability and person correlation isabout 0.426.

2/14/2013 22

St ti ti l A l i


23/31

Statistical Analysis -Regression Project Performance = 2.270 + 0.528 Functionality +

Error, R2 = 0.536 which means 53.6 percent of thevariation of Project Performance can be explained byFunctionality.

Project Performance = 2.760 + 0.414 Reliability + Error,R2 = 0.363 which means 36.3 percent of the variation ofProject Performance can be explained by Reliability

Project Performance = 2.647 + 0.439 Usability + Error,R2 = 0.415 which means 41.5 percent of the variation ofProject Performance can be explained by Usability.

2/14/2013 23

Statistical Anal sis


24/31

Statistical AnalysisRegression Project Performance = 1.552+ 0.685 Efficiency + Error,

Also R2 = 0.720 which means 72 percent of thevariation of Project Performance can be explained byEfficiency.

Project Performance = 3.326+ 0.268 Maintainability +Error, Also R2 = 0.208 which means 20.8 percent of thevariation of Project Performance can be explained byMaintainability.

Project Performance = 3.469+ 0.241 Portability + Error,Also R2 = 0.181 which means 18.1 percent of thevariation of Project Performance can be explained byPortability

2/14/2013 24

Statistical Analysis


25/31

Statistical AnalysisRegression Project Performance = 1.324- 0.099 Functionality -0.096

Reliability + 0.185 Usability + 0.745 Efficiency + 0.102Maintainability - 0.099 Portability + Error

R2 = 0.777 which means 77.7 percent of the variation of

Project Performance can be explained by all qualityfactors which has more stronger relationship

2/14/2013 25


26/31

Conclusion Researcher has identified six important quality factors

for SCRUM software Export companies after conductinginterviews and discussions with the industry experts.These quality factors were in match exactly with ISO9126.

Most valid construct out of quality factors was Efficiencyand the output of principal component analysisexplained that the first factor accounts for 86% followedby Functionality (78%), Reliability (69%), Maintainability(68%), Portability (59%), Usability (58%).

Also Cronbachs Alpha for all research constructs weregreater than 0.7. Therefore it has been proven that theconceptual model is very valid and very reliable.

2/14/2013 26


27/31

Conclusion Project performance has significant positive relationship

with all quality factors, Functionality, Reliability, Usability,Efficiency, Maintainability and Portability because of allp value


28/31

Recommendations

SCRUM related projects, it is recommended toconsider all six quality factors together for betterresults and for keeping high interrelationship betweenquality factors and project performance.

It is recommended for SCRUM practicing companies

to focus more on quality factors Portability,Maintainability, Reliability and Usability respectively.

2/14/2013 28


29/31

Suggested Future Studies It is recommended to conduct a study with applicability

of CMMI with SCRUM together. Companies now also starting software development

with KANBAN and with LEAN concepts. Therefore for afuture researcher it will be beneficial for conducting

research on applying software quality with abovementioned agile methodologies.

2/14/2013 29


30/31

Limitations Sample covers only 3 scrum projects from each

company. SCRUM practicing companies from registered bodies of

Sri Lanka.

42% of the sample represents USA projects; therefore,

the sample may be biased. Project performance factors are limited to effort,

productivity, schedule and cost as scope of theresearch.

Research fully based on Sri Lankan Software exportcompanies.

2/14/2013 30


31/31

Thank You All

Suggestions are welcome !!!

2/14/2013 31

suresh- final viva07122010

Documents