Agile Methodology

B9BA105
2023-24

PhD Luciana Nascimento

luciana.nascimento@dbs.ie
Motivation to Agile
Agile Methodologies
Agile methodologies are approaches that Main features
enable ways of managing projects and • Short cycles

developing products that are more • Fast and frequent deliveries

• Small, self-managing and

adaptable to changes.
multidisciplinary team

• Focus on quality

• Delivering high customer value

They are aligned with the values and
principles of the Agile Manifesto.
Agile Methodologies
Agile Methodologies
Agile Methodologies
Agile Methodologies

SCRUM KANBAN Execution

LEAN CULTURE

OKR Strategy

DESIGN THINKING Innovation

ANTIFRAGILE LEADERSHIP Management

SCRUM
SCRUM Theory
Scrum is founded on empiricism and lean thinking.
- Empiricism asserts that knowledge comes from experience and making decisions based on
what is observed.
- Lean thinking reduces waste and focuses on the essentials.

Scrum employs an iterative, incremental approach to optimize predictability and to control risk.

Scrum engages groups of people who collectively have all the skills and expertise to do the
work and share or acquire such skills as needed
SCRUM - Pillars
Transparency
The emergent process and
work must be visible to both
those performing the work and
those receiving the work.
Transparency allows
inspection.
Inspection
Scrum artifacts and progress
toward agreed-upon goals must
be inspected frequently and
diligently to detect potentially
undesirable variances or issues.
Inspection enables adaptation.
Adaptation
If any aspect of a process
deviates outside acceptable
limits or if the resulting
product is unacceptable, the
process being applied or the
materials being produced
must be adjusted.
SCRUM
3+5+3

• 3 Roles : Product Owner, Scrum Master, Developers

• 5 events : Sprint, Sprint Planning, Daily, Sprint Review, Sprint Retrospective

• 3 Artifacts: Product Backlog, Sprint Backlog, Increment

SCRUM - Roles
PO - Product Owner
Accountable for maximizing
the value of the product
resulting from the work of the
Scrum Team.
The entire organization must
respect their decisions
SCRUM Team
SM - SCRUM Master
Accountable for establishing
Scrum as defined in the Scrum
Guide.
Accountable for the Scrum
Team’s effectiveness, by
enabling the Scrum Team to
improve its practices
Developers
Developers are the people in
the Scrum Team that are
committed to creating any
aspect of a usable Increment
each Sprint
PO - Product Owner
The Product Owner is accountable for effective
Product Backlog management, which includes:

• Developing and explicitly communicating the

Product Goal
• Creating and clearly communicating Product
Backlog Items
• Ordering Product Backlog Items
• Ensuring that the Product Backlog is transparent,
visible and understood
 SM - SCRUM MASTER
Serves the Scrum Team
• Coaching the team members
in self-management and
cross-functionality;
• Helping the Scrum Team
focus on creating high-value
Increments that meet the
Definition of Done;
• Influencing the removal of
impediments to the Scrum
Team’s progress; and,
• Ensuring that all Scrum
events take place and are
positive, productive, and
kept within the timebox.
Serves the PO
• Finding techniques for
effective Product Goal
definition and Product
Backlog management
• Providing ways for the Scrum
Team to understand the
need for clear and concise
Product Backlog items
• Establishing empirical
product planning for a
complex environment
• Facilitating stakeholder
collaboration as requested or
needed
Serves the Organization
• Leading, training, and
coaching the organization in
its Scrum adoption;
• Helping employees and
stakeholders understand and
instill an empirical approach
for complex work
• Removing barriers between
stakeholders and Scrum
Teams.
SM - SCRUM MASTER
Developers
The Developers are always accountable for:

• Creating a plan for the Sprint, the Sprint Backlog

• Instilling quality by adhering to a Definition of Done
• Adapting their plan each day toward the Sprint Goal
• Holding each other accountable as professionals

Source: https://saat-network.ch/2023/03/developers-in-scrum/

Developers may also have instances where they need to embrace such
practices as facilitation, mentoring, teaching and coaching.

A Developer is not necessarily a software developer.

 Questions?
Comments?
https://tinyurl.com/pmquestion
SCRUM - Events
SPRINT
SCRUM Events
Sprints are short projects, where all work is done
Sprint When one ends, the next one immediately begins
Begins with the Planning, finishes with the Retrospective
Fixed length events of one month or less
Sprint Planning

During the Sprint:

Daily SCRUM
● No changes are made that would endanger the Sprint Goal;
● Quality does not decrease;
● The Product Backlog is refined as needed; and,
Sprint Review ● Scope may be clarified and renegotiated with the Product
Owner as more is learned.

Sprint
Retrospective
SCRUM Events
The Sprint starts with a planning session in which the Developers plan
Sprint the work they intend to do in the Sprint

Results in the creation of the Sprint Backlog, which includes the

Sprint Planning Sprint Goal, the selected Product Backlog Items and the Developers’
plan
Daily SCRUM
During the meeting, the Scrum Team focuses on:

● The value that can be created during the Sprint

Sprint Review ● Choosing which Product Backlog Items will be addressed
during the Sprint
● Planning the work required to accomplish their goal
Sprint ● Planning to create an Increment that meets the Definition of
Done
Retrospective
SCRUM Events
Developers get together for 15
Sprint minutes every day to inspect the
work towards the Sprint Goal and to
plan the upcoming day’s work.
Sprint Planning
During the Daily Scrum, they identify
any issues they need help in
Daily SCRUM
resolving, ask for help when they
need it and adjust the Sprint Backlog,
if necessary
Sprint Review

Sprint
Retrospective
SCRUM Events
Sprint

Sprint Planning
Is a working meeting where the Scrum Team presents their
completed work to their stakeholders and asks for feedback and
Daily SCRUM
guidance.
Together, the Scrum Team and stakeholders discuss
● the progress made toward the Product Goal,
Sprint Review ● any emerging changes in the business or technical climate
● what to do next.
Sprint
Retrospective
SCRUM Events
Sprint

Sprint Planning
The last working meeting of a Sprint.
Daily SCRUM The team typically discusses:
● How well the team members interact and communicate
● Any impediments they’ve encountered
Sprint Review ● How well impediments were removed
● If the Definition of Done still serves them as written, or if it needs to be
updated
Sprint ● If there are any improvements to how the team works that can be
Retrospective implemented in future Sprints -> Improvement Actions!
 Event Inspection Adaptation Participants Timebox

Sprint Planning Product Backlog, Sprint Backlog, Scrum Team 8 hours for a 1
Product Goal, Sprint Goal month Sprint
Definition of Done

Daily Scrum Progress toward Sprint Backlog Developers 15 minutes

Sprint Goal

Sprint Review Increment, Sprint, Product Backlog Scrum Team, 4 hours for a 1
Product Backlog, Stakeholders month Sprint
Progress toward
Product Goal

Sprint Sprint (process, Actionable Scrum Team 3 hours for a 1

Retrospective interactions, tools, improvements, month Sprint
etc), Definition of Definition of Done
Done

Source: scrum.org
 Questions?
Comments?
https://tinyurl.com/pmquestion
SCRUM - Artifacts
SPRINT
SCRUM Artifacts: The Product Backlog
The Product Backlog’s purpose is to represent all of the work
the Scrum Team knows it needs to do in order to deliver the
product.

The Product Backlog consists of:

Product Backlog items (PBIs) - each of which represents
something that needs to be done.
A Product Goal - that describes the Scrum Team’s current
long-term objective for the product.

SINGLE TRANSPARENT CURRENT ORDERED

Product Backlog Items - Example
As a teacher, I want Refactor user
Establish criteria for the
to be able to interface code to
Implement encryption assessment of open
configure the group improve
for all personal user source software that
of tools that are understandability and
data. (engineering might be used as a basis
available to performance.
improvement) for parts of this system.
individual classes. (engineering
(development activity)
(feature) improvement)
Product Backlog
 SCRUM Artifacts: The Sprint Backlog
The Sprint Backlog represents what the Developers plan to
accomplish during the Sprint. They create this plan during the
Sprint Planning.
The Sprint Backlog contains:
● The Sprint Goal which describes the objective for the Sprint.
Why are we doing this Sprint?
● A set of Product Backlog items (PBIs) selected for the Sprint.
Which PBIs will be addressed in this Sprint?
● An actionable plan for how the team will deliver the work and
achieve the Sprint Goal.
How will we achieve our Sprint Goal?
SCRUM Artifacts: Increment

An Increment is a concrete stepping stone toward the

Product Goal.

Each Increment is additive to all prior Increments and

thoroughly verified, ensuring that all Increments
work together.
In order to provide value, the Increment must be
usable.
SCRUM Artifacts
The Definition of Done - DoD
Examples of the items in a Definition of Done
for a health-focused software application
The Definition of Done is the commitment by the
Developers for the Increment. ● All testing completed
● No known defects
It creates transparency by providing everyone a
● Code review completed and passed
shared understanding of the required standards of ● Meets HIPAA Compliance standards
work that was required as part of the Increment. ● Meets general security requirements
Created by the SCRUm Team.
Kanban - Intro
What is Kanban?
There are a variety of approaches to Kanban, but most agree that Kanban is a change management
method that focuses on the following principles:
Visualize Work : Visualize every step in your value chain from vague concept to releasable
increment.

Limit Work-In-Progress (WIP): Set explicit limits on the amount of work allowed in each stage.

Make Policies Explicit: Make the policies you are acting according to explicit.

Measure and Manage Flow: Measure and Manage Flow to make informed decisions and visualise
consequence

Identify Improvement Opportunities: Create a Kaizen culture where continuous improvement is

everyone’s job.
 Kanban Board
Workflow

SCRUM teams
Item State often use a
Kanban Board

(not necessarily
the whole Kanban
method)

Different
classes of
items

Pull items from

the Top
Limit Work In Progress
Measure the Flow
Ex.:
Kanban - Visualize Work
 SCRUM vs Kanban
SCRUM KANBAN

Cadence Regular fixed length sprints (ie, 2 weeks) Continuous flow

At the end of each sprint if approved by the

Release methodology Continuous delivery or at the team's discretion
product owner

No existing roles. Some teams enlist the help of an

Roles Product owner, scrum master, development team
agile coach.

Key metrics Velocity Cycle time

Teams should strive to not make changes to the

Change philosophy sprint forecast during the sprint. Doing so Change can happen at any time
compromises learnings around estimation.
 Questions?
Comments?
https://tinyurl.com/pmquestion
Case