Agile Software Development

Methodology

CREATED BY: ANKIT GUPTA

Topics

 Agile Software Development

 Characteristics of Agile Processes

 Agile Methods

 Scrum

 Product Backlog

 Sprint Backlog

 Daily Standup Meeting

 Agile Process
Topics

 User Story & Task Examples

 Agile Tools

 JIRA Agile: Features

 Sprint Overview

 What Agile Deliver

 Thank You
Agile Software Development

 Agile software development is a conceptual framework for software engineering that

promotes development iterations throughout the life-cycle of the project.

 Software developed during one unit of time is referred to as an iteration/sprint, which may
last from one to four weeks.
Characteristics of Agile Processes

 Agile process possess the following main characteristics:

 Quality
Testing is integrated throughout the lifecycle, enabling regular inspection of the
working product as it develops. This allows the product owner to make necessary
adjustments & gives the product team early sight of any quality issues.
 Visibility
Agile development principles encourage ‘user/client’ active involvement throughout
the product’s development process. This provides excellent visibility for key
stakeholders, both the project’s progress and the product itself, which in turn helps to
ensure that expectations are effectively managed.
Continue…

 Early Identification and Resolution of Issues

Small incremental releases made visible to the product owner and product team
through its development help to identify any issues early and make it easier to respond
to change. The clear visibility in agile development helps to ensure that any necessary
decisions can be taken at the earliest possible opportunity, while there’s still time to
make a material difference to the outcome.
 Iterative Releases, Communication, Continuous Integration
The active involvement of a user representative/product owner, the high visibility of
the product and progress, and the flexibility to change when change is needed, creates
better business engagement and customer satisfaction. This is an important benefit
that can create much more positive and enduring working relationships.
Continue…

 Predictable Costs and Schedule

Because each Sprint is a fixed duration, the cost is predictable and limited to the
amount of work that can be performed by the team in the fixed-schedule time box.
Combined with the estimates provided to the client prior to each Sprint, the client can
more readily understand the approximate cost of each feature, which improves
decision making about the priority of features and the need for additional iterations.
 Other Characteristics:
• Adaptive, welcoming changes, even late in the lifecycle.
• Changing requirements
• Changing techniques
• Small to medium sized teams
• Simple design
• Minimal system into production
Agile Methods
Scrum

SCRUM is an agile development method which concentrates specifically on how to

manage tasks within a team-based development environment. It consists of three
roles, and their responsibilities are explained as follows:
 Scrum Master
Master is responsible for setting up the team, sprint meeting and removes obstacles to
progress
 Product owner
The Product Owner creates product backlog, prioritizes the backlog and is responsible for
the delivery of the functionality at each iteration
 Scrum Team
Team manages its own work and organizes the work to complete the sprint or cycle
Continue…
Product Backlog

 Product Backlog

The Product Backlog is the single source of requirements for any changes to be made to the
product.

The Product Owner is responsible for the Product Backlog, including its content, availability,
and ordering. The Product Backlog lists all features, functions, requirements,
enhancements, and fixes that constitute the changes to be made to the product in future
releases.
Sprint Backlog

 Sprint Backlog

The sprint backlog is a list of tasks selected from the Product Backlog to be completed
during the current sprint. During the sprint planning meeting, the team selects some items
from product backlog items, usually in the form of user stories, identifies the tasks
necessary to complete each user story, and estimates how many hours each task will take
to complete.
Continue…
Daily Standup Meeting

Stand up meetings is where the development and testing team meets daily to discuss:
 What progress in the assigned task they made yesterday
 What tasks they have planned to do today
 Is there any impediment or obstacle that prevents them from completing the task
In addition to these details each member has to tell that how long they are going to take to
complete the assigned task within the sprint.
 If any remaining or pending task of any member of the team is not completed in that
particular sprint then they share such details in the daily meetings.
 Accordingly the pending task(s) from the previous sprint are taken care in the next sprints.
 Likewise if there are any changes in the requirement from the customers or any build issues
or any blocking issues then such details are also discussed in the meetings.
Agile Process

 Create user stories from business prospective thereby creating Product Backlog
 Prioritize the stories as per business in backlog.
 Each iteration of a scrum is known as Sprint
 Follow sprint planning meeting where the stories are selected which needs to be
completed into a particular sprint thereby determining the Sprint Backlog.
 Translate the stories into tasks and then into sub-task.
 Estimates the tasks to be completed in a particular sprint.
 Product is designed, coded, and tested during the sprint.
 Each Sprint begins with the Daily Sprint Meeting
 Follow Agile methodology to complete stories in a particular sprint.
 Once the sprint is completed, we showcase the developed product (internal & external)
 Follow sprint retrospective meeting, where team learns how they're doing and find ways to
improve.
User Story & Task Examples
User Story
As a patient, I should be able to Sign Up
with the Patient App
As a patient, I should be able to Sign In Integrate API in mobile development
into the app
Tasks
Prepare Sign Up API with proper request and response parameters
Prepare Manage Patient module in backend
Design the Sign Up screen
Integrate API in mobile development
Manage Navigation
Draft Test Cases for Patient Sign Up
Execute Test Cases for Patient Sign Up
Prepare Sign In API with proper request and response parameters
Design the Sign In screen
Manage Navigation
Draft Test Cases for Patient Sign In
Execute Test Cases for Patient Sign In
Agile Tools

 JIRA Agile
JIRA Agile unlocks the power of Agile, user can create and estimate
stories, build a sprint backlog, identify team commitment and velocity,
visualize team activity, reporting on team progress.
JIRA Agile: Features
 Create a Board (Scrum): A board displays issues from one or more projects, giving you a
flexible way of viewing, managing and reporting on work in progress.

 Configuring a Board: Manage Board, Renaming Board, Changing a Board administrator and
sharing a board

 Use Board:
• Create new Stories — Use inline Story create to quickly add Stories to your backlog.
• Prioritize the backlog — Create issues for your backlog and estimate them, and drag-
and-drop to add them to a sprint.
• Estimate Stories
• Create Tasks & Sub-Tasks — Break a story down into implementable chunks and create
tasks & sub-tasks.
Continue..
 JIRA Reporting:
• Cumulative Flow Diagram
• Release Report
• Sprint Report
• Velocity Chart

 Working with User Story Functionality:

• Creating, Viewing & Editing story
• Estimating story
• Flagging a story

 Working with Sprint Functionality:

• Creating a Sprint
• Editing or Reordering a Sprint
• Adding stories to a Sprint
• Removing stories from a Sprint
• Starting & Ending a Sprint
• Deleting a Sprint
Sprint Overview
 Continue…

Sprint Planning
Product Backlog Team Structure & Capabilities Business Conditions
Sprint
Sprint Backlog 2-4 Weeks Plan
Daily Scrum Meeting
Daily 15 minutes status meeting Tasks Discussion &
Decision Making
with team Impediments
Sprint Review Meeting
Review Meeting (internal) Review Meeting (external)
Sprint Retrospective Meeting
What improvements can be
What went well? What went wrong?
done?
What Agile Deliver

 Agile allows us to focus on delivering the highest business value in the shortest
time.
 It allows us to rapidly and repeatedly inspect actual working software (every two
weeks to one month).
 Every two weeks to a month anyone can see real working software and decide to
release it as is or continue to enhance for another iteration.
Thank You