UNIVERSITY INSTITUTE OF

INFORMATION AND TECHNOLOGY

PANJAB UNIVERSITY
Batch : 2013-2017

Submitted to:
Mrs. Rajni Sobti
Dept. of IT

Submitted By:
Tarun Khampa -UE138091
Tanzin Angmo -UE138089
(Group -1)

Agile: The Business Benefits

AGILE ASSIGNMENT
BUSINESS BENEFITS OF AGILE
REPORT

Agile: The Business Benefits of Agile

Software Development

Agile: The Business Benefits of Agile

Software Development
Your success in life isnt based on your ability to simply change. It is based on
your ability to change faster than your competition, customers and business.
Mark Sanborn
If IT budgets are any indication, most organizations large and small rely heavily on
customized software, and large-scale interconnected systems are now the norm. So how
can an organization changeand change quicklywhen IT systems are large,
interconnected, and based on custom software?
One answer is Agile software development. Agile software development is a family of
methods for developing sophisticated software applications and systems. It emphasizes
simple code, frequent testing, adjusting goals and expectations on an ongoing basis,
delivery of functional pieces early and often (as opposed to a single large release), and
delivering value to the customers.
Done right, Agile software development can replace yearly software releases with
monthlyor even weeklybuild/release cycles.

The Benefits of Agile Software Development.

Any organization needing customized software or large-scale systems can benefit from
Agile development. Utilizing Agile methods allows you to:
Improve Quality. By breaking down a project into manageable units, the
project team may focus on producing and testing high-quality code.
According to the 2011 CHAOS report from the Standish Group:
The agile process is the universal remedy for software
development project failure. Software applications developed
through the agile process have three times the success rate of
the traditional waterfall method and a much lower percentage
of time and cost overruns.Agile: The Business Benefits of
Go to Market More Quickly & Improve ROI. By utilizing Agile
development practices, businesses may free themselves up from being

forced to rely on features and deliverables that were proposed months (or
even years) ago, and adjust and deploy more quickly based on todays
needs. Additionally,
Agile can quickly produce a working version of software, and early deployment
of functional parts means that businesses will begin to see real ROI more
quickly.
Mitigate Risk, and Quickly. Frequent testing and shorter feedback loops mean
that problems may be discovered and addressed more quickly. And functioning
code may continue to operate while issues are being resolved in later additions.
More Easily Manage the Project Scope. Agile development practices
emphasize a list of requirements, with very short development cycles, that
evolves as the project progresses. This flexible process results in predictable
release dates and manageable budgets, and helps prevent development projects
from mushrooming out of control.
Promote Transparency and Improve Decision-Making. Using Agile
development practices, stakeholders have frequent and early opportunities to see
and have a say in what is being developed.

Blasting the Myths About Agile.

Even in light of all its benefits, Agile software development has not been
universally accepted/adopted by organizations as the development methodology of
choice. This is largely due to a number of myths regarding Agile.
Myth No.1: Agile involves little to no planning.

False!

Fact: Agile software development involves extensive planning. Whats

different about Agile is the focus on incremental, adaptive planning. Under
this approach, the project plan is organized into iterations with a time frame
of one to two weeks. Therefore, as requirements and needs change, problems
arise, and new insights emerge, the project can adapt. The Agile manifesto
emphasizes
responding to change over following a plan.
Myth No.2: Agile produces/comes with no documentation. False!
Fact: Documentation is an important part of Agile software development.
The objective and extent of documentation will vary by project, and the

fundamental purpose of documentation remains communication and

achievement of goals.
Myth No.3: Agile only works well for small projects. False!
Fact: While it is true that Agile development practices often emphasize
small, cross-functional teams, Agile practices may be applied and scaled to
projects of any size.
Myth No.4: With Agile, you wont know what youre getting until its done False!
Fact: A key advantage of Agile methodology is the transparency,
communication and interaction it facilitates between decision makers and
developers so there are no surprises when a project is complete.
Deliver the project needed at the end, not the one requested at the beginning.
Jim Highsmith
Under both the traditional waterfall methodology and the Agile methodology, a project
begins with a discovery phase. Under the waterfall method, the requirements and
direction identified in this initial stage will serve as the development roadmap. The
drawback to this approach is that (1) there may be a huge gap between what the decisionmakers/client requested and what was delivered and/or (2) the decision-maker/client may
have simply changed his or her mind during the process.
Agile methodology addresses the issue of undefined/murky or changing requirements by
incorporating ongoing communication and interaction between those who want and those
who do. Because, for most projects, readily accepting change can cost significantly less
time/effort/money than assuming requirements will never change. As Jim Highsmith, one
of the founding members of the Agile Alliance, said: Deliver the project needed at the
end, not the one requested at the beginning.

Is Agile Right for Your Organization?

If you are looking for a software solution for your organization, we encourage you to
consider using the Agile methodology. This is particularly so if (1) the desired solution
cannot be easily articulated or involve a great deal of unknowns (e.g., requirements,
budget, timeline); (2) the project involves a high degree of complexity and may require an
evolutionary feedback process; and/or (3) the desired solution is unique and includes new
or emerging technology or content. Agile should also be considered if time to market is a
great concern.