Agile Network India | How to assess success of an Agile Implementation by Jaimon Francis

1. JAIMON FRANCIS
Enterprise Agile Coach
Introduction
Agile Partitioner for 6 + year
20+ year experience in IT
Agile Coach, Product Owner, Scrum Master
SAFe, Scrum, Kanban frameworks

2. Agenda
Agile Transformation Drivers
Challenges and Pitfalls
Key Focus Areas and Best Practices
Corrective Actions

3. Agile Transformation Drivers

4. Challenges
Observations
Reactions
Stories not getting completed in sprint
Team not able to deliver consistently and with
quality
Underutilized team members
Team skill gaps and dependencies on key
members
Lack of clarity on when feature will be released

5. Pitfalls

6. Transparency
Leadership team were
struggling to visualize
when the product
features will be released
The focus was on story
completion and to
achieve team velocity
The big picture was missing
and there was no mechanism
to visualize feature/release
progress
Dependencies were not
visible which made it difficult
to act in time and to enable
flow

7. Transparency
Prioritize the features
based on value
Focus on feature
completion
The release goals
were visible to
everyone
Team started
focusing on feature
completion
Time to market
was reduced
Better
feedback
loop
Feature dependencies
were identified and
tracked

8. Planning and Readiness
Stories not getting
completed in sprint and
features not getting
released
Inputs/pre-requisites
not available as planned
Blockers due to external
dependencies
Rework
Team not able to
achieve the sprint
forecast
External team
dependency
Gaps in understanding
requirements

9. Planning and Readiness
Feature elaboration
plan
Multiple-iteration goal Blockers reduced
drastically
Flow was
established
Throughput
improved
Identify dependencies
and make it visible
Make sure that stories
are made ‘ready’ only
after DOR is met
Predictability
increased

10. Team Performance
Team not able to deliver
consistently and with
quality
Frequent shuffling of
team members
Lack of coordination
within the team
DEV & QA out-of-sync
Poor Quality &
Increased Technical
Dept
DEV – QA silos
Increased Defects

11. Team Performance
Created a common
goal for the team
DEV team members
were encouraged to
support testers to
achieve feature
completion
Better team
cohesion
Automation was
achieved within the
sprint
Reduced
Technical Debt
All team members were
involved in business
discussions
DOD was
redefined
Quality
improved

12. Key Focus Areas
Releasable Features
Business Value
Time To Market
Ensure feature is releasable, ensure flow
Whenever feature is ready make it available to user
(reduce decay of value)
Work on the most valuable feature which bring
maximum ROI
Quality Constantly improve DOD, Reduce Technical Debt