This document discusses key aspects of Agile development methodologies. It outlines the four values of the Agile Manifesto: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan. It then describes four common Agile practices: sprint backlogs, test-driven development, pair programming, and daily stand-up meetings. For each practice, it provides details on what they are and lists advantages and disadvantages.

1. ADVANCED SYSTEMS ANALYSIS AND DESIGN
Agile Manifesto
PREPARED BY : ABDULKADIR OSMAN
MOHAMED

2. THE AGILE MANIFESTO STATES THE
FOLLOWING:

3. INDIVIDUALS AND INTERACTIONS
OVER PROCESSES AND TOOLS
• Means this we prefer individuals and
interactions instead of processes and
tools.
• What this point intends to me is that
the attention ought to be on the
people and the correspondence
between them. The process and
tools ought to be the base required
for a given circumstance.

4. WORKING SOFTWARE OVER
COMPREHENSIVE DOCUMENTATION
• It Doesn’t mean we don’t do
comprehensive documentation, but we
prefer to use working software as a primary
set of documentation
• but if you don’t document or if your
software issue documentation you are
going to run into problem

5. CUSTOMER COLLABORATION OVER
CONTRACT NEGOTIATION
• Contracts and project sanctions may give
some limit conditions inside which the
parties can work,
• yet just through progressing cooperation
can an improvement group plan to
comprehend and deliver what the customer
needs

6. RESPONDING TO CHANGE OVER
FOLLOWING A PLAN
•If we look a traditional project management, no one
can argue that following a plan is a good idea. In the
turbulent universe of business and innovation,
circumspectly following a plan can have critical
results, regardless of the possibility that it's executed
loyally.
• planning is still critical

7. AGILE DEVELOPMENT
METHODOLOGIES
• a) Sprint backlog
• b) Test-driven development
• c) Pair-programming
• d) Daily stand-up meeting

8. A) SPRINT BACKLOG
• The sprint backlog is a simple list of
the tasks that must executed by the
team in order to deliver an increment
of functional software at the end of
that sprint
• Giving some real attention to this
process is fundamental to a better
understanding by the team about
what should be done and to better
planning during the sprint .

9. SPRINT BACKLOG
Advantage Disadvantage
Should be updated every day
Less hours and tasks
Team can add or subtract items from the list
Sprint Backlog can only be updated by the team
No more than 300 tasks in the list

10. B)TEST-DRIVEN DEVELOPMENT (TDD)
• Also called test-driven design, is a
method of software development in
which unit testing is repeatedly done
on source code.
• The concept is to "get something
working now and perfect it later."
After each test, refactoring is done
and then the same or a similar test is
performed again. The process is
iterated as many times as necessary
until each unit is functioning
according to the desired specification.

11. TEST-DRIVEN DEVELOPMENT (TDD)
Advantage Disadvantage
 Iterative development and testing
 The codes start getting documented
 Tests become safety Net
 Programmers like to code, not to test
 Test writing is time consuming
 TDD may not always work

12. C) PAIR-PROGRAMMING
•Pair-programming is two programmers sharing
a single workstation (one screen, keyboard and
mouse among the pair). The programmer at the
keyboard is usually called the "driver", the other,
also actively involved in the programming task
but focusing more on overall direction is the
"navigator";

13. PAIR-PROGRAMMING
Advantage Disadvantage
 Overcoming difficult problems
 Reduced cost of development
 Learning and training
 Decreased risk of RSI
 Work preference
 Intimidation
 Conflict

14. D) DAILY STAND-UP MEETING
• This is a daily meeting usually in the
morning, which allows the team to remain
updated on progress and identify
roadblocks. This meeting should not take
more than 15 minutes, and each person
should have no more than 2 minutes to
speak.

15. DAILY STAND-UP MEETING
Advantage Disadvantage
 Employees keep each other updated.
 Anyone may suggest a topic.
 Meetings create a “brain trust”.
 Too many questions due to not being a regular at
meetings
 There’s always the question of who starts
 It’s very predictable and may lead to people only
really listen to the person that talks before them

16. Designed by: Kadir 2016