The document discusses continuous improvement in Agile processes. It states that retrospectives, which are meetings at the end of each sprint to discuss what went well, what didn't, and how to improve, are key to continuous improvement. Effective retrospectives have action items tracked to completion. A case study shows that using digital tools like shared boards for virtual retrospectives and action tracking backlogs helped ensure actions were completed, improving engagement, ideas, and outcomes. Continuous improvement is built into the Agile methodology through regular retrospectives.

1. Continuous improvement in Agile
BY SHALINI REDDY

2. Shalini Reddy
● I work for IBM as Senior Delivery manager
● I come from technical, Project management and process
background
● Certification: PMP® Certified, AgileCoachCertified, AWS
CloudPractitioner, Azure CloudFoundation Certified
ITIL® , Certified Lean Six Sigma Green Belt,
Certified DevOps Master
Certified SAFe®4 Agilest (SA), CSM® Certified Scrum
Master, Certified KanbanSystem Design - KMP I
● Personal front I have 1 son - Vishanth
● I like to do meditation, My favourite book - the Secret by Rhonda
Byne
HD Image

3. Continuous improvement in Agile
Plan
Execute
Review
Identify
Continues
improvement
➢ Many times, Continues improvement is
considered as nice to have, however CI is a
very real and effective methodology for
driving major long-term and sustainable
improvements
➢ Retrospectives are essentially planned
sessions that follow a period of work (e.g a
two-week sprint) that focuses on what did go
well or didn't go well, and what can be done
to improve the next sprint. The goal of
an agile team is to continuously improve how
they work as a team

4. Retrospectives
 Scrum is structured to deliver continuous
improvement. For example, at the end of every
Sprint a Sprint Retrospective is held. The purpose of
this meeting is for the whole team to ask three
questions
 A Sprint Retrospective is held at the end of each
sprint, building continuous improvement into the
methodology
 Action from retro meetings are tracked and worked
upon to closer
 Team reflects on the way of working and
continuously become better in what they do.
What went
well
What would
have gone
better
What do
you want to
try next
What
questions do
we have
Retro

5. Virtual Retro - Case Study
 Challenge
1. Retro was conducted but no actions tracked or worked
upon to closure
2. No Physical board for doing retro which resulted only
discussion and no actions after the retro
 Solution
1. Shared Digital board for conducting virtual retro, so that
team can post their ideas on the board before the Retro
2. Digital Action tracker was created and tracked in all the
retros (added in the backlogs)
 Results
1. 100% team engagement and increase in the volume of
actions/ideas to 60% completion which improved in
quality, lot cost savings & process improvement ideas
were implemented.
 Wins
1. Retro was conducted formally, and
actions tracked & worked upon
tothe closure
2. Digital boards/actions were added
to the backlogs
 Results
1. 100% team engagement and
increase in the volume of
actions/ideas to 60% completion
and continues improvement was
evident
Agile Project A
Agile Project B