Post on 15-Apr-2017
CHANGE REQUEST FOR RIGHT MINDSET
Rahul Sudame- CSM, PMI-ACP, SAFe SPC
CHANGE REQUEST IN AGILE?
Responding to
ChangeAdaptive Self
ManagingSignoff Change Request CCB
Waterfall Agile
BUT WE DO NEED ONE CR – FROM WATERFALL
• Command & Control
Plan Driven
• Plan Driven
• Hierarchical
BUT WE DO NEED ONE CR – TO AGILE
• Collective ownership
• Iterative
• Teamwork
BIGGEST ROADBLOCK - MINDSETCome on! We cannot ship hardware in
phases
We cannot skip compliance in
our environment
How can we plan a Sprint
for production support?
Agile in compliance
driven environment
As a Manager, I am responsible for
delivery!
FROM PRODUCT OWNER’S ANGLE
Building Product Backlog is not a casual activity, it
needs time!
There are so many meetings in Agile, I can’t
spare that much time
Now I need to convert all of my FSDs into user
stories
Do I need to learn Cucumber, FitNesse at
this age?
FROM PROJECT MANAGER’S ANGLE
How is the release possible without a detailed project
plan?
Team cannot do planning & tracking by themselves!
Is my job safe in Agile?
I will become Scrum Master and will implement
Agile ‘My’ way
FROM ARCHITECT’S ANGLE
How can we ignore HLD,
LLD, Detailed Architecture?
Have you got ‘signoff’ on the design before
proceeding with coding?
Lets have design Sprint before coding sprint
We cannot skip Design &
Architecture!
FROM DEVELOPER’S ANGLE
Agile has increased night outs for me
I need to finish this story in
current Sprint ‘anyhow’
I need to do design, coding, unit testing,
code reviews & update Jira in ‘same’ sprint
With so many meetings, when should I spend time
on coding?
FROM TESTER’S ANGLE
Who is my boss – QA Manager, Project Manager or Scrum
Manager?
Automation drive in Agile is
killing my manual testing
job
Developers are throwing new builds at
me so rapidly
I cannot complete test case writing & testing in
same Sprint!
FROM CUSTOMER’S ANGLE
These engineering guys are asking for my time every two
weeks
Let me demand Agile project
with fix price & fix timelines
Alas! I don’t need to raise Change Request
anymore!
Come on! I don’t have time to create product
backlog
AGILE FAILURE MODES Just following ‘practices’ not ‘principles’
Scrum-but – Tailoring to the extreme
None or in-effective retrospection meetings
Imposed Agile
Culture doesn’t support change
AGILE FAILURE MODES Compliance & Control measures to extreme
Lack of collaboration
Ignorance towards design, documentation & other engineering best practices
PO / PM / SM with command & control style
Tsunami of technical debt
EASIER SAID THAN DONE
AgileMindset
Servant leadership
Adaptive Managemen
t
Active Listening
Brainstorming Techniques
Empowered Teams
TRANSFORMING TO AGILE IS NOT EASY
IT NEEDS SERIOUS EFFORTS The rational for going Agile needs to be discussed
& agreed
Senior management needs to provide complete support
Continuous & serious Change Management needs to be applied
Effective support system like training/coaching, communities of practice needs to be built
SUMMARY Right mindset is absolutely needed for success of
Agile
Model the desired behavior
Create and communicate a common vision
Willingness to challenge the status quo
Be open to try new things
Empower & encourage others