THE AGILE MANAGEMENT

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

1AGILE MANAGEMENT
Executive Summary
The agile approach of project management describes an innovative approach to plan and handle
multiple software projects. Software projects can be describes as the group of operations
conducted to gain an identifiable result of value. The project members frequently faces numerous
issues while this type of projects. The management of these software projects requires high
knowledge as well as management skills. In this modern world every industries are using some
enhance project management approaches like waterfall model and agile project management
because they help to put low emphasis on the up – front plans as well as help the project
members to maintain strict controls on their respective software projects. This particular study
describes two project management approach namely waterfall and agile management. The study
also showcases the industrial trends and the methodologies used by them. The study describes
history, success and issues in both the project management approaches.

2AGILE MANAGEMENT
Table of Contents
Executive Summary.............................................................................................................1
Introduction..........................................................................................................................3
Discussion............................................................................................................................3
History of Waterfall and Review.....................................................................................3
Waterfall Issues/Success..................................................................................................7
History of Agile and Review...........................................................................................8
Agile Issues/Success........................................................................................................9
Industrial trends and selection of Methodologies..........................................................12
Conclusion.........................................................................................................................14
Bibliography of Agile Terms.............................................................................................15
APA References.................................................................................................................16

3AGILE MANAGEMENT
Introduction
The method of creating or developing computer programs and software is always directed
by various project management methodologies. The methodologies used in software
development describes a layout which is utilized for planning, handling and controlling all
processes involving in developing the information system or computer software. These software
development methodologies are referred as the SDLC or software Development Life Cycle and
these methodologies are widely used in multiple software engineering as well as industrial
domains (Crawford, 2014). Numerous researchers studied and invented many models of SDLC.
Some reputed SDLC models used are namely, Waterfall model, agile framework, RAD (Rapid
Application Development), Rational Unified Process (RUP) and many more.
This particular report aims at two project methodologies namely, the waterfall model and
the agile methodology. The report describes the history and issues of both the methodologies.
Lastly, the report portrays the methodology usually used by various industries. The agile project
management methodology is discussed in this report which comprises of the agile principles and
the agile development cycle.
Discussion
History of Waterfall and Review
The waterfall model was proposed by Winston W. Royce in the year 1970. He proposed
the model to illustrate some possible software engineering methods. The water fall model of
SDLC is referred as a sequential software development process where the progress is represented
as the flow in downward direction. The flow maintain some phases which are executed for
developing a computer software or information systems (Mishra & Mishra, 2013). These phases

4AGILE MANAGEMENT
are essential to be executed in this model because the information system can be developed only
after the execution of these phases. Each of the phase is executed one after another. Each phase
is completed before the next phase starts and the phases do not overlap each other. It was first
model that was utilized for the software development. The life cycles of this model are illustrated
in a general way and thus these models are easily adaptable (Špundak, 2014). The
implementation factors vary as per the software developed.
The phases of waterfall stated and described below:
Requirements: The initial phase of this SDLC model deals with determining the project
requirements. This is referred as one of the critical phase of the waterfall model. In this phase the
project team and the clients prepare a requirement document where they list all the software they
require for their proposed project or information system. In this phase the project members
determine the limitations and the functionality of all the required software. The requirement
document comprises of all the information required for developing the proposed information
system or project and this document is also known as the SRS (Software Requirement
Specification) (Ebert, 2014). This SRS document is initially endorsed as well as verified by the
clients prior to the starting of the proposed project. This SRS document acts as the input for the
next phases.
Design: The system design is made on the basis of the prepared SRS. This phase deals
with designing the software and hardware where the functionality of both the hardware and
software is separated. The design phase transforms the requirements into a software
representation for accessing quality prior to the generation of the code. Code generation is
referred to the method of converting the design into the machine readable form. The generation
of code is completed easily if the software design is prepared in a simple way. After this, a test

5AGILE MANAGEMENT
plan is produced. This test plan will ensure that the proposed project is ready for the
implementation in various industrial fields or software engineering domains. The test plan is
required in every software projects as it is a vital part of the project which will conclude that the
proposed project is ready to use (Hu et al., 2013). The proposed project is handed or used by the
clients or customers depending on the result of the test plan.
 Implementation and Unit Testing: The software modules are then divided into various
units. These units are logically separable section of software. Thus, testing of these units
become easier method as the testing of these units is done separately. The testing of these
units are conducted by the developer himself or herself. The units are tested to ensure that
there is no defects in the units and can be operated freely and effectively.
System Testing and Integration Phase: In this phase, all units are assembled together to
form a system. These units are assembled on the testing result. If any defect is determined then
the units are excluded. Now, the whole system is tested and is verified that the system meet all
the functional as well as performance requirements of customers (Mahalakshmi & Sundararajan,
2013). The testing of the system is conducted as mentioned in the testing plan. The testing of the
whole system examined the functionality and the efficiency of the system. The implementation
or usage of the system highly depends on the testing result. Thus, a test report is generated in this
phase. The test report also conclude whether the system is ready to implement or not.
 Deployment of the proposed Project or system: After the completion of the functional
and non – functional testing of the whole system the product or the project is deployed in
the real environment or to the customers. The project or the product is provided to the
market and the clients can use the project. The testing plan are also shown to every users

6AGILE MANAGEMENT
such that they can be ensured that the launched product is safe for their environment as
well as can be used safely.
 Maintenance: The product or the project can have some issues in the client’s
environment. The issues are aroused due to some abnormal atmosphere of the client’s
environment. These issues are solved by releasing patches. The developers prepare some
patches for the users such that they can applied to the system and the issues can be solved
out. An outdated version of the system can produce numerous issue to the users.
Maintenance is conducted for making the system better as well as to increase the
efficiency of its functionality.
Figure 1: Phases of Waterfall model

7AGILE MANAGEMENT
(Source: Verma, Bansal & Pandey, 2014)
Waterfall Issues/Success
Waterfall model comprises of numerous advantages. Some of the reputed advantages are as
follows:
1. It allows the project managers with high control and departmentalization. Each stage of
this model can be scheduled with some definite deadline and it is ensured that each of the
stage is completed within the assigned deadline and each stage produced some output.
2. The water fall model is maintained or structured through some easy understandable as
well as explainable phases. This allow both the project members as well as the clients to
develop the project in a more easy and efficient manner.
3. The rigidity of model allow the project managers to manage their software projects
effectively. The rigidity of the model is increased as ever phase of the model comprises
of some definite deliverables as well as review method (Mahadevan, Kettinger &
Meservy, 2015).
4. The phases of the model do not overlap which does not increases the complexity for the
project members.
5. The testing of the system allow the user to trust on the system and also allow them to
easily implement the system in their environment.
However, the waterfall model comprises of some issues too. The major ideas of the
waterfall model are listed below:
1. It is a complex process for the project team to estimate the cost and time for every
phase of waterfall model. Time and cost are the vital constraints for any type of

8AGILE MANAGEMENT
projects. In Waterfall model, it is a complex process or harder to draw an estimation
regarding the time and cost of every phase of the concerned model.
When the application is drawn or put in the testing stage, it become difficult for the
project members to change the previous operations (Edeki, 2015).
2. If an error occurs in the testing phase all the initial phases are to be reviewed which is
complicated process for every project members as well as consume huge time.
3. This model cannot be applied in the object oriented and complex projects.
4. This model can only be applied when the requirements are clear and are easily
available.
History of Agile and Review
Agile project management deals with the iterative as well as incremental approach. In
agile project management an in depth analysis of the projects is not required at the initial phase
of the project rather in agile project management it changes the project methodologies with time
and project requirement. The main aim of each of the iteration is to produce innovative product.
The project management proved as a critical element of any organization’s efficiency as well as
its success. Enhanced project management methodologies are required as the software projects
aim to generate identical service or product within some project constraints or project boundaries
like quality, cost and time (Patwardhan et al., 2016). In the agile software development, the
developers operate as a team to handle or manage clients. The characteristics of every
development cycle of the agile framework are decided jointly by the clients as well as the
developers. The project managers have a vital role in software projects where each and every
decisions are taken carefully and according to the project aims and objectives. Agile
methodology is the method which assists in continuous iteration of the testing and development

9AGILE MANAGEMENT
phases in software development practices. In this methodology, the testing and the development
practices are concurrent to each other. This methodology also allow an enhanced communication
among the developers, testers, managers and customers.
Figure 2: Agile Project Methodology
(Source: Ozawa & Zhang, 2013)
Agile Issues/Success
The continuous changing patterns in the project environment have added to the
difficulties of the project managers. The traditional project management methods put emphasis
on the development of different plans at the same time installing certain control mechanisms to
avoid deviations from the previously made plans. In this scenario agile project management is

10AGILE MANAGEMENT
being used as an alternative to the existing traditional approaches. In agile project management
the project teams make use of flexible as well as iterative approaches to implement projects
which help them in adjusting plans with respect to the changes in project environment (Banica et
al., 2017). The main advantage of agile project management technique is flexibility and
flexibility is ensured in the agile methodology by inculcating three main factors that are
embracing changes, reflecting as well as learning in a continuous manner and delivering a part of
the functionality incrementally. The agile principles in industries discourage usage of various
bureaucratic processes of managing projects and instead of these the teams are encouraged to
make use of short as well as incremental cycles at time of project implementation. These
methodologies help in reviewing completed cycles, drawing lessons for the betterment of
subsequent cycles.
The agile project management methodology divides the whole project into several
sprints and each of the divided sprints adds some sort of value to the previous one. Designs of
the project can be improvised on a frequent basis as per the lessons obtained from the previous
sprint and feedbacks obtained from the stakeholders of the project (Eason, 2016). In the agile
project methodology, the project head is responsible for providing directions, establishing
specific rules at the same time facilitating collaboration in between the project team and the
project stakeholders. Agile project management in case of industries relies upon informal as well
as flat organizational structures thereby enhancing the responsiveness along with flexibility of
the projects to the modifications in the environment. The other main or major feature of agile is
that it is defined by the high level of involvement of the project stakeholders in the domain of
project development and the process of implementation. The involvement of the stakeholders in
the project helps in making improvisations as per requirements and necessities of the

11AGILE MANAGEMENT
stakeholders so that they are satisfied with the end project result (Reddy, 2015). The agile project
management methodology has a lot to do in the industry sector as industries mainly deal with
products thus high level of stakeholder involvement will help in understanding the requirements
of the clients and the products can customize accordingly. The agile methodology considers the
fact that there can be some requirements which might be missed at the planning stage thus giving
scope to the users to accommodate new requirements along with new changes to the existing
requirements at all phases of a project (Thakurta, 2013). The industries can be benefitted from
agile methodology as in this methodology customer satisfaction is given the utmost priority. The
agile methodology in industries can help reduce costs by effectively eliminating the costly
changes and associated reworks in the projects.
There are many challenges in the agile methodology as well and one of the major
challenges is difficulty in project scheduling that is scheduling the various tasks in a project. In
case of agile methodology the specifications are defined for individual sprints and do not
consider the whole project thus making it difficult for the project managers to estimate the
duration of the project. This generally has a significant impact on the ongoing work of the
project. The time duration that a project requires to get completed is considered to be one of the
major constraints in project management and thus this can affect the project in an adverse way
(Mahalakshmi & Sundararajan, 2013). If the project team is unable to come up with accurate
schedules then it can have drastic effect on the project proceedings. Agile project management
throws a challenge as far as knowledge management is concerned. Agile project management
discourage structured forms of communications as well as decision making that can sometimes
be a problem in case of complex projects. In agile project management knowledge is tacit at the
same time being undocumented is considered as being involved in frequent shifting of power

12AGILE MANAGEMENT
from the hands of the management to the team implementing the same. The other disadvantage
of agile project management is that it focuses on people rather than on process or plans. The
successful implementation of the project depends on collaboration, cooperation and
communication in between the project team members and the stakeholders (Stoica et al., 2016).
Industrial trends and selection of Methodologies
There are various agile methodologies used by the industries. Some of them are:
 Scrum: Scrum is the agile development methodology that focuses especially on the
management of the project operations within the team based environment. The scrum
methodology comprises of three basic roles namely, scrum master, scrum team and
product owner. Each of the iteration in the scrum is known as the sprint. In each sprint
the top users of the product backlog are selected and then they are turned in the sprint
backlog (Opelt & Mittermayr, 2013). The project team operates on the basis of some
specific sprint backlog. The team also verifies the daily operation.
Figure 3: Whole Scrum Process
(Source: Demirtas, Tuzkaya & Seker, 2014)

13AGILE MANAGEMENT
 Crystal Methodologies: This methodology is based on three different concepts
chartering, cyclic delivery and wrap up (Stellman & Greene, 2014).
 DSDM (Dynamic Software Development Method): Dynamic Software Development
Method is the RAD (Rapid Application Development) approach used in the software
engineering which helps to deliver the agile project delivery framework. Here all the
users are to be involved solely as well as they have to perform some specific and
respective operations.
 FDD (Feature Driven Development): The Feature Driven Development describes
numerous short and specific phases of project operations which include domain
walkthrough, promote to build, design inspection and code design and inspection
(Kruchten, 2013).
 Lean Software Development: This methodology is based on the principle of “Just in time
production”. It focuses in increasing speed of production with the time. It comprises of
seven phases namely, Early delivery, Amplifying learning, Eliminating Waste, Defer
commitment, Empowering the team, Optimize the whole and Building Integrity
(Špundak, 2014).
 Extreme Programming: This agile methodology is highly applicable where the project
requirements frequently changes or the user changes their requirements frequently
(Kushleyev et al., 2013). The business requirements are collected as stories and these
stories are loaded in some definite place known as the parking lot. Extreme programming
comprises of six phases planning, analysis, design, execution, wrapping and closure.

14AGILE MANAGEMENT
Figure 4 : XP phases
(Sources: Rigby, Sutherland & Takeuchi 2016)
Conclusion
Therefore, it can be concluded that software project require high skills of both knowledge
and management. The discussed project management methodologies helped numerous software
project managers to lead their software projects in an easier manner. Agile project management
deals with the iterative as well as incremental approach. In agile project management an in depth
analysis of the projects is not required at the initial phase of the project rather in agile project
management it changes the project methodologies with time and project requirement. The main
aim of each of the iteration is to produce innovative product. The project members frequently
faces numerous issues while this type of projects. The management of these software projects
requires high knowledge as well as management skills. In this modern world every industries are

15AGILE MANAGEMENT
using some enhance project management approaches like waterfall model and agile project
management because they help to put low emphasis on the up – front plans as well as help the
project members to maintain strict controls on their respective software projects.
Bibliography of Agile Terms
DSDM (Dynamic Software Development Method): Dynamic Software Development
Method is the RAD (Rapid Application Development) approach used in the software engineering
which helps to deliver the agile project delivery framework
FDD (Feature Driven Development): The Feature Driven Development describes
numerous short and specific phases of project operations which include domain walkthrough,
promote to build, design inspection and code design and inspection
Crystal Methodologies: This methodology is based on three different concepts chartering,
cyclic delivery and wrap up
Scrum: Scrum is the agile development methodology that focuses especially on the
management of the project operations within the team based environment. The scrum
methodology comprises of three basic roles namely, scrum master, scrum team and product
owner
Extreme Programming: This agile methodology is highly applicable where the project
requirements frequently changes or the user changes their requirements frequently

16AGILE MANAGEMENT
APA References
Banica, L., Radulescu, M., Rosca, D., & Hagiu, A. (2017). Is DevOps another Project
Management Methodology?. Informatica Economica, 21(3), 39.\
Crawford, J. K. (2014). Project management maturity model. Auerbach Publications.
Demirtas, N., Tuzkaya, U. R., & Seker, S. (2014, July). Project management methodology
selection using SWOT-fuzzy AHP. In Proceedings of the World Congress on Engineering,
London, UK (pp. 2-4).
Eason, O. K. (2016). Information Systems Development Methodologies Transitions: An
Analysis of Waterfall to Agile Methodology.
Ebert, C. (2014). Software product management. IEEE Software, 31(3), 21-24.
Edeki, C. (2015). Agile Software Development Methodology. European Journal of Mathematics
and Computer Science Vol, 2(1).
Hu, Y., Zhang, X., Ngai, E. W. T., Cai, R., & Liu, M. (2013). Software project risk analysis
using Bayesian networks with causality constraints. Decision Support Systems, 56, 439-449.
Kruchten, P. (2013). Contextualizing agile software development. Journal of Software: Evolution
and Process, 25(4), 351-361.
Kushleyev, A., Mellinger, D., Powers, C., & Kumar, V. (2013). Towards a swarm of agile micro
quadrotors. Autonomous Robots, 35(4), 287-300.

17AGILE MANAGEMENT
Mahadevan, L., Kettinger, W. J., & Meservy, T. O. (2015). Running on Hybrid: Control Changes
when Introducing an Agile Methodology in a Traditional" Waterfall" System Development
Environment. CAIS, 36, 5.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced Engineering,
3(6), 192-196.
Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A
Comparative Study. International Journal of Emerging Technology and Advanced Engineering,
3(6), 192-196.
Mishra, A., & Mishra, D. (2013). Software project management tools: a brief comparative view.
ACM SIGSOFT Software Engineering Notes, 38(3), 1-4.
Opelt, A., Gloger, B., Pfarl, W., & Mittermayr, R. (2013). Agile contracts: creating and
managing successful projects with Scrum. John Wiley & Sons.
Ozawa, H., & Zhang, L. (2013, August). Adapting agile methodology to overcome social
differences in project members. In 2013 Agile Conference (pp. 82-87). IEEE.
Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Reddy, A. (2015). The Scrumban [r] evolution: getting the most out of Agile, Scrum, and lean
Kanban. Addison-Wesley Professional.
Rigby, D. K., Sutherland, J., & Takeuchi, H. (2016). Embracing agile. Harvard Business Review,
94(5), 40-50.

18AGILE MANAGEMENT
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.
Stellman, A., & Greene, J. (2014). Learning agile: Understanding scrum, XP, lean, and kanban. "
O'Reilly Media, Inc.".
Stoica, M., Ghilic-Micu, B., Mircea, M., & Uscatu, C. (2016). Analyzing Agile Development-
from Waterfall Style to Scrumban. Informatica Economica, 20(4).
Thakurta, R. (2013). Impact of Scope Creep on Software Project Quality. Vilakshan: The XIMB
Journal of Management, 10(1).
Verma, J., Bansal, S., & Pandey, H. (2014). Develop framework for selecting best software
development methodology. International Journal of Scientific & Engineering Research, 5(4).