The document discusses Agile software development. It provides information on what Agile development is, the main phases (requirements planning, design workshop, implementation), and that the process can repeat until customer satisfaction. It notes Agile development allows for rapid development, involvement of customers, and uses tools and teamwork. Benefits include improved quality, opportunities for corrections, customer satisfaction, and faster time to market. However, disadvantages include needing active user involvement throughout and new requirements potentially arising during development.

1. Agile
Development
Agile Software Development Nature of ASDM
Tools
Why this ?Crew ii
@ Dimuth Chathuranga 243~ Piyumika Samarasekara 126 ~ Yohan Gunathilaka 122 ~ Sachith Perera 123 ~ Nayanajith Karunarathna 124
KOTELAWALA DEFENCE UNIVERSITY – INTAKE 30

2. What is Agile Software
Development?
It is a method of Software development
where the problems and answers to a
development is found through
collective, self organizing cross
functioning team members.
Agile
Software
Development
http://en.wikipedia.org/wiki/Agile_software_development

3. Agile
Software
Development
There are three main phases :
 Requirements planning
 Design workshop
 Implementation
There may be several other sub steps to merge to a one.
but mainly there are three steps to follow.
www.mgt.ncu.edu.tw/~ylchen/sasd-slide/chap08.ppt

4. This process can be Repeat until the Customer Satisfaction
ButThere are NoTime toWaste….
We need to hurry!
http://upload.wikimedia.org/wikipedia/commons/thumb/5/53/Rapid_application_software_development.svg/
700px-Rapid_application_software_development.svg.png
Agile
Software
Development

5. Agile Software Development :
 Is a rapid way to develop a computer application.
 Is use to develop both Desktop and web-based
applications
 Is an object development approach
 Is use several tools to implement a good product.
 Is a way which customer also can involve.Nature ofASD
www.mgt.ncu.edu.tw/~ylchen/sasd-slide/chap08.ppt

6.  The concept :
 To more actively involve system users in the
analysis, design and construction activities
 To organize systems development into a series
of focused, intense workshops jointly involving
system owners, users, analysts, designers and
builders
 To accelerate the requirements analysis and
design phases through an iterative construction
approach
 To reduce the amount of time until the users
begin to see a working system
 To use prototypes to their fullest potential
www.mgt.ncu.edu.tw/~ylchen/sasd-slide/chap08.ppt
Nature ofASD

7. www.mgt.ncu.edu.tw/~ylchen/sasd-slide/chap08.ppt
o Resources to develop
o Skilled Developers andTesters
o Teamwork
o Required Developing Software
o Supervised Development
o Proper Planning &
Management
Tools

8. http://www.codeproject.com/Articles/604417/Agile-software-development-methodologies-and-how-t
TEAM WORK
Extreme Programming emphasizes teamwork.
Managers, customers, and developers.They improves a
software project in five essential ways: communication,
simplicity, feedback, respect, and courage.
“As developers we need to remember that XP is not the only
game in town.”- Pete McBreen
Tools

9. WhyThis ?
Benefits:
The Higher traction, because Agile offers,
• Improved quality
• More opportunities for mid-course corrections
• Improved customer or business satisfaction
• Better alignment between business & IT
• Improved time to market.
http://www.codeproject.com/KB/architecture/604417/alert.jpg

10.  The benefits :
 Useful for development where the requirements are
unpredictable
 Increases end-user enthusiasm and visibility due to active
involvement
 Users and management see working, actual solution outputs
rather than conceptual designs more rapidly than in Model-
Driven Development
 Errors and omissions tend to be detected earlier in
prototypes than in system models
 Testing andTraining is a natural by-product of the underlying
prototyping approach
 The iterative approach is more “natural” fit because change
is an expected factor during development
 It reduces risk because you test the technical solution
iteratively instead of making a wholesale commitment to
any solution
WhyThis ?

11. WhyThis ?

12. Disadvantages
 Active user involvement and collective efforts
are required all through out the development
process.
 New requirements may arise or change while the
development is going on.
 Miscommunication between team members
may cause an improperly developed software.
 Because testing is done while developing, the
finished product may have higher chances for
errors.
WhyThis ?

13. Barriers to Further Agile Adoption
WhyThis ?
http://www.codeproject.com/KB/architecture/604417/Barriers.jpg

14. THANK
Y Uo
243,126,122,123,124