1. Provide a well-formulated thesis statement in your introduction paragraph.

2. Explain how a business user could be involved in the core activities of building an information system.

3. Analyze how software development methodologies (such as agile development) can work in tandem with project management for the benefit of both information systems development projects and organizations.

4. Evaluate how project managers and/or IT managers can ensure that information system development projects arein alignment with business strategies and goals.5. Summarize your findings in a five-page paper using proper APA formatting

Attached files are to be used as source of reference.

 

 

Published in IET SoftwareReceived on 22nd June 2011Revised on 14th August 2011doi: 10.1049/iet-sen.2011.0110ISSN 1751-8806Agile software development methodology formedium and large projectsM. Rizwan Jameel QureshiFaculty of Computing and Information Technology, King Abdul Aziz University, P.O. Box 80221, Jeddah 21589,Kingdom of Saudi ArabiaE-mail: anriz@hotmail.comAbstract:Extreme programming (XP) is one of the most widely used agile methodologies for software development. It intends toimprove software quality and responsiveness to changing customer requirements. Despite the facts that the use of XP offers anumber of beneFts and it has been a widely used agile methodology, XP does not offer the same beneFts when it comes tomedium and large software projects. Some of the reasons for this are weak documentation, lack of strong architecture andignorance to risk awareness during the software development. Owing to the ever-increasing demand of agile approaches, thisstudy addresses the problem of XP’s ability to handle medium and large projects. Most of the companies that employ XP as adevelopment methodology for medium and large projects face this problem, which echoes the importance of this problem. Toaddress this problem, in this study XP model is extended in such a way that it equally offers its beneFts for medium- andlarge-scale projects. As an evaluation of the extended XP, three independent industrial case studies are conducted. The casestudies are described and results are presented in the study. The results provide evidence that the extended XP can bebeneFcial for medium and large software development projects.1IntroductionAgile methods for software developed emerged in the mid-1990s[1, 2]and focus on agility for software development.In essence, agility means responding to changes quicklyand efFciently. Possible changes required in softwareprojects are in budget, schedule, resources, technology,requirements and team. These are the ‘reacting’ changes onwhich agile models focus by delivering Frst increment in acouple of weeks and complete software in couple ofmonths. Twelve golden principles have been deFned in anagile alliance meeting conducted in 2001[1]. Theseprinciples provide support for development of only smallsoftware projects having small teams[3]. However, there isno guidance about how to customise agile process modelsfor the development of medium and large software projects[4–6]. There are several criteria to classify projects such assize, complexity and mission criticality[7].Generally, a software project is considered ‘small’ if line ofcode (LOC) of the project is between 10 000 and 40 000,‘medium’ if LOC is between 40 000 and 100 000 and‘large’ if LOC are typically over 100 000. In addition tothis, ‘size’ of a project can also be measured in terms ofhuman effort (e.g. number of person-months applied)[7].This paper measures ‘size’ in terms of LOC to classify theprojects as small, medium and large.Key beneFts of agile models are fast development and costreduction. ±ast development in some cases leads to poorsoftware (SW) quality and carrying all disadvantagesof rapid application development (RAD) and prototypemodels, such as weak documentation, difFcult to upgrade,lack of reuse and excessive maintenance[8]. Extremeprogramming (XP) is a widely used among all agilemodels. A number of studies have been reported abouteffective implementation of XP for small projects[9, 10].XP was proposed based on ideas and practices frompreviously proposed process models to achieve advantagessuch as time saving, cost reduction, refactoring andsuitability for small projects with small teams[7, 11].Anexample is the refactoring technique which improves asoftware quality in terms of design and code throughoutsoftware development. However, some drawbacks of XPthat can be found in the literature are inappropriate forsafety critical projects, limited support for outsourcing,inadequateassistancefordistributeddevelopmentenvironment, weak documentation and unsuitable formedium and large projects[12–14].Medium and large projects have some characteristicssimilar to small projects such as time constraints, changingbusiness situations and vague requirements[12]. Softwareindustry has to bear an immense amount of stress to deliverproducts timely without sacriFcing quality. Traditionalmethodologies are not fulFlling the need of softwareindustry to achieve fast development without compromisingquality whereas agile methodologies cannot be directlyimplemented for medium and large development projectsbecause of inadequate documentation, weak architectureand lack of risk management. Therefore there is a need toadapt the agile methodologies for medium and largeprojects to achieve fast development with high quality to358IET Softw., 2012, Vol. 6, Iss. 4, pp. 358–363&The Institution of Engineering and Technology 2012doi: 10.1049/iet-sen.2011.0110www.ietdl.org

 

Attachments:

• 1494044491-agile software development methodology.pdf
• 1494044493-Effective management and IT.pdf