Creators

Nirdesh Dwa & Jyoti Manandhar

Veda (veda-app.com)

AGILE & SCRUM

OVERVIEW
Agile Methodology
Basic Overview
Agile Methodology

Meaning of Agile

Agile is the ability to create

and respond to change by
accepting change and working
on it.

It is a way of dealing with, and

ultimately succeeding in, an uncertain
and turbulent environment.
Agile Methodology

The History

The primitive way of software Summit was held and the term
development could not keep up with the agile software development was
everchanging and frequent customers’ stamped owing to the flexibility
change requests, which led to software and interactive nature of
development failure in most cases. development

Late 1970’s Early 1990 2000s After 2000

A small group of software Agile Development

industries began to address the became a popular
problem by reacting and methodology for
adapting to the changing software
requirements and technologies. development.
Agile Methodology

The Agile Mindset

+ Set of attitudes supporting an agile working environment.

+ Respect, collaboration, improvement and learning

cycles, pride in ownership, focus on delivering value, and
the ability to adapt to change.

+ Not a must-have before practising agile but it does help

a team to flourish and it does help to make employees happy
and productive.

+ Reasoning behind practising agile.

+ Makes managers less directive and more supportive

Agile Methodology

Agile Manifesto: Values

Individual and interactions over Process and tools

Working Software over Comprehensive Document

Customer Collaboration over Contract Negotiation

Responding to change over Following a plan

Agile Methodology 1. Satisfy your 2. Welcome 3. Deliver 4. Work
customer change frequently together

The 12 Agile Principles

5. Trust and 6. Face to face 7. Working 8. Sustainable

support communication software development

9. Continuous 10. Maintain 11. Self 12. Reflect and

attention simplicity organizing team adjust
Agile Methodology

Agile Mindset Values (Cont)

Summary of Agile Principles

+ Welcome change.

+ Continuous delivery

+ Customer Collaboration

+ Motivated self-organized team

+ Importance of face to face conversation

+ Frequent meetings to discuss the process

 Agile Methodology

< 1% XP

< 1% DSDM / Atern

< 1% Agile Unified

Process (Agil UP)

1% Feature-Driven
Development (FDD)

1% Agile Modeling
Agile Framework Use Cases

2% Other

2% Lean Development

3% I Don’t Know

4% Iterative Development

5% Kanban

6% Scrumban

Custom Hybrid
8%
(multiple methods)

Scrum/
10%
XP Hybrid

56% Scrum
Scrum Framework
Basic Overview
 Agile Framework: Scrum

Basic Overview
Scrum Framework

+ Agile Framework

+ Solve problems with Scrum

+ Fail fast, learn fast

+ Focus on maximizing team efficiency

+ Fixed time & budget but flexible scope

+ All about collaboration & communication

 Why use Scrum?

+ Faster + Continuous improvement, improves how teams work

Scrum Framework

and deliver value in less time.

+ Better
+ Customer Focused
+ Happier
+ Emposers Team
+ Smarter
+ Lowers risk and increases return in investment (ROI)
Scrum Framework
 Roles in Scrum
Scrum Framework

Product Owner Scrum Master The Team

+ Gather and create goals + Create a list of tasks + Drive the plan for
or user stories each sprint
+ Distribute work equally
+ Manage and prioritize + Stay focused and well
+ Track progress
backlog organized.
frequently
+ Interact with clients + Cross-train each other.
+ Spot improvement
or management
opportunities + Approach project with
+ Identify more areas a ‘we’ attitude.
to work on
Implementation
important parts
Implementation
 Ceremonies of Sprint

Sprint Sprint Daily Sprint Sprint

planning scrum review retrospective
Implementation
 1. The Sprint

+ Finalize a cycle, timebox work

+ Itself an event that contains all the work and events that happens
during the timeboxed period of development

+ Starts immediately after concluding the previous sprint

+ Usually the duration of 1 to 4 weeks

Implementation
 2. Sprint Planning

+ Product Owner and Development team finalize the tasks from the Product Backlog

+ Product Owner prioritizes the items from the backlog

+ The development team can question and push back where necessary

+ The development team then decide the number of backlogs that would be
delivered at the end of the sprint

+ Create a sprint goal and sprint backlog.

+ Plan for upcoming sprints too

Implementation

+ New backlog items

+ Write User story - written by PO

 3. Daily Standups

+ Face to face 10-15 min stand up (now that we are working from home, let’s try a
video call)
+ Create a plan for the next 24 hours so should be started before starting work on
that day
+ Meeting should be short and to the point
+ Things to discuss:

■ What you did yesterday?

■ What you will do today? (Planning event rather than status tracking)

■ Any impediments?
Implementation

+ No detailed discussions. If required, the team may meet immediately after the
huddle to discuss further
 4. Sprint Review

+ Scrum Master facilitates the event and makes sure the participants understand
the purpose of the event. The Scrum Master keeps this event time-boxed.

+ A meeting is held after coming to an end of the sprint (usually the last day)

+ PO explains what product backlog items have been completed and what has
not been

+ The Dev team provides a demo

+ The Dev Team discusses what went well during the Sprint, what problems it ran
into, and how those problems were solved
Implementation

+ Stakeholders provide feedback and share room for improvement if any

+ Changes to be added to the product backlog

+ Scrum Master explains the

 4. Retrospective

+ Occurs after sprint review before planning for next Sprint

+ A one hour meeting for two weeks duration sprint and three hours meeting for
four weeks duration sprint

+ Discussion on the following:

■ what went well?

■ what did not go well?

■ what can be done better? Keep doing what went well and
implement what could be done better.
Implementation
 Scrum Artifacts

Product Backlog Sprint Backlog Product Increment

Implementation
 Scrum Artifacts (contd)

Product Backlog Sprint Backlog Product Increment

+ Collection of work to be + Collection of work to be + Sum of backlog items

done by the team done by a team during that achieve sprint
sprint goals
+ Living Document
+ Detailed Plan
+ At the end of a sprint,
+ Gets developed along with + Better if we don’t alter it
new increment must be
the product development
a working product
Implementation

+ The meaning of done

must be universal
throughout the team

.
LET’S GET THINGS DONE TOGETHER