\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={A Review of Mobile Application Development in the Agile Software Development Environment},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2019-01-15 (revised: 15 January 2019)}
\def\TheID{\makeatother }
\def\TheDate{2019-01-15}
\title{A Review of Mobile Application Development in the Agile Software Development Environment}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{Neymis Misiko  Jacob}

             \affil[1]{  Umma University}

\renewcommand\Authands{ and }

\date{\small \em Received: 12 December 2018 Accepted: 31 December 2018 Published: 15 January 2019}

\maketitle


\begin{abstract}
        


With the ever changing dynamic environment in mobile devices, mobile software applications need to cope with some particular performance environment that include the limited resources, high autonomy requirements and mark et regulations among other constraints [1]. To provide a software development process that responds to these challenges, adoption of Agile methodology that follows an iterative approach to build software rapidly where the entire software development lifecycle is brok en down into smaller iterations helps to minimize overall risk s. This allows software projects developed though agile methodologies to be easily modified rapidly to meet the users/customers? requirements. This paper assesses the development of mobile applications in the agile software development environment.

\end{abstract}


\keywords{agile development environment, mobile applications, mobile-D.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
ccording to Sommerville \hyperref[b1]{[2]}, software processes are categorized as either plan-driven or agile processes. Plan-driven processes involves all process activities being planned in advance and progress is measured against the devised plan. Agile processes on the other hand, involves planning that is incremental and is much easier to change the process to reflect changing customer requirements. A mix of both processes in SE is important as each comes with its values necessary for product development. As Boehm and Turner \hyperref[b2]{[3]} discuss, each approach is suitable for different types of software. Generally, SE need to find a balance between plan-driven and agile processes \hyperref[b1]{[2]}. Spataru \hyperref[b3]{[4]} established that agile methods are good approaches towards mobile application development coined together with end-user inclusion in the lifecycle, performance testing of components and adoption of software product line principles. 
\section[{II.}]{II.} 
\section[{The Concept Agile Software Development}]{The Concept Agile Software Development}\par
Corrall et.al \hyperref[b0]{[1]} stated that mobile software development and applications need to cope with a particular execution environment that have limited resources, high autonomy requirements, market regulations, and many other constraints. There is need for developers to therefore to employ the agile Author: Jomo Kenyatta University of Agriculture and Technology. e-mail: Jneyole434@gmail.com development which is an umbrella term for several iterative and incremental software development methodologies \hyperref[b4]{[5]}. According to Sriram and Saji \hyperref[b5]{[6]} a development methodology has a direct relationship with managing project complexity. It accompanies and has implications for usability, maintainability, adaptability, reliability and portability of the software being developed.\par
In the late 1990's, agile methodologies became dominant to address some shortcomings of traditional methodologies like heavy documentation, lack of productivity, reliability and simplicity \hyperref[b6]{[7]}. Agile alliance, in response to more process driven traditional methodologies, stresses upon people, communication and customer priorities \hyperref[b7]{[8]}. Also, different agile methodologies has exhibited flexibility to working within constraints, without demanding major upfront investments, while being adaptable to changing market conditions \hyperref[b10]{[9]}.\par
The fundamentals of agile methodology namely the incremental and iterative development methods required the researchers to work on the principle of separating design, implementation and testing \hyperref[b11]{[10]}. To date the most popular agile methodologies include Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development, and Feature-Driven Development (FDD) \hyperref[b4]{[5]} have been employed in software development giving software products that are versatile and more robust to the market. Sriram and Saji \hyperref[b5]{[6]} cited a document by Nerur \& Balijepally \hyperref[b12]{[11]} on the main characteristics of agile development methodologies stating that the main characteristics of agile development methodologies include more autonomy, decision-making discretion and adaptive understanding, have a theoretical background, which is consistent with problem framing, problem solving approaches in architecture and strategic management. This main characteristics indicate that agile methodologies provide the designers with greater opportunities to develop software products that reliable. 
\section[{III. Plan-Driven and Agile Development}]{III. Plan-Driven and Agile Development}\par
Software processes can be categorized as either plan -driven or agile processes. According to \hyperref[b1]{[2]}, Plan -driven are processes where all of the process activities are planned in advance and progress is measured against this plan. In comparison to agile A processes, Sommerville \hyperref[b1]{[2]} indicates that in agile planning is incremental and it is easier to change the process to reflect changing customer requirements. Each approach is therefore suitable for different types of software. Good practice as discussed by Boehm and Turner \hyperref[b2]{[3]} is that there is need to find a balance between plan-driven and agile processes.\par
Software processes are complex and, like all intellectual and creative processes, rely on people making decisions and judgments \hyperref[b1]{[2]}. In line with this, software processes can be improved by process standardization where the diversity in software processes across an organization is reduced. Through this, there is improved communication and a reduction in training time, and makes automated process support more economical. Standardization is important first step in introducing new software engineering methods and techniques and good software engineering practice.\par
According to Mudasir Kirmani \hyperref[b13]{[12]}, agile methodology follow an iterative approach to build software rapidly where the entire software development lifecycle is broken down into smaller iterations. The iterations helps to minimize overall risks allowing a software development project be easily modified on the upfront and strictly maintaining the project schedule and budget. I all this the software product is delivered on time and according to the budget that it was initially proposed on.\par
Inspite of the agile methodology being iterative, the methodology has some limitations \hyperref[b5]{[6]}. Such as dependence on run-time tacit knowledge rather than more documented information, lack of traceable and proved implementation guidelines for mission critical projects, lack of adequate support for repetitive and large scale projects and team requirement of highly talented, self-motivated individuals with a high degree of implementation freedom \hyperref[b6]{[7]}.The resulting software product/ project developed using agile methodologies are dependent mainly on organizational factors like customer commitment, decision time, team location and composition, corporate culture and people factors like competency and self-motivation \hyperref[b14]{[13]}.\par
According to Andrei C. Spataru \hyperref[b3]{[4]} the main argument against agile methods is the asserted lack of scientific validation for associated activities and practices, as well as the difficulty of integrating planbased practices with agile ones. In order to address various concerns, several methodologies within the agile category have evolved Abrahamsson et al. \hyperref[b15]{[14]} identifies ten of them as truly agile. They include: -SCRUM, PP, ASP, FDD, XP, DSDM, Crystal, AM and ASD. For mobile software development, agile methods represent a relatively new approach to software development \hyperref[b3]{[4]}.\par
IV. 
\section[{Agile Project Management}]{Agile Project Management}\par
According to Beck et al. \hyperref[b7]{[8]} Agile alliance, in response to more process driven traditional methodologies, stresses upon people, communication and customer priorities. Rajagopalan and Mathew \hyperref[b5]{[6]} indicated that agile software development methodology has a direct relationship with managing project complexity. According to Martin et al. the customer plays a very important role in agile projects with key responsibilities to drive the project, interact constantly with business users and provide requirements and participate in retrospection to test the intermediate deliverable and its compliance \hyperref[b16]{[15]}. However, at times the customer may fail to keep these practices or be consistent due to the dynamic nature of development projects.\par
In solving this, the customer's role is essentially not played by a single person but there are pseudo roles assumed by different people to drive the project effective conclusion. Known by role labels such as the technical liaison, negotiator, and customer coach, skill specialists for designer, tester and quality facilitator \hyperref[b5]{[6]}. Chow et al. \hyperref[b17]{[16]} Identified factors that can serve to guide in the selection of agile methodologies for projects in organizations with specific characteristics. Project success or failure in agile methodologies are guided by six key dimensions of agile methodologies with specific attributes to guide selection of a specific methodology. They include: -delivery strategies, software engineering techniques, team capability, project management process, team environment and customer involvement \hyperref[b5]{[6]}.\par
V. 
\section[{Agile Methods in Mobile Software Development}]{Agile Methods in Mobile Software Development}\par
According to Spataru \hyperref[b3]{[4]} mobile applications market is currently undergoing rapid expansion. He further asserts that mobile platforms continue to improve in performance as the users' need for a wide variety of mobile applications increases. Software development for mobile platforms comes with unique features and constraints. The development environment and the technologies that support the software are different compared to "traditional" settings. Abrahamsson et al \hyperref[b18]{[17]} identified important distinguishing characteristics to be a high level of competitiveness, necessarily short time-to-delivery and added difficulty in identifying stakeholders and their requirements.\par
Due to substantial differences in the environment and in platform specifications modifications in customer needs and expectations. Abrahamsson \hyperref[b19]{[18]} states Technological constraints apply to mobile platforms in the form of limited physical resources and rapidly changing specifications. There is need to focus on agile methods and their suitability for mobile application development. Agile methods for mobile software development emphasize the adaptability of enterprises to a dynamic environment \hyperref[b20]{[19]}. The unique features of agile methods derive from the list of principles found in the Agile Manifesto \hyperref[b21]{[20]}.\par
Smart mobile devices like cellphones and tablets are a key target for software products and services \hyperref[b0]{[1]}. Consequently, software applications for the smart devices is receiving greater attention by companies' individuals and business enterprises globally. Along with the features and computing power offered by these mobile equipment, mobile software applications (apps) bear the big challenge of performing satisfactorily in a heterogeneous and resource-limited environment \hyperref[b13]{[12]} that demands high availability, efficient performance and short response time while delivering value to the end user.\par
In the mobile ecosystem mobile software development rapidly requires updates and developments to meet the diverse customer requirements against a universe of constraints that exist on mobile environments namely evolving and inherent. The evolving constraints include current limitations that will be solved in the future by the evolution in technology, resources, bandwidth and coverage. Inherent constraints on the other hand are those intrinsic to mobile platforms, since they are part of the operational condition of the system and will not be solved in the near future \hyperref[b0]{[1]}. These constraints should be taken into account by developers to determine the practices to relieve them as means of non-functional requirements.\par
Wasserman \hyperref[b22]{[21]}, indicated that mobile applications development are similar to software engineering for other embedded applications. However, the mobile applications development present s ome additional requirements that are less commonly found if compared to traditional software applications \hyperref[b13]{[12]}. Boehm and Turner \hyperref[b23]{[22]} identify fundamental concepts to agile development such as: simple design principles, a large number of releases in a short time frame, extensive use of refactoring, pair programming, testdriven development, and seeing change as an advantage. Abrahamsson, et al. \hyperref[b24]{[23]} mention that an agile development method is incremental, cooperative, straightforward and adaptive.\par
Along the agile methodology, a new development methodology specifically tailored for mobile application development, called Mobile-D, is presented \hyperref[b18]{[17]}. The method is based on agile practices, drawing elements from well-established agile methods such as Extreme Pro gramming and Crystal Methodologies and also from the heavier Rational Unified Process \hyperref[b25]{[24]}. The Rational Unified Process is explained from a practical point of view in \hyperref[b26]{[25]}. Practices associated to Mobile-D include test-driven development, pair programming, continuous integration, refactoring, as well as software process improvement tasks. The methodology serves as a basis for this work, and will be further detailed in the following section \hyperref[b27]{[26]}.\par
The Mobile-D process should be used by a team of at most ten co-located developers, working towards a product delivery within ten weeks. The Mobile-D methodology of the agile method comprises five phases: Explore, Initialize, Productionize, Stabilize, and System Test \& Fix. Each of these phases has a number of associated stages, tasks and practices. The complete specifications of the method are available in \hyperref[b28]{[27]}.\par
One issue with the mobile-D method is that the well-known practices adopted by the Mobile-D process do not account for the performance of components under development, either at design time or during coding \hyperref[b3]{[4]}. To address the issue integration of performance testing activities in the lifecycle, more specifically extending the Test-Driven Development practice with performance aspects is mentioned. 
\section[{VI.}]{VI.} 
\section[{Conclusions}]{Conclusions}\par
The importance of projection completion JIT cannot be over emphasized, with the use of the agile methodology in mobile software development, it introduces end -user feedback support, application categories and software product lines principles. The Mobile-D presents more of the ideal characteristics. Since the methodology was improved in aspects such as the inclusion of performance testing in the lifecycle. The ever dynamic changing environment of the mobile devices, software developers for mobile applications must be up to the task to develop software apps that meet this limitations and still satisfy the user needs. The different agile methodologies have demonstrated flexibility to working within constraints, without demanding major upfront investments, while being adaptable to changing market conditions \hyperref[b10]{[9]}. 			\footnote{( ) C © 2019 Global Journals} 			\footnote{© 2019 Global Journals} 			\footnote{( )© 2019 Global Journals} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Beck et al.]{b7}\label{b7} 	 		\textit{},  		 			K Beck 		,  		 			M Beedle 		,  		 			A Cockburn 		,  		 			W Cunningham 		,  		 			M Fowler 		,  		 			J Grenning 		,  		 			J Highsmith 		,  		 			A Hunt 		,  		 			R Jeffries 		,  		 			J Kern 		,  		 			B Marick 		,  		 			R C Martin 		,  		 			S Mellor 		,  		 			K Schwaber 		,  		 			J Sutherland 		,  		 			D Thomas 		,  		 			B 		.  		 	 
\bibitem[Spataru ()]{b3}\label{b3} 	 		\textit{},  		 			A C Spataru 		.  	 	 		\textit{Agile Development Methods for Mobile Applications}  		2010.  		 			University of Edinburgh 		 	 
\bibitem[Spataru ()]{b27}\label{b27} 	 		\textit{},  		 			A C Spataru 		.  	 	 		\textit{Agile Development Methods for Mobile Applications}  		2010.  		 			University of Edinburgh 		 	 
\bibitem[Cho ()]{b6}\label{b6} 	 		‘A hybrid software development method for large-scale projects: rational unified process with scrum’.  		 			J Cho 		.  	 	 		\textit{Issues in Information Systems}  		2009. 10  (2)  p. .  	 
\bibitem[Chow and Cao ()]{b17}\label{b17} 	 		‘A survey study of critical success factors in agile software projects’.  		 			T Chow 		,  		 			D B Cao 		.  	 	 		\textit{Journal of Systems and Software}  		2008. 81  (6)  p. .  	 
\bibitem[Versionone (2017)]{b4}\label{b4} 	 		\textit{Agile 101 General Learnings},  		 			Versionone 		.  		30th July 2017.  	 	 (VersionOne Company) 
\bibitem[Kirmani ()]{b13}\label{b13} 	 		‘Agile methods for mobile application development: A comparative analysis’.  		 			M M Kirmani 		.  	 	 		\textit{International Journal of Advanced Research in Computer Science}  		2017. 8  (5)  p. .  	 
\bibitem[Agile Software Development Manifesto. Retrieved from Manifesto for Agile Software Development ()]{b21}\label{b21} 	 		\textit{Agile Software Development Manifesto. Retrieved from Manifesto for Agile Software Development},  		 \url{http://agilemanifesto.org/}  		2001.  	 	 (Agile Alliance) 
\bibitem[Abrahamsson et al. ()]{b15}\label{b15} 	 		‘Agile Software Development Methods: A Comparative Review1’.  		 			P Abrahamsson 		,  		 			N Oza 		,  		 			M T Siponen 		.  	 	 		\textit{Agile Software Development},  				 (Berlin, Heidelberg)  		2010. Springer. p. .  	 
\bibitem[Abrahamsson et al. ()]{b24}\label{b24} 	 		‘Agile Software Development Metods: Review and Analysis’.  		 			P Abrahamsson 		,  		 			O Salo 		,  		 			J Ronkainen 		,  		 			J Warsta 		.  	 	 		\textit{VTT Electronics},  				2002.  	 
\bibitem[Abrahamsson ()]{b19}\label{b19} 	 		‘Agile Software Development of Mobile Information Systems’.  		 			P Abrahamsson 		.  	 	 		\textit{Advanced Information Systems},  				 (Berlin)  		2007.  	 
\bibitem[Corral et al. ()]{b0}\label{b0} 	 		\textit{Agile Software Development Processes for Mobile Systems: Accomplishment, Evidence and Evolution},  		 			L Corral 		,  		 			A Sillitti 		,  		 			G Succi 		.  		2013. Berlin Heidelberg: Springer.  	 
\bibitem[Mohammad et al. ()]{b10}\label{b10} 	 		‘Agile Software Methodologies: Strength and Weakness’.  		 			A H Mohammad 		,  		 			T Alwada'n 		,  		 			J A Ababneh 		.  	 	 		\textit{International Journal of Engineering Science and Technology (IJEST)}  		2013. 5  (3)  p. .  	 
\bibitem[Available (2017)]{b9}\label{b9} 	 		 \url{http://agilemanifesto.org/}  		\textit{Available},  				August 2017.  	 
\bibitem[Boehm and Turner ()]{b2}\label{b2} 	 		\textit{Balancing Agility and Discipline: A Guide for the Perplexed},  		 			B Boehm 		,  		 			R Turner 		.  		2003. Boston: Addison-Wesley.  	 
\bibitem[Boehm and Turner ()]{b23}\label{b23} 	 		\textit{Balancing Agility and Discipline: A Guide for the Perplexed},  		 			B Boehm 		,  		 			R Turner 		.  		2003. USA: Addison-Wesley.  	 
\bibitem[Vinekar et al. ()]{b14}\label{b14} 	 		‘Can agile and traditional systems development approaches coexist? An ambidextrous view’.  		 			V Vinekar 		,  		 			C W Slinkman 		,  		 			S Nerur 		.  	 	 		\textit{Journal of Information systems management}  		2006. 2  (3)  p. .  	 
\bibitem[Rajagopalan and Mathew ()]{b5}\label{b5} 	 		‘Choice of Agile Methodologies in Software Development: A Vendor Perspective’.  		 			S Rajagopalan 		,  		 			S K Mathew 		.  	 	 		\textit{Journal of International Technology and Information}  		2016. 25  (1)  p. .  	 
\bibitem[Beck and Andres ()]{b25}\label{b25} 	 		\textit{Extreme Programming Explained: Embrace Change},  		 			K Beck 		,  		 			C Andres 		.  		2004. USA: Addison-Wesley Professional.  	 	 (2nd Edition) 
\bibitem[Larman and Basili ()]{b11}\label{b11} 	 		‘Iterative and incremental development: A brief history’.  		 			C Larman 		,  		 			V R Basili 		.  	 	 		\textit{Computer}  		2003. 36  (6)  p. .  	 
\bibitem[Abrahamsson et al. ()]{b18}\label{b18} 	 		‘Mobile-D: an agile approach for mobile application development’.  		 			P Abrahamsson 		,  		 			A Hanhineva 		,  		 			H Hulkko 		,  		 			T Ihme 		,  		 			J Jäälinoja 		,  		 			M Korkala 		.  	 	 		\textit{Conference on Object Oriented Programming Systems Languages and Application; Companion to the 19th annual ACM SIGPLAN},  				 (Vancouver)  		2004.  	 
\bibitem[Vtt Electronics ()]{b28}\label{b28} 	 		‘Portal of Agile Software Development Methodologies’.  		 			Vtt Electronics 		.  		 \url{http://virtual.vtt.fi/virtual/agile/mobiled.html}  	 	 		\textit{VTT Electronics},  				2006. 2017.  	 	 (Accessed 01st September) 
\bibitem[Sommerville ()]{b1}\label{b1} 	 		\textit{Requirements Engineering},  		 			I Sommerville 		.  		2016. Boston, Massachusetts: Pearson Education, Inc. p. .  	 	 (in Software Engineering, 10th Edition) 
\bibitem[Salo ()]{b20}\label{b20} 	 		 			O Salo 		.  		\textit{Enabling Software Process Improvement in Agile Software Development Teams and Organisations},  				 (Helsinki)  		2006. VTT.  	 
\bibitem[Wasserman ()]{b22}\label{b22} 	 		‘Software engineering issues for Mobile application development’.  		 			A I Wasserman 		.  	 	 		\textit{proceedings of the FSE/SDP workshop on figure of software engineering research},  				 (the FSE/SDP workshop on figure of software engineering researchFoSER, New Mexico, USA.AC.)  		2010.  	 
\bibitem[Van ()]{b8}\label{b8} 	 		\textit{The agile manifesto},  		 			A Van 		.  		2014.  	 
\bibitem[Kroll and Kruchten ()]{b26}\label{b26} 	 		\textit{The Rational Unified Process Made Easy: A Practitioner's Guide to the RUP},  		 			P Kroll 		,  		 			P Kruchten 		.  		2003. USA: Addison-Wesley Professional.  	 
\bibitem[Nerur and Balijepally ()]{b12}\label{b12} 	 		‘Theoretical reflections on agile development methodologies’.  		 			S Nerur 		,  		 			V Balijepally 		.  	 	 		\textit{Communications of the ACM}  		2007. 50  (3)  p. .  	 
\bibitem[Martin et al. ()]{b16}\label{b16} 	 		‘XP customer practices: A grounded theory’.  		 			A Martin 		,  		 			R Biddle 		,  		 			J Noble 		.  	 	 		\textit{Agile Conference, AGILE'09 -IEEE},  				2009.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
