0% found this document useful (0 votes)
5 views4 pages

Agile Software Development Techniques

programming technical

Uploaded by

6x49wjk6fm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
5 views4 pages

Agile Software Development Techniques

programming technical

Uploaded by

6x49wjk6fm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Software Development Techniques Atica Altaie

AGILE DEVELOPMENT TECHNIQUE

AGILE::: What it means?


 Agile has become a word describing a modern software process.
 A term used to describe "lightweight" development
 A methodology for iteratively developing products

An agile team is a team able to respond to changes. Changes in the


software being built, changes to the team members, changes because of
new technology, and changes of all kinds that may have an impact on the
product they build. An agile team recognizes that software is developed by
individuals working in teams and that the skills of these people, their
ability to collaborate is at the core for the success of the project.

29
Software Development Techniques Atica Altaie

But agility is more than an effective response to change. It:

 Encourages team structures that make communication (among team


members, between technologists and business people, between software
engineers and their managers) more easy.
 It emphasizes rapid delivery of operational software.
 It adopts the customer as a part of the development team and works to
eliminate the “us and them”.

AGILITY PRINCIPLES:
The Agile Alliance defines 12 agility principles for those who want to
achieve agility:
1. Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
2. Welcome changing requirements, even late in development
3. Deliver working software frequently, from a couple of weeks to a couple
of months.
4. Business people and developers must work together daily throughout the
project.
5. Build projects around motivated individuals. Give them the environment
and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and
within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.

30
Software Development Techniques Atica Altaie

8. Agile processes promote sustainable development. The sponsors,


developers, and users should be able to maintain a constant pace
indefinitely.
9. Continuous attention to technical excellence and good design enhances
agility.
10. Simplicity is essential.
11. The best architectures, requirements, and designs emerge from self–
organizing teams.
12. At regular intervals, the team reflects on how to become more
effective, then adjusts its behavior accordingly.
Not every agile process model applies these 12 principles with equal
weight, and some models choose to ignore the importance of one or more
of the principles.

The Impact of Agile Software Development Process on the Quality of


Software Product
Agile being one of the quickest methodologies for software development,
allows the quality product to be delivered to the customer side. The product
quality always depends upon level of satisfaction of the customers. The
higher the level of satisfaction, the higher will be the quality of the product.
However, it has been observed by different developers that only if the
process quality is as per the requirements the product quality will be as
expected, “process with high quality standards yields products with high
quality standards”. One can define process quality as a process that
conforms to defined process specifications to get good quality product.

31
Software Development Techniques Atica Altaie

Overall quality is much more complicated term than it appears. There are
varieties of perspectives for consideration for example, customer’s
perspective, developer’s perspective, tester’s perspective, specification
based perspective, manufacturing based perspective, and quality assurance
based perspective and many more.

Agile based- Different Software Quality Perspectives

32

You might also like