Agile Methodologies for Software Development: A Comprehensive Review

This report provides a comprehensive review of various agile methodologies for software development, including Extreme Programming, Scrum, Crystal families of methodologies, Feature Driven Development, and more. It discusses the phases, roles, and practices of each methodology, and compares them. The report also emphasizes the benefits of agile methodologies in managing complex projects.

Running head: PROJECT MANAGEMENT
PROJECT MANAGEMENT
Name of the Student
Name of the University
Author Note:

1
PROJECT MANAGEMENT
Table of content
Introduction....................................................................................................................................3
Different agile methods..................................................................................................................4
Extreme programming (XP)........................................................................................................5
Scrum.........................................................................................................................................6
Crystal families of methodologies..............................................................................................7
Feature Driven Development.....................................................................................................9
Rational methods.....................................................................................................................10
Dynamic development methods..............................................................................................11
Adaptive software development..............................................................................................12
Open source software development........................................................................................12
Pragmatic programming...........................................................................................................13
Conclusion....................................................................................................................................14
Bibliography..................................................................................................................................16

2
PROJECT MANAGEMENT
Introduction
Agile is known to be one of widely used framework of Software Development. This particular
methodology is recognized on global platform. A number of organization all over the globe have
implemented this methodology1. This particular methodology is all about promoting regular iteration for
development and testing. It is mainly encountered in the software development lifecycle of the whole
project. Two kind of activities that is testing and development are considered to be concurrent for the
given waterfall method. Agile can be stated as a set of practices which has been designed in such a way
that it can provide adaptability, flexibility, and communication2. It can act like working software which
comes up with proper plans and processes. This particular software development creates a platform
where team members can easily work together in efficient way. Agile methodology is very much
beneficial for managing some of complex projects. It comes up with certain number of practices which
can work with iterative and proper techniques which can be easily adopted3. Agile comes up with
various methods and methodologies which is needed for software development. It works in various
1 Anslow, C. and Maurer, F., 2015, February. An experience report at teaching a group based agile software
development project course. In Proceedings of the 46th ACM Technical Symposium on Computer Science
Education (pp. 500-505). ACM.
2 Baca, D., Boldt, M., Carlsson, B. and Jacobsson, A., 2015, August. A novel security-enhanced agile software
development process applied in an industrial setting. In Availability, Reliability and Security (ARES), 2015 10th
International Conference on (pp. 11-19). IEEE.
3 Brhel, M., Meth, H., Maedche, A. and Werder, K., 2015. Exploring principles of user-centered agile software
development: A literature review. Information and Software Technology, 61, pp.163-181.

3
PROJECT MANAGEMENT
stages like of software development like design of software and architecture, development, testing and
lastly deliveries of project management.
In the coming pages of the report an idea has been provided regarding the agile methodology.
After that various kind of agile methodology like extreme programming, scrum, feature-driven
development and many other have been discussed in details. The last section of the report mainly deals
with comparison of various kind of agile methodology.
Different agile methods
Various methods are introduced and reviewed in systematic way by making use of various
structure4. It comes up with proper roles, responsibilities, scope and present research with respect to
methods which are easily identified. Process can be defined as certain number of phases in the life cycle
of product by which the various software is developed. Roles and responsibility can be stated as
allocation of proper roles by which production of software is carried out by the help of development
team5. Practice emphasizes on certain number of activities and product of work which helps in defining
to be easily used in the given process. Proper adaptation and experience can be considered to be very
much helpful for various kinds of methods and practices which is followed by various developers 6. It
4 Conforto, E.C., Salum, F., Amaral, D.C., da Silva, S.L. and de Almeida, L.F.M., 2014. Can agile project
management be adopted by industries other than software development?. Project Management
Journal, 45(3), pp.21-34.
5 Dingsøyr, T. and Moe, N.B., 2014, May. Towards principles of large-scale agile development.
In International Conference on Agile Software Development (pp. 1-8). Springer, Cham.
6 Dingsøyr, T., Fægri, T.E. and Itkonen, J., 2014, December. What is large in large-scale? A taxonomy of scale for
agile software development. In International Conference on Product-Focused Software Process Improvement (pp.

4
PROJECT MANAGEMENT
emphasizes on certain number of methods which needs to be introduced in the given organization.
Scope of use helps in identification the different limits in each of the method.
Extreme programming (XP)
XP stands for Extreme programming which has developed from various kind of problems which
are caused due to long cycle development. It was started like a simple opportunity which was stated for
completing the job in given time. By long-term practice it has been found that this model is very much
effective in software development process. After carrying out number of successful trials which is in
practice, the XP method was easily theorized by the help of various principles and practices which needs
to be taken into account. XP method has been taken into account and easily lined up for various kind of
methodology for development of process. The term ‘extreme’ comes into action due to various
principles and practices which is seen due to some of the extreme level 7. The life cycle of XP comes with
main five phases that are Exploration, Planning, Production, iteration and lastly maintenance and death.
In the first phase that is Exploration, various customers can easily write details of story card
which is needed to be included in the beginning phase. Each and individual story aims in providing detail
information which respect to various kind of feature which is required to be added in the program 8. At
similar instance it helps in completing the project team by familiarizing with various kind of tools and
techniques which is required in the given project.
273-276). Springer, Cham.
7 Ghobadi, S. and Mathiassen, L., 2016. A model for assessing and mitigating knowledge sharing risks in agile
software development. Information Systems Journal, pp.1-33.
8 Heikkilä, V.T., Damian, D., Lassenius, C. and Paasivaara, M., 2015, August. A mapping study on requirements
engineering in agile software development. In Software Engineering and Advanced Applications (SEAA), 2015 41st
Euromicro Conference on (pp. 199-207). IEEE.

5
PROJECT MANAGEMENT
In the second phase that is planning, the priority is given for large number of stories and
agreement on the contents of small releases which is made in the first. The programmer can easily check
the amount of effort which needs to be schedule and proper agreed upon. The planning phase generally
requires couple of days.
Iteration phase is all about various kind of iteration of the whole system before the first release.
The schedule is designed in such a way that it can perform large number of iteration which requires
around four weeks for its proper implementation. The first iteration builds up a system with a proper
architecture for the whole system. This particular thing can be done by proper selection of various
stories9. Customers mainly aims in deciding the proper kind of stories which is needed for various kind of
stories. The overall functionality test can be easily done by various kind of customers which is needed
for running at each and every iteration. The last of phase of iteration in the system is all about
understanding the fact that the given product is ready for production.
Scrum
The Scrum method has been developed in such a way that it can easily manage the various
system for proper kind of development method10. It can be stated as an empirical method which aims in
providing various kind of industrial process of control theory. It is required for the development of
system which can result in providing flexibility, productivity and lastly proper adaptability11. It does not
provide any kind of specific software development technique which is needed for proper
9 Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile software development
methodologies: A comparative analysis. ACM SIGSOFT Software Engineering Notes, 40(1), pp.1-6.
10 Mc Hugh, M., McCaffery, F. and Casey, V., 2017. Barriers to using agile software development practices within
the medical device industry.

6
PROJECT MANAGEMENT
implementation of software. Scrum emphasizes the fact that how the given to team members can easily
function for producing flexible system which is encounter in the changing environment.
The main goal of Scrum is all about development of system which requires certain number of
techniques and technical variables12. The whole scenario is expected to change during the whole
process. This ultimately makes the development of process to be unpredictable and complex in nature.
It requires flexibility for the given system development method to easily respond to various kind of
changes. As a result of the development process, a system is needed for producing the usefulness of the
given system.
Scrum methodology helps in enhancing different kind of engineering practices in various kind of
organization. It requires various kind of management activities which helps in identifying any kind of
problem13. It is needed for analyzing the flexibility, productivity and lastly proper adaptability. It does not
provide any kind of software development methods or techniques which is needed for certain number
software development techniques which are needed for implementation of any kind of software. Scrum
emphasizes the fact that how the various kind of team members should function so that they can easily
11 Moran, A., 2014. Agile Software Development. In Agile Risk Management (pp. 1-16). Springer, Cham.
12 Ouriques, R.A.B., Wnuk, K., Gorschek, T. and Svensson, R.B., 2018. Knowledge Management Strategies and
Processes in Agile Software Development: A Systematic Literature Review. arXiv preprint arXiv:1807.04962.
13 Papadopoulos, G., 2015. Moving from traditional to agile software development methodologies also on large,
distributed projects. Procedia-Social and Behavioral Sciences, 175, pp.455-463.

7
PROJECT MANAGEMENT
provide large number of system which is very much flexible in nature14. Scrum methodology mainly
comes up with three stages that are pre-game, post-game a and lastly development.
Crystal families of methodologies
Crystal family of methodologies is generally inclusive of large number of methodologies which is
needed for selection of individual methodology which is needed for each and every project. This
particular methodology is generally inclusive of various kind of principles which is needed for various
kind of project. Crystal family comes up with certain number of rules and values which is needed by
various kind of project. The first thing which should be taken into account that various kind of project
are always in incremental way which comes with large number of incremental length 15. The whole
emphasis should be given on proper kind of communication and cooperation with large number of
people. Crystal methodologies does not provide any kind of limit with respect to any kind of
development practice, tools and lastly work products. It also allows the adaptation of various kind of
things like XP and scrum. This particular methodology comes up with objective of reducing the various
kind of work products. Along with this, it aims in giving proper kind of shaping the projects and
development of project as a whole. At present there are mainly three kind of crystal methodology that is
crystal clear, clear orange and clear orange web. Crystal clear has been especially designed for various
kind of medium size projects which comes up with 10 out 40 project member of project16. The ultimate
14 Rai, A.K., Agrawal, S. and KHALIQ, E., 2017. Identification of Agile Software Risk Indicators and Evaluation of Agile
Software Development Project Risk Occurrence Probability. International Journal of Engineering Technology,
Management and Applied Sciences, 5(7), pp.403-408.
15 Rosa, W., Madachy, R., Clark, B. and Boehm, B., 2018. Agile Software Development Cost Modeling for the US
DoD.
16 Schmidt, C., 2016. Agile Software Development. In Agile Software Development Teams (pp. 7-35). Springer, Cham

8
PROJECT MANAGEMENT
goal of crystal clear is to provide idea regarding the main roles of various aspect like designer program,
user and lastly response. The whole sub roles have been designed in such a way various kind of expert of
business and gathering of requirement17. The roles are mainly introduced in crystal clear. It aims to
provide a wide range of ultimate role which is needed for having technology, function and another kind
of infrastructure. The given terms can be classified as cross-functional group which comes up with
various kind of roles.
Feature Driven Development
FDD stands for feature-driven development is known to be a well-known adaptive model which
is needed for development of the system18. FDD approach does not cover the entire development
method for software but rather than it focusses on two phases that are building and design. This
particular approach has been designed in such a way that it can easily work with various activities of
software development project. It does not require any kind of particular or specific model. FDD
approach comes up with proper kind of practices which is known to be effective in nature. It focuses on
certain quality of aspect which is needed in various kind of roles and models which comes up with
deliveries which are tangible in nature. It is mainly used for keeping a track about the progress of the
project19. FDD comes up with mainly five stages which are helpful technique which is needed by project
17 Silva, F.S., Soares, F.S.F., Peres, A.L., de Azevedo, I.M., Vasconcelos, A.P.L., Kamei, F.K. and de Lemos Meira, S.R.,
2015. Using CMMI together with agile software development: A systematic review. Information and Software
Technology, 58, pp.20-43.
18 Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint arXiv:1409.6600.
19 Usman, M., Mendes, E., Weidt, F. and Britto, R., 2014, September. Effort estimation in agile software
development: a systematic literature review. In Proceedings of the 10th International Conference on Predictive
Models in Software Engineering (pp. 82-91). ACM.

9
PROJECT MANAGEMENT
manager. FDD comes up with certain number of roles and responsibility which is required in the given
project. It comes up with certain number of best practices and developer which aim in selecting the best
kind of practices.
Rational methods
Rational Unified Process or RUP is known to be iterative process which is needed by various
object-oriented system. It makes of various kind of modeling requirements which is needed by various
foundation system. RUP is very inclined towards the development of object-oriented. It does not make
implicitly rule out of another one which is given. The duration of iteration is not constant 20. RUP comes
up with activity driven so that there can be role for each can every activity. Configuration within the
given exception of provided roles can be easily defined in both environment workflow and process of
business modeling. The total lifespan of RUP project comes up with four phases that is Inception,
Elaboration, Construction and lastly iteration. These particular phases are split up into various kind of
iteration. It comes up with notion of producing giving desirable amount of software which requires a
considerable amount of software. The total duration of the given iteration can easily vary from two
weeks to even six months.
In the inception phase, the given life-cycle notion of the projects is provided to each and every
stakeholder21. This particular entails the establishment of boundaries, scope and acceptance criteria of
20 van Kelle, E., van der Wijst, P., Plaat, A. and Visser, J., 2015, May. An empirical study into social success factors
for agile software development. In Proceedings of the Eighth International Workshop on Cooperative and Human
Aspects of Software Engineering (pp. 77-80). IEEE Press.
21 Yamato, Y., Katsuragi, S., Nagao, S. and Miura, N., 2015. Software maintenance evaluation of agile software
development method based on OpenStack. IEICE TRANSACTIONS on Information and Systems, 98(7), pp.1377-
1380.

10
PROJECT MANAGEMENT
the given project. In many cases, it is seen that critical use is checked which helps in identifying the
functionality of the given system.
In the elaboration phases, the architecture of the software is provided. The main issues are
checked and analyzed22. The project plan is defined in the given phase which helps in having a proper
kind of overview of the given project. RUP makes assumption in the collaboration phase which helps in
analyzing the various aspects in the elaboration phase. After this particular phase it can be assumed that
most of the given case and actors have bene properly identified and described by the help of network
architecture. At the end of the elaboration phase, a proper kind of analysis needs to be done for
understanding the given risk. Both the aspect that is architecture stability and expansion of resources
needs to be done in elaboration phase.
Dynamic development methods
Dynamic development method is considered to be one of rapid framework which is needed for
rapid application. DSDM is considered to be as a non-profit and non-proprietary framework which is
needed for RAD development. The whole idea is behind the DSDM is instead of fixing the given amount
for functionality of the product. Proper adjustment needs to be done with respect to time and resource
for each of the given functionality. DSDM comes up with mainly five kind of phases that is model of
functional iteration, iteration for design and build and lastly implementation. Approach of DSDM comes
up with various kind of iteration in the form of time boxes. The timebox is allowed for each and every
kind of iteration which is taking place. The time allowed for each and every kind of iteration is planned
22 Yamato, Y., Shigematsu, N. and Miura, N., 2014. Evaluation of agile software develeopment method for carrier
cloud service platform development. IEICE TRANSACTIONS on Information and Systems, 97(11), pp.2959-2962.

11
PROJECT MANAGEMENT
at an earlier stage. In DSDM is known to be typical kind of timebox duration which ranges from few days
to few weeks.
Feasibility study can be considered to be most suitable for the project to be accessed easily.
With the help of proper judging, a proper kind of decision can be done or not. Two kinds of product is
prepared that is a report for feasibility and a proper kind of outline plan for feasibility.
Adaptive software development
ASD stands for Adaptive software development mainly emphasize on various kind of problem
which is encountered during development of complex and large system. The method is considered to be
best for increasing the iterative development and along with prototyping23. ASD project is mainly
developed with the help of three phases that speculates, learn and lastly collaboration. The phases are
named in such a way that they can emphasize on various kind of roles which is needed for changing the
whole method. Speculation is used instead of planning a given plan. It is mainly for highlighting the need
of team which is needed for development of high change system.
Open source software development
The combination of various invention of the given bulletin system and old method of software
development aims to share code among the colleagues24. The whole development process has created
novel development paradigm for offering of OSS which tends to work in innovative way for production
of various software. OSS model aims to work like source code which is needed for modification and
distribution of any kind of charges. The following factors are considered to be important for
understanding the motivation and drivers for development of OSS development that is Technological,
economical and lastly socio-political.
23 Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint arXiv:1409.6600.
24

12
PROJECT MANAGEMENT
The effect of network is considered to be one of crucial factor for the success at the time of OSS
development25. New kind of prototypes needs to be placed in the net. Various organization around the
globe are studying on the various effects of new kind of business models. It can be easily bought out due
to new kind of effects of business models. It is mainly done by new kind of business model which is
bought with the help of OSS production of software.
Pragmatic programming
Pragmatic programming is considered to be misleading as there is no such kind of method.
Instead of that set of programming best practices is needed26. The ultimate reason behind the including
of programmatic does not come up with any kind of process, phases and lastly distinct roles involved in
various work products. From the point of view of agile, the most vital aspect is to focus on increasing the
incremental development, testing on rigorous basis and lastly user-centered design. This particular
approach is considered to be most suitable one for standpoint of practical approach. It comes up from
the point of view of both positive and negative. A certain amount of effort is being applied to explain the
how the design and software implementation can be done in much better way27. There is large number
25 Usman, M., Mendes, E., Weidt, F. and Britto, R., 2014, September. Effort estimation in agile software
development: a systematic literature review. In Proceedings of the 10th International Conference on Predictive
Models in Software Engineering (pp. 82-91). ACM.
26 van Kelle, E., van der Wijst, P., Plaat, A. and Visser, J., 2015, May. An empirical study into social success factors
for agile software development. In Proceedings of the Eighth International Workshop on Cooperative and Human
Aspects of Software Engineering (pp. 77-80). IEEE Press.
27 Yamato, Y., Katsuragi, S., Nagao, S. and Miura, N., 2015. Software maintenance evaluation of agile software
development method based on OpenStack. IEICE TRANSACTIONS on Information and Systems, 98(7), pp.1377-
1380.

13
PROJECT MANAGEMENT
of solution for understanding the software without any certain number of changes. There are large
number of solution is being offered for understanding the changes and refactoring of the given solution.
The method of pragmatic programming is required for having a proper kind of test code which is
implemented on the side of the actual code. All the given testing which is carried out is considered to be
automatic in nature. Automatization aims in encouraging various kind of programmatic programmers to
carry out the given task. Spanning slightly focus on some of the fewer pages which are needed for need
and all the things in specific level.
Conclusion
From the above pages of the report, it can be easily stated that this report is all about agile
methodology of project management. The report highlights some of the traditional plan based software
which is not in practice now. Various kind of traditional methodologies is being used in details. So as a
result, various kind of industry developers is developing at a rapid rate so that new kind of solution is
difficult to grasp and remain unused. Agile software methodology comes up with certain number of
methods which can be used for official methods. Agile methods aim to provide large number emphasis
on proper publication of agile manifesto. Certain number of attempts are being used for emphasizing on
various aspects like software working, interaction and collaboration with large number of customers. A
large number of methods are being used for understanding new kind of methodologies which is needed
for agile principles. A large number of technologies related to new methodologies are coming into action
due to various principles related to agile methodology. Agile comes up with people-centric view which is
needed for software development. It is considered to be as one of the important sources for various
kind of competitive advantage. It highlights on the factors of new kind of product development which
comes up with human strategies which are difficult for imitating.

14
PROJECT MANAGEMENT

15
PROJECT MANAGEMENT
Bibliography
Anslow, C. and Maurer, F., 2015, February. An experience report at teaching a group based agile
software development project course. In Proceedings of the 46th ACM Technical Symposium on
Computer Science Education (pp. 500-505). ACM.
Baca, D., Boldt, M., Carlsson, B. and Jacobsson, A., 2015, August. A novel security-enhanced agile
software development process applied in an industrial setting. In Availability, Reliability and Security
(ARES), 2015 10th International Conference on (pp. 11-19). IEEE.
Brhel, M., Meth, H., Maedche, A. and Werder, K., 2015. Exploring principles of user-centered agile
software development: A literature review. Information and Software Technology, 61, pp.163-181.
Conforto, E.C., Salum, F., Amaral, D.C., da Silva, S.L. and de Almeida, L.F.M., 2014. Can agile project
management be adopted by industries other than software development?. Project Management
Journal, 45(3), pp.21-34.
Dingsøyr, T. and Moe, N.B., 2014, May. Towards principles of large-scale agile development.
In International Conference on Agile Software Development (pp. 1-8). Springer, Cham.
Dingsøyr, T., Fægri, T.E. and Itkonen, J., 2014, December. What is large in large-scale? A taxonomy of
scale for agile software development. In International Conference on Product-Focused Software Process
Improvement (pp. 273-276). Springer, Cham.
Ghobadi, S. and Mathiassen, L., 2016. A model for assessing and mitigating knowledge sharing risks in
agile software development. Information Systems Journal, pp.1-33.

16
PROJECT MANAGEMENT
Heikkilä, V.T., Damian, D., Lassenius, C. and Paasivaara, M., 2015, August. A mapping study on
requirements engineering in agile software development. In Software Engineering and Advanced
Applications (SEAA), 2015 41st Euromicro Conference on (pp. 199-207). IEEE.
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software Engineering Notes, 40(1),
pp.1-6.
Mc Hugh, M., McCaffery, F. and Casey, V., 2017. Barriers to using agile software development practices
within the medical device industry.
Mc Hugh, M., McCaffery, F. and Casey, V., 2017. Integrating agile practices with plan-driven medical
device software development.
Moran, A., 2014. Agile Software Development. In Agile Risk Management (pp. 1-16). Springer, Cham.
Ouriques, R.A.B., Wnuk, K., Gorschek, T. and Svensson, R.B., 2018. Knowledge Management Strategies
and Processes in Agile Software Development: A Systematic Literature Review. arXiv preprint
arXiv:1807.04962.
Papadopoulos, G., 2015. Moving from traditional to agile software development methodologies also on
large, distributed projects. Procedia-Social and Behavioral Sciences, 175, pp.455-463.
Rai, A.K., Agrawal, S. and KHALIQ, E., 2017. Identification of Agile Software Risk Indicators and Evaluation
of Agile Software Development Project Risk Occurrence Probability. International Journal of Engineering
Technology, Management and Applied Sciences, 5(7), pp.403-408.
Rosa, W., Madachy, R., Clark, B. and Boehm, B., 2018. Agile Software Development Cost Modeling for
the US DoD.

17
PROJECT MANAGEMENT
Schmidt, C., 2016. Agile Software Development. In Agile Software Development Teams (pp. 7-35).
Springer, Cham.
Silva, F.S., Soares, F.S.F., Peres, A.L., de Azevedo, I.M., Vasconcelos, A.P.L., Kamei, F.K. and de Lemos
Meira, S.R., 2015. Using CMMI together with agile software development: A systematic
review. Information and Software Technology, 58, pp.20-43.
Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint
arXiv:1409.6600.
Usman, M., Mendes, E., Weidt, F. and Britto, R., 2014, September. Effort estimation in agile software
development: a systematic literature review. In Proceedings of the 10th International Conference on
Predictive Models in Software Engineering (pp. 82-91). ACM.
van Kelle, E., van der Wijst, P., Plaat, A. and Visser, J., 2015, May. An empirical study into social success
factors for agile software development. In Proceedings of the Eighth International Workshop on
Cooperative and Human Aspects of Software Engineering (pp. 77-80). IEEE Press.
Yamato, Y., Katsuragi, S., Nagao, S. and Miura, N., 2015. Software maintenance evaluation of agile
software development method based on OpenStack. IEICE TRANSACTIONS on Information and
Systems, 98(7), pp.1377-1380.
Yamato, Y., Shigematsu, N. and Miura, N., 2014. Evaluation of agile software develeopment method for
carrier cloud service platform development. IEICE TRANSACTIONS on Information and Systems, 97(11),
pp.2959-2962.