AGILE DEVELOPMENT

Chapter 5
 AGILE

What is it? Agile software engineering combines a philosophy

and a set of development guidelines. The philosophy
encourages customer satisfaction and early incremental
delivery of software; small, highly motivated project teams;
informal methods; minimal software engineering work
products; and overall development simplicity. The development
guidelines stress delivery over analysis and design (although
these activities are not discouraged), and active and continuous
communication between developers and customers.
 TRADITIONAL TO AGILE

Why there is a need to move from Traditional to Agile?

 (TRADITIONAL TO AGILE)

SOFTWARE DEVELOPMENT MODELS

Extensive Documentation, Planning Less Documentation

and Designing
TRADITIONAL AGILE
Less interaction with customer Continues communication
with Customer
Long Processes Fast and easy development

Spiralnot focus much

Does Scrum and welcome
Flexible
on requirement change changes
Water Fall FDD

V-Model ASD

4
DSDM
 AGILITY PRINCIPLES

• Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes
harness change for the customer's competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.
• Business people and developers must work together daily throughout the
project.
• Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within
a development team is face-to-face conversation.
• Working software is the primary measure of progress.
 AGILITY PRINCIPLES

• Agile processes promote sustainable development. The sponsors,

developers, and users should be able to maintain a constant pace
indefinitely.
• Continuous attention to technical excellence and good design enhances
agility.
• Simplicity—the art of maximizing the amount of work not done—is
essential.
• The best architectures, requirements, and designs emerge from self
organizing teams.
• At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly
 REQUIREMENT CHANGE REASON

• Defect fixing
• A missing requirement
• Enhancement of a functionality
• Strategy of Project
• Improvement of design
• Reduction of scope
• Redundant functionality
• Obsolete functionality
• False Requirements
• Conflict resolution
• Requirement clarification
 SCRUM
 Scrum is one of the widely used agile methodologies.
 Scrum benefits:
 Manage complex projects
 Incremental and iterative approach
 Less documentation
 Fast development.
 In scrum methodology, project is divided into small work modules These
work modules are called sprints.
 SCRUM framework based of three parts; scrum roles, scrum artifacts
and the scrum ceremonies
 A sprint is about 1-2 weeks long and less than a month. These sprints
are scheduled strictly .
 SCRUM
SCRUM

Scrum Scrum
Scrum Roles
Artifacts Ceremonies

Product Owner Product Backlog Sprint planning

Scrum master Sprint Backlog Daily scrum meeting

Scrum team Sprint review meetings

Burn Charts

9
 SCRUM ROLES

Roles in scrum include; Product owner, a scrum master and

scrum team.
A Product owner is a client himself who prioritize and write
requirements, responsible for its funding and product release
planning, or a person who act on behalf of the client.
A scrum master act as project manager that is responsible for
managing all the scrum activities including managing teams,
tasks, sprints, delivery and successful completion of project.
Scrum team includes all the members who develop the
project, usually consist of 2 Or 8-10 members; they are
responsible for the requirements implementation of the project.
 SCRUM ARTIFACTS

Scrum artifacts include; Product backlogs, sprint backlogs and burn

charts. Product backlogs are the lists of tasks of the project that are
prioritized by the product owner according to the business need.
Sprint backlog consist of tasks that are going to implement in the sprint to
complete a module.
Burn charts is a graph consist of horizontal and vertical lines that show
how many task and time left for the project, it is used to track the project.
 SCRUM CEREMONIES

Scrum ceremonies are all the events happen in scrum include; Scrum Sprint
planning, daily scrum meetings, and sprint review meetings.
Sprint planning meeting is a meeting held before each sprint between the product
owner and team to discuss and plan what will be done in the next sprint.
Daily scrum meeting held daily for 15-20 minutes between the scrum master and the
team to discuss the status of the tasks, what will be next task? And any obstacles exist.
Three key questions are asked and answered by all team members
• What did you do since the last team meeting?
• What obstacles are you encountering?
• What do you plan to accomplish by the next team meeting?
It helps the team to discuss all the matters with each other to maintain the quality of
tasks.
Print review meeting held at the last of each sprint between the product owner and
team, to present what module they have done as a result of the sprint.
SCRUM PROCESS