2. Ok! So we decide.
We will start agile project
execution from now on for all
our projects…
This won’t work for us!
We are wasting our
We Make Banking Easier time…
39/A,
4th Block, 6th Main, Board Room
Jayanagar,
Bangalore
This will reduce my customer
escalations and increase No more of the huge
collaboration with them… documentation which
no one reads…
We will deliver fast and
follow lightweight
processes…
3. Sameer
Agile Coach
Let’s start just two projects
with agile …
Switzerland
4. Planned Setup
James Vijay
Customer Contact Manager
Madhu
Architect
Ram
Account Manager
Development Team (15)
3 Leads
4 Senior Developers
8 Junior Developers
Switzerland
Quality Team (4)
2 Senior s
2 Juniors
5. Planned Setup
James Vijay
Customer Contact Sameer
Manager
Agile Coach Madhu
Architect
Ram
Account Manager Guys! We need to relook
at the set-up…
Development Team (15)
3 Leads
4 Senior Developers
8 Junior Developers
Switzerland
Quality Team (4)
2 Senior s
2 Juniors
6. Vijay
Manager
Company Project Madhu
Management Culture Needs Architect
Risk Customer
Appetite
Emotions People
James
Customer Contact
Ram
Account Manager
7. New Project Setup…
James
Product Owner (20%)
Team A Team B
5 Developers 5 Developers
2 QEs Kishor 3 QEs
0.5 Ux PO Proxy 0.5 Ux
0.5 Documentation 0.5 Documentation
Madhu
Overall
Project
Architect
8. I want to be the scrum master
Two weeks is too less for us.
We build complex software…
Scrum Anything is ok for me. I just
Rollout have to do my coding well.
Nothing else matters!
Meeting WOW! Agile, sounds good.
No more design.
No more documentation…
Yep! Agile is the current HOT
thing. And pretty simple.
I am super excited …
I’m sure nothing will change
Aren’t the current
Will the empowered team need
processes working?
a manager!?
Why do we need YAC?
If yes what will he do??
(Yet Another Change!)
Hummm… Ok… Agile…!
12. Yes Sameer!
I fully understand that things will
not be hunky dory from day Preparation: Sprint 0
one…
I am willing to support with
patience
(wk 1-2)
Team A
Team B
POCs
Kishor
James PO Proxy
Product Owner Landscape
Set-up
Templates
Initial
Product Technical
Backlog ramp-up
Team
Definition of Building
Done
14. Sprint 1 Results
(week 3-4)
Backlogs Status
BL1 Done
BL2 In complete
BL3 Done
Definition Of Done BL4 Rejected *
Zero open issues (prio 1-3) 5 open issues
BL5 Incomplete
Zero static code check issue 15 open issues
BL6 Done
(prio 1-2)
Code reviews Done for completed backlogs * Requirement Misunderstood
Automated unit tests Partial
Documentation Done for completed backlogs
15. Sprint 1 Retrospective
We were able to
achieve only half of
what we had planned I think we did reasonable.
I am happy the way the
team has put in efforts
James
The backlog should be Product Owner
little more detailed and
clearer
You developers should
finish coding 2 days early
so that we have time to
test
Team
Guys, a descent start,
Things were too stressful We really did well on…
towards the end … testing … Sameer
… closing on the backlogs… Agile Coach
Am sure we will do much
better next time
16. Sprint 2 Results
(week 5-6)
Backlogs Status
BL2 Done
BL4 Done
BL5 Done
Definition Of Done BL7 Done
Zero open issues (prio 1-3) 2 open issues
BL8 Rejected *
Zero static code check issue Done
BL9 Rejected *
(prio 1-2)
Code reviews Done * Missed part of acceptance criteria
Automated unit tests Partial
Documentation Done
17. Sprint 2 Retrospective
We should look at
acceptance criteria Better.
more carefully Focus more on understanding
the requirements correctly…
James
Product Owner
I think some of our
developers should also test
Code reviews were
worthless…
Team
Guys, Much better than the
I am still not sure where last sprint. We also
we are heading… improved on…, … Sameer
Don’t feel miserable…
Agile Coach
Let’s aim a “all well” sprint
for the next one…
18. Inception Phase: Characteristics and Tools
Excitement Suspicion Agile Coach
Prejudice
Struggle Expectation
Anxiety
Management
Assumptions
Unlearning Resistance
New Learning
Conflicts Management
Messed up Messed up
Planning Execution Transition
Chaos
Nothing Planning
Works Resistance
Stress Fear of Determination
Failure
Crashing
Shaking Management
Expectations
confidence Support
19. Sprint 4 Results
(week 10-12)
Backlogs Status
BL12 Done
BL14 Done
BL15 Done
Definition Of Done BL16 Done
Zero open issues (prio 1-2)* Done
BL17 Issue!
Zero static code check issue Done
(prio 1-2)
Code reviews Done
Automated unit tests Done
Documentation Done
* Done criteria adjusted
20. Sprint 4 Retrospective
It’s very good that
developers too helped I am happy.
in testing… I think we are getting
there…
James
Things were critical till the Product Owner
last day…
We focused really hard on
the done criteria…
Team
Let’s improve the utilization
factor of the team and
We should anticipate issues dependency on people.
more proactively … Sameer
Let’s look at the burndown Agile Coach
more regularly and replan
things…
21. Settling Phase: Characteristics and Tools
Things falling Management
in place Support
Ray of hope
Coaching
Building Trust
Open
communication Experimentation
Situational
Leaders Risk Taking
Fragile Setup
Failure
Tolerance
22. Sprint 15 Results
(week 30-32)
Backlogs Status
BL82 Done
BL83 Done
BL84 Done
Definition Of Done BL85 Done
Zero open issues (prio 1-2) Done
BL86 Done
Zero static code check issue Done
(prio 1-2)
Code reviews Done
Automated unit tests Done
Documentation Done
23. Sprint 15 Retrospective
We have reached quite
good predictability in
our execution Guys I am happy overall.
Put a little bit more focus
on Quality!
James
Product Owner
Shall we try “Pair
Programming”
I think it is not required.
We do code reviews which
is enough.
Team
Guys, Customer has reported 10
usability issues on the functionality
that we shipped in last 3 sprints. I
I work at odd times… think this is what James as well as Sameer
is referring to. Can we … Agile Coach
24. Matured Phase: Characteristics and Tools
Engineering
Stability Excellence
Predictability
Matrices
Fault
Tolerance
Hunt Issues
Sense of
Satisfaction
Reduce Safety
Comfort Zone Nets
Unwritten
Understandings Continues
Improvements
Slow
Improvements Challenges
25. Sprint 30 Results
(week 62-64)
Backlogs Status
BL182 Done
BL183 Done
BL184 Done
Definition Of Done BL185 Done
Zero open issues (prio 1-2) Done
BL186 Done
Zero static code check issue Done
(prio 1-2)
Code reviews Done
Automated unit tests Done
Documentation Done
26. Sprint 30 Retrospective
…I mean there is no
end to performance
improvements… I think we should
reduce the staffing
James
Product Owner
This is my last sprint
anyways….
Team
We should draw an end
line.
… May be form a support Sameer
team if required. Agile Coach
27. Dissolving Phase: Characteristics and Tools
Sense of low Wind-up Fast
value work
Disinterest
Clear Goals
Move-on
Challenges
Splitting team
Anxiety
No gradual
disinvestment
Less Challenges
Losing Support Team
Improvements
30. Reformation Phase: Characteristics and Tools
My Scrum
vs.
Your Scrum Unlearning
What was working
Relearning
there doesn’t work
here!
Scrum is not one
way
What didn’t work
there, won’t work!
here
31. Expect this when you are Scrumming…
Matured
Settling Dissolving
Inception Reformation
