TABLE OF CONTENT:

1. Introduction
Agile project management is an iterative approach to
delivering a project throughout its life cycle.
Iterative or agile life cycles are composed of
several iterations or incremental steps towards the
completion of a project. Iterative approaches are frequently
used in software development projects to promote velocity
and adaptability since the benefit of iteration is that you can
adjust as you go along rather than following a linear path.

One of the aims of an agile or iterative approach is to release

benefits throughout the process rather than only at the end. At
the core, agile projects should exhibit central values and
behaviours of trust, flexibility, empowerment and collaboration

2. Rational

We need agile project management because it helps us focus

on what matters. Becoming more agile through organisations
and team’s brings flexibility to change and allows us to deliver
value often with continuous feedback.

The goal is not to ‘be agile’ the goal is to improve. With an

incremental and iterative approach, we increase predictability
and control risk

3. Objectives
The agile management philosophy concentrates on
empowered people and their interactions, and early and
constant delivery of value into an enterprise.

Iterative or agile project management focuses on delivering

maximum value against business priorities in the time and
budget allowed, especially when the drive to deliver is greater
than the risk. Some agile principles include:
 The project breaks a requirement into smaller pieces, which
are then prioritized by the team in terms of importance.
The agile project promotes collaborative working, especially
with the customer.
The agile project reflects, learns and adjusts at regular
intervals to ensure that the customer is always satisfied and is
provided with outcomes that result in benefits.
Agile methods integrate planning with execution, allowing an
organization to create a working mindset that helps a team
respond effectively to changing requirements

4. Research Methodology
Agile methodology is a project management approach that
prioritizes cross-functional collaboration and continuous
improvement. It divides projects into smaller phases and
guides teams through cycles of planning, execution, and
evaluation.

 Agile methodology basics

Agile is a project management approach developed as a more
flexible and efficient way to get products to market. The word
‘agile’ refers to the ability to move quickly and easily.
Therefore, an Agile approach enables project teams to adapt
faster and easier compared to other project methodologies.
 What is Agile methodology?
Agile methodology is an approach to project management that
uses four values and 12 principles to organize projects.
The four values of the Agile Manifesto are:
i) Individuals and interactions over processes and tools.
ii) Working software over comprehensive documentation.
iii) Customer collaboration over contract negotiation.
iv)Responding to change over following a plan.

The Agile method works in ongoing sprints of project planning

and execution, enabling you to continuously adapt and mature
your plan, scope, and design throughout the project.
Agile projects require an iterative approach, which supports
incremental, frequent, and consistent delivery of workable
products to your customer or client. This innovative approach
ensures your project team can consistently deliver concrete
products without being delayed by changes and evolving
requirements.

Agile has a high level of customer involvement and includes

frequent reviews of progress with both the project team and
the customer.
You can run an Agile project using several different
frameworks. Some of the more popular ones include:

 Scrum
 Kanban
 Extreme Programming
 DSDM

 The 12 Agile principles

The Manifesto for Agile Software Development outlines 12

Agile principles that all projects should follow. These are:

i) Our highest priority is to satisfy the customer through early and

continuous delivery of valuable software. The first principle of Agile
methodology states that customers should receive project
deliverables or iterations across regular intervals throughout the
project’s life cycle, rather than just one product delivery at the
end.
ii) Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage. The Manifesto’s authors found that, with
traditional project management, it was difficult to
accommodate last-minute change requests. This principle
ensures that Agile projects can adapt to any changes, no
matter how late in the game, with minimal delay.
iii) Deliver working software frequently, from a couple of weeks
to a couple of months, with a preference for shorter
timescales. Agile projects plan for frequent, short project timelines
that allow for a fast turnaround of workable products. Teams will
often break Agile projects into one to four week-long sprints or
project intervals, each one ending in the delivery of a product.
iv) Business people and developers must work together daily
throughout the project. This Agile principle states that regular
communication with all stakeholders is critical to the project’s
success. Commonly, this involves a short daily meeting with both
the project team and any other key stakeholders.
v) Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get
 the job done. A central concept of the Agile project management
methodology is that the right people need to be placed in the right
positions and given the autonomy required to do their jobs well. It’s
essential to design a project team based on capabilities rather than
job positions or titles. The project manager’s focus should be on
motivating the project team and supporting them, rather than
micromanaging them.
vi) The most efficient and effective method of conveying
information to and within a development team is face-to-
face conversation. The Agile Manifesto emphasizes the
importance of co-locating teams and stakeholders whenever
possible, as face-to-face communication is more effective than
email or phone. If your team cannot be co-located, video
conferencing is an option that can still capture the value of non-
verbal cues.
vii) Working software is the primary measure of progress.The
Agile methodology aims to provide complete, working deliverables.
This goal should always take priority over any additional
requirements, such as project documentation. Other metrics, such
as hours spent or time elapsed, are not considered as important as
delivering working products.
viii) Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain
a constant pace indefinitely. According to this principle, Agile
projects should have a consistent pace for each iterative cycle or
sprint within the project. This breakdown should eliminate the need
for overtime or crashing schedules while promoting frequent output
of workable products. It should also create a repeatable cycle that
the team can continuously follow for as long as necessary.
 ix) Continuous attention to technical excellence and good
design enhances agility. An Agile project’s primary focus should
be on improving the end product and achieving advancements
consistently over time. Each iteration should always improve on the
previous one, and the team should always be looking to innovate.
x) Simplicity – the art of maximizing the amount of work not
done – is essential. An Agile project aims to get just enough done
to complete the project and meet the requested specifications. Any
additional documentation, steps, processes, or work that does not
add value to the customer or enhance the project outputs should be
avoided or eliminated.
xi) The best architectures, requirements, and designs emerge
from self-organizing teams. Agile is based on the belief that you
need motivated, autonomous, and skilled teams to deliver the best
results and products. Teams should be empowered to organize and
structure themselves as required. They should have the freedom to
collaborate and innovate as they see fit, without being hampered by
too much oversight.
xii) The team discusses how to become more effective at
regular intervals, then tunes and adjusts its behavior
accordingly. A successful, self-motivated team requires a strong
focus on advancing their skills and processes to grow and improve.
The team should have regular reviews on their performance and
outcomes, including discussions on improving as they move
forward.

5. Limitation of the Proposal Project

Agile development aims to support early and quick development of
working code that meets the needs of the customer. Agile supporters
claim that code is the only deliverable that matters, whereas, agile
opponents found that emphasis on code will lead to memory loss,
because the amount of documentation and modeling done is not
enough [1]. There are some limitations to apply agile methodologies
[1].

First limitation of Agile methodologies is that it is not suitable for

maintenance, since there is not much documentation for the system.
Developers are not concentrating on the documentation as much
because the primary goal when using an Agile Methodology is to write
software not documentation.[20] Another limitation is that Agile
Methodologies depend heavily on the user involvement, and thus, the
success of the project will depend on the cooperation and
communication of the user. Another limitation is that agile
methodologies concentrate work quality on the skills and behaviors of
the developers, as the design of the modules and sub-modules are
created mainly by single developer. This is because they focus on
building systems that solve specific problems, and not the general
ones. Agile methodologies work best for teams with relatively small
number of members (no less than 3 and no more than 9) [23], and
hence, they will not work well for teams with large number of
members.

To get the advantages of applying agile methodologies in the

development, there is a set of assumptions that are assumed to be
true. To mention some are: cooperation and face to face relation
between the customers and the development team; evolving and
changing requirements of the project; developers having good
individual skills and experiences; in addition to many more [1]. If these
assumptions cannot be met, it may be better to go with a different
methodology for better project outcome.