1

2

Suggested Framework to Apply Agile Methodology in Egypt

Submitted by : Tasneem Abd El-Hameed Mohamed

Supervised by:

Dr. Mahmoud Abd EllatifAssociate Professor of Information Systems,

Faculty of Computers & Information,

Helwan University, Cairo, Egypt

Supervised by:

Dr. Sherif KholiefAssociate Professor of Information Systems,

Faculty of Computers & Information,

Helwan University, Cairo, Egypt

Faculty of Computers and InformationSystems Department

A Master’s thesis in partial fulfillment of the requirements for the master Degree in information system

3 Jan 2017

3

Thesis Consists of Chapter 1: Introduction

Chapter 2: Background of study

Chapter 3: Literature review

Chapter 4 : Methodology

Chapter 5: Result of empirical study

Chapter 6: Conclusion and Future work

4

Introduction

Problem Statement

Study Objectives

Study Methodolog

y

5

•By increasing the needs of turning manual work to automated work in a lot of enterprises all over the worlds in all aspects.

•Software development process has become very complicated.

•Now a day, different software development methodologies have been introduced and applied.

Introduction

6

•Despite of applying different software development process in different projects

•Most of Projects Faced a lot of Challenges

Problem Statement

Project Success16%

Project Chal-lenged

53%

Project Impaired31%

Chaos Report

7

•Agile methodology become most popular and more successful than traditional methodologies

Problem Statement

8

• In Egypt, software services has been grew to GDP by 13% in 2014 to 2015 (According to ITIDA )

•However, There is no specific survey or study conducted by information technology industry agency (ITIDA) about software Project Success in Egypt

•Also, no specific Survey or study about agile success adoption in Egypt

Problem Statement

9

•Chaos Report Not covered geographic result.

•VersionOne, 2015 No respondent From Africa – Egypt Region

•VersionOne, 2016 1 % From Africa – no specific information from Egypt

•From Previous studies: less evidence about agile critical success factors adoption in Egypt- Africa Region

Problem Statement

10

•State a proper framework1. That could be used by Egyptians software

companies to ensure the success of agile adoption.

2. For failure factors to work on them while agile adoption to avoid failure.

Study Objectives

Survey

Hypothesis

Data Collection

Findings

Hypothesis confirm or reject

Methodology

11

• Tackled most of critical success and failure factors surveys and studies that have been introduced

Literature Review Survey

Dimensions Factors

{Belassi1996}

{Mahanti2006}

{Chow2008}

{Misra2009}

{Mansor 2010}

{Wan2010}

{Melo2011}

{Kumar2012}

Sheffield2013}

{Hummel2015}

Technical

High expertise for team √   √ √   √   √   √

Practices         √ √ √     √

12

Dimensions Factors

{Belassi1996}

{Mahanti2006}

{Chow2008}

{Misra2009}

{MansorSandNoor2010}

{Wan2010}

{Melo2011}

{Kumar2012}

{Sheffield2013}

{Hummel2015}

Project

Project type √   √ √           √

Schedule   √ √       √      

Team Size     √   √   √     √

13

14

• From Literature Survey Critical Success Dimension collected and displayed in a mind map model Called 4POT

Literature Review Survey

15

CSD

People

Project

Process

Product

Organization

Technical

4POT Mind Map Model

Literature Review Survey

16

• Factors merged under one keywordExample: high Competence and expertise and technical background for team and project manager “High Expertise”• Free success factors inserted into its related

Dimension

Literature Review Survey

17

CSF

Project

Project Type

Schedule

Team Size

Pilot Project

Minimum change of requirement

Example

• Mapping Each factor with related Agile principle

Dimensions Factors

{Belassi1996}

{Mahanti2006}

{Chow2008}

{Misra2009}

{Mansor 2010}

{Wan2010}

{Melo2011}

{Kumar2012}

Sheffield2013}

{Hummel2015}

Principles

Technical

High expertise for team and organizational factor

√   √ √   √   √   √ P9

Practices         √ √ √     √ P9

18

19

•Principle 9 States that: Continuous attention to technical excellence and good design enhances agility.

•Then CSDF Model Displayed

CSDF Mind Map Model

CSF

Process Organization

Product Technical

People Project

Education and Support

Customer Centric issue

Management Style

Communication Skills

Motivation

Report and Adapt

Committed

Project Champion

Regular Delivery

Effective Requirment

Integrate to External

Proper Methodology

Simplicity

Software Reuse

Software charcteristics

Project Type

Practises

Schedule

Team Size

Pilot Project

Minimum change of requirement

Sustain Agility

High Expertise

Corporate Culture

Environment

Team Distribution

Troubleshooting team

Tool usage 20

21

• Each Factors Drawn a hypothesis

Hypotheses

+ve Support from top management Effect

Agile Success Adoption

Dimension Factors Hypothesis H#People Education and support Support from top

management will have a successful positive effect on Agile Success adoption 

H1a

Customer Centric issues Customer Collaboration during the project with team members will have a successful positive effect on Agile Success adoption

H1b

Communication skills Good Communication between team will have a successful positive effect Agile Success adoption

H1e

22

23

• Initial Pre-test was carried out by sending a sample of questionnaire to five agile experts volunteer.•Each volunteer was given the survey via online survey tool.•Each volunteer completed the full survey, and asked for initial feedback.•The volunteer were asked Certain questions about the meaning of the items on the survey.

Pre-Test Questionnaire

24

• Some Questions were found to be ambiguous based upon the respondent’s misidentification of the question’s meaning.•Questions were modified based upon the pre-test•Final survey created.

Questionnaire Structure

25

•Questionnaire sent to 1000 across social media and emails

•Only 172 Responded

•Sample t-test method applied using SPSS tool.

•Hypotheses test applied

Result of Empirical study

 Sig. (2-tailed) N Mean

Std. Deviation

Std. Error Mean

Practices .007 136 4.17 .726 .062

Troubleshooting .009 136 4.20 .868 .074

High Expertise .000 136 4.50 .730 .063

Tool usage .094 136 4.13 .864 .074

26

H# Factors ResultH1a Customer Centric issues AcceptedH1b Management style RejectedH1c Management style RejectedH1d Communication skills AcceptedH1e Motivation RejectedH1f Education and support AcceptedH1g Committed AcceptedH2a High Expertise AcceptedH2b Troubleshooting Accepted

Hypotheses Test

27

28

Critical Success Factor

29

Failure Factor

30

•To Avoid Agile Failure

Management style Educating project managers and coaching them

Motivation encouraging employees to prevent employee’s boringness, by introducing some gamification like daily standup, planning poker

Recommendation

31

Effective Requirement applying and defining some practices for writing and slicing user story, designing a prototype, and personas.

Tool Usage Train employees to use different and new tools to help the team for accelerating the agile process, tools for automation, coding, analysis, designing and Agile management.

Recommendation

A Qualitative study to determine the success and failure factors

Empirical Investigation about the type of methodologies that applied in Egyptians software companies

What are the most suitable and proper methodology that can be adopted in Egyptian Enterprises

SAFe principles Egyptian software companies

Future Work

32

33

• Abd, T. et al., 2016. Identify and Classify Critical Success Factor of Agile Software Development Methodology Using Mind Map. International Journal of Advanced Computer Science and Applications(ijacsa), 7(5), pp.83–92.

List of Publication

34

• Thanks Dr. Shreef Mazen • Thanks Dr. Maha Attia • Thanks to Dr. Mahmoud Abd El Latif• Thanks Dr. Sherif kholief • Thanks My Mother, Father, Brothers and

my grandma for their support and helping• Thanks to my Manager Tamer badr • Finally Thanks to Amr Noaman, Maged

Kotchy, Mona shokrof, Khaled Rawy for their help

Acknowledgements

35