Search icone
Search and publish your papers

Ascertaining the use of agile methodology in Extreme Programming (XP) in the software development industry

Or download with : a doc exchange

About the author

General public

About the document

Published date
documents in English
28 pages
General public
1 times
Validated by
0 Comment
Rate this document
  1. Abstract
  2. Chapter 1
    1. Introduction
    2. Overview
  3. Chapter 2
    1. Agile modeling
    2. Extreme Programming (XP)
    3. The lifecycle of an XP project
    4. Scrum
    5. Feature Driven Development (FDD)
    6. Dynamic system development method
  4. Chapter 3
    1. Research methodology
    2. Type of methodology used
    3. Agile methods and offshore development
    4. People oriented
    5. Adaptive
    6. Conformance to actual
    7. Balancing flexibility and planning
    8. Empirical process
    9. Decentralized approach
    10. Simplicity
    11. Collaboration
    12. Small self organizing teams
  5. Chapter 4: Research findings and discussion
    1. Comparison of agile and heavyweight
    2. Project size
    3. People factor
    4. Risk factors
    5. Questionnaire format
    6. Software development questions
    7. General questions
    8. The results
    9. Mode of methodology used
    10. Using agile or heavyweight for software development
    11. Pros and cons of agile methods
  6. Chapter 5: Conclusion
  7. Chapter 6: Recommendations for further research
  8. References

Software has been division of modern society since previous 50 years. There are many software development methodologies in use. Some companies have their own customized methodology for developing the software but majority of them speak about two kinds of methodologies: heavyweight and lightweight. Heavyweight methodologies are also taken as the traditional method to develop software; they claim their support to comprehensive planning, detailed documentation, and expansive design. The lightweight methodologies are called as agile modeling and they have gained necessary attention from the software engineering community in the previous few years. Unlike traditional methods, agile methodologies give short iterative cycles and they rely on tacit knowledge within a team as opposed to documentation.

In this dissertation, it is described that the characteristics of some traditional and agile methodologies that are commonly used in software development. It is also discussed that the strengths and weakness among the two opposing methodologies and granted the challenges associated with implementing agile processes in the software industry. This anecdotal evidence is increasing regarding the effectiveness of agile methodologies in certain environments; but there has not been much collection or analysis of empirical evidence for agile projects. Yet to support this dissertation a questionnaire was conducted, soliciting feedback from software industry practitioners to evaluate which methodology has a better success rate for various sizes of software development. According to our findings agile methodologies can grant larger number of advantages for small scaled and medium scaled projects but for large scaled projects traditional methods seem more in use for their advantages.

[...] The last two phases are the iterative part of the procedure that supports the agile development with quick adaptations to late changes in needs and business requirements. The FDD approach includes regular and tangible deliverables, along with precise monitoring of the progress of the report (29). FDD comprises of five sequential steps, an explanation of the various functions and responsibilities used in FDD. Feature Driven Development processes Develop an Overall Model - A high level walk through of the system scope and its situation is performed by the domain expert to the team members and chief architect. [...]

[...] Following this, the challenges associated with implementation of agile processes in the software industry according to software practitioners and anecdotal evidence. To conclude, I conducted a questionnaire to gather feedback from software developers in Perth and analyzed which methodology was used to develop software and as well as their views on agile and heavyweight methodologies. Chapter 2 Literature review Agile Modeling Agile devotes quality of being agile; readiness for motion; activity, nimbleness, dexterity in motion? as mentioned in the Oxford Dictionary ?software development methods are attempting to offer once again an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes?. [...]

[...] Questions were also aimed to determine which aspects of the agile and heavyweight methodology is most appealing and does not appeals to the respondents in development. In addition, the respondents granted feedback on whether the adoption of agile and heavyweight methodologies had any impact on the project cost and software quality. Finally respondents gave their opinion on what they thought is a more suitable methodology for every scaled project and to what level they would take an agile technique whilst using a heavyweight methodology. [...]

Recent documents in computer science category

Net neutrality in United States

 Science & technology   |  Computer science   |  Presentation   |  10/02/2018   |   .doc   |   3 pages

Reconstructing householder vectors from tall-skinny QR

 Science & technology   |  Computer science   |  Presentation   |  04/21/2017   |   .doc   |   4 pages