www.studymafia.

org

Seminar report

On

Agile Methodology
Submitted in partial fulfillment of the requirement for the award of degree
of CSE

SUBMITTED TO: SUBMITTED BY:

www.studymafia.org www.studymafia.org
 www.studymafia.org

Acknowledgement
I would like to thank respected Mr…….. and Mr. ……..for giving me such a wonderful
opportunity to expand my knowledge for my own branch and giving me guidelines to present a
seminar report. It helped me a lot to realize of what we study for.

Secondly, I would like to thank my parents who patiently helped me as i went through my work
and helped to modify and eliminate some of the irrelevant or un-necessary stuffs.

Thirdly, I would like to thank my friends who helped me to make my work more organized and
well-stacked till the end.

Next, I would thank Microsoft for developing such a wonderful tool like MS Word. It helped my
work a lot to remain error-free.

Last but clearly not the least, I would thank The Almighty for giving me strength to complete my
report on time.
 www.studymafia.org

Preface
I have made this report file on the topic Agile Methodology; I have tried my best to elucidate all
the relevant detail to the topic to be included in the report. While in the beginning I have tried to
give a general view about this topic.

My efforts and wholehearted co-corporation of each and everyone has ended on a successful
note. I express my sincere gratitude to …………..who assisting me throughout the preparation of
this topic. I thank him for providing me the reinforcement, confidence and most importantly the
track for the topic whenever I needed it.
 www.studymafia.org

Introduction
Agile software development methodology is an process for developing software (like other
software development methodologies – Waterfall model, V-Model, Iterative model etc.)
However, Agile methodology differs significantly from other methodologies. In English, Agile
means ‘ability to move quickly and easily’ and responding swiftly to change – this is a key
aspect of Agile software development as well.

What is Agile Methodology?

Agile methodology can be defined as the process to develop software such as V-Model, Iterative
Model, Waterfall Model, etc. It is basically a set of methods and practices that are based on the
principles and values expressed in the Agile Manifesto. The whole process depends upon the
coordination between the teams for proper utilization of the appropriate practices.

All the agile models come with iterations or Sprints that are much shorter in duration varying
from two weeks to two months. During this period, the pre-determined features are delivered.
The Agile models generally have one or more iterations and deliver the entire project at the end
of the last iteration. All the feature in the agile way of working are completed in terms of
development, testing, design and rework prior to the end of the process. All the work is
performed in the single phase.
 www.studymafia.org

Example of Agile Software Development

Example: Google is working on project to come up with a competing product for MS Word, that
provides all the features provided by MS Word and any other features requested by the
marketing team. The final product needs to be ready in 10 months of time. Let us see how this
project is executed in traditional and Agile methodologies.

In traditional Waterfall model –

 At a high level, the project teams would spend 15% of their time on gathering
requirements and analysis (1.5 months)
 20% of their time on design (2 months)
 40% on coding (4 months) and unit testing
 20% on System and Integration testing (2 months).
 At the end of this cycle, the project may also have 2 weeks of User Acceptance testing by
marketing teams.
 In this approach, the customer does not get to see the end product until the end of the
project, when it becomes too late to make significant changes.

The image below shows how these activities align with the project schedule in traditional
software development.
 www.studymafia.org

With Agile development methodology –

 In the Agile methodology, each project is broken up into several ‘Iterations’.

 All Iterations should be of the same time duration (between 2 to 8 weeks).
 At the end of each iteration, a working product should be delivered.
 In simple terms, in the Agile approach the project will be broken up into 10 releases
(assuming each iteration is set to last 4 weeks).
 Rather than spending 1.5 months on requirements gathering, in Agile software
development, the team will decide the basic core features that are required in the product
and decide which of these features can be developed in the first iteration.
 Any remaining features that cannot be delivered in the first iteration will be taken up in
the next iteration or subsequent iterations, based on priority.
 At the end of the first iterations, the team will deliver a working software with the
features that were finalized for that iteration.
 There will be 10 iterations and at the end of each iteration the customer is delivered a
working software that is incrementally enhanced and updated with the features that were
shortlisted for that iteration.

The iteration cycle of an Agile project is shown in the image below.

 www.studymafia.org

This approach allows the customer to interact and work with functioning software at the end of
each iteration and provide feedback on it. This approach allows teams to take up changes more
easily and make course corrections if needed. In the Agile approach, software is developed and
released incrementally in the iterations. An example of how software may evolve through
iterations is shown in the image below.
 www.studymafia.org

Agile methodology gives more importance to collaboration within the team, collaboration with
the customer, responding to change and delivering working software.

Agile development has become common place in IT industry. In a recent survey over 52% of
respondents said that their company practiced Agile development in one form or another.
Irrespective of your role in the organization, it has become essential to understand how Agile
development works and how it differs from other forms of software development.

In traditional approach each job function does its job and hands over to the next job function.
The previous job functions have to signoff before it is handed over the next job function
authenticating that the job is full and complete in all aspects. For example, Requirement
gathering is completed and handed over to design phase and it is subsequently handed over to
development and later to testing and rework. Each job function is a phase by itself.

In Agile way of working, each feature is completed in terms of design, development, code,
testing and rework, before the feature is called done. There are no separate phases and all the
work is done in single phase only.
 www.studymafia.org

Difference between Agile model and Non-Agile models

Parameters Agile Model Non-Agile Models
Approach of this methodology This methodology is very This methodology is not as
flexible and adjustable and can flexible as Agile model and it’s
adapt to the project needs. tough to accommodate changes
in the project.
Measurement of Success The success of the project in In this methodology the success
Agile model is measured by the of the project is measured by
Business value delivered. the Conformation to plan.
Size of the Project The Project size is usually The project size is Large in
small in Agile model. However non- Agile models.
larger projects can also be
handled using the Scaled Agile
Framework (SAFe).
Style of Management The style of management in The management style in the
Agile model is not centralized. non-Agile models is dictatorial.
It is distributed among the team Only one person is the decision
members. maker and rest of the people
follows him.
Ability to adapt to change In Agile model the changes are But in non-Agile models the
accepted and adapted as per the changes are not accepted easily
project needs. in the later stages of the
development.
Documentation required Less documentation is required More documentation is required
in Agile. in non-Agile models.
Importance of In Agile model more emphasis In non-Agile models the more
is given to the people that importance is given to the
means it’s People- Oriented. process hence it’s Process-
Oreinted.
Cycles or iterations Agile methodology has many But, in Non-Agile methodology
cycles or iterations which is the cycles are limited.
also known as Sprints.
Planning in Advance There is minimal upfront In Non-Agile models the
planning in Agile methodology. planning should be complete
before the development starts.
Revenue In Agile method the return on In non-Agile methods the return
investment is early in the on investment is at the end of
project cycle. the project.
Size of the team The size of the team in Agile But in Non-Agile models the
methodology is usually small team size is large.
and creative.
 www.studymafia.org

When to use Agile and Non-Agile models

Project Attributes Agile Model Non-Agile Model
Requirement of the Project Requirements in Agile model In Non-Agile models the
can change as per the customer requirements are very clear
requirement. Sometimes before entering into the
requirements are not very clear. development phases. Any
change in the requirement is not
easily accepted during the
development phases.
Size of the Project The Project size is small in But in Non-Agile models the
Agile model hence small team Project size is usually big hence
is required. big team is required.
Design of the Project In Agile model the architecture In Non-Agile models the
is made as per the current architecture is made as per the
requirements but is designed to current requirements as well as
be flexible. for future requirements.
Planning and Control of the In Agile model the planning of But in Non-Agile models the
Project the project is Internalized and plans are documented properly
has qualitative control. and have quantitative control.
Type of Customers Agile methodology is followed In Non-Agile models the
by the collaborated, dedicated customers are of Contract
collated and knowledgeable provisions.
customers.
Developers required In Agile model the developers In Non-Agile models the
should be knowledgeable, developers should be more Plan
analytically strong, collated and Oriented.
collaborative.
Refactoring In Agile model refactoring is But in Non-Agile models the
not costly. refactoring is very costly.
Risks involved Usually in Agile models the In Non-Agile models the risks
chances of occurrence of are understood clearly and the
unknown risks are more which impact of the risk in the project
can have major impact in the is very less.
project.
 www.studymafia.org

Advantages of Agile Methodology

 In Agile methodology the delivery of software is unremitting.
 The customers are satisfied because after every Sprint working feature of the software is
delivered to them.
 Customers can have a look of the working feature which fulfilled their expectations.
 If the customers has any feedback or any change in the feature then it can be
accommodated in the current release of the product.
 In Agile methodology the daily interactions are required between the business people and
the developers.
 In this methodology attention is paid to the good design of the product.
 Changes in the requirements are accepted even in the later stages of the development.

Disadvantages of the Agile Methodology

 In Agile methodology the documentation is less.
 Sometimes in Agile methodology the requirement is not very clear hence it’s difficult to
predict the expected result.
 In few of the projects at the starting of the software development life cycle it’s difficult to
estimate the actual effort required.
 The projects following the Agile methodology may have to face some unknown risks
which can affect the development of the project.

Conclusion
Presently, the agile methodology is more commonly used in the IT industry. As per the recent
survey, the respondents of more than 50% companies practiced the Agile development. No
matter what role it played in the industry, there is a need to understand its working and how it is
different from other methods of software development.

REFERENCES

1. www.google.com
2. www.wikipedia.org
3. www.studymafia.org
4. www.pptplanet.com