This paper describes Saikat's experiences with Agile values, tranforamtion and my implementation of them. He describes the circumstances that have led him to believe passionately that Agile Frameworks will best assure the success of his projects.
Competency models for the team and how to choose specific practices against the model.
He describes what has worked for him and why, and he describes what hasn’t worked and why.
Highlights:
A different Approach to look into Agile practices and Transformation.
The difference between Agile Adoption and Agile Transformation.
The real goal of Agile change initiatives.
Adapting Practices in Agile.
3. Agenda
My High Level Agile Learnings
What guides AgileTransformation
Need for Culture
Challenges ofToday
Transformation Strategies
Five Essential Steps of anAgileTransformation Journey
Questions
Engineering Practices to furtherTransformation
7. – Its Adjective
Not Just Output
Show Contextual Leadership
Be Safe Do Incrementally
Basics Of Team Synergy is must
Don’t Be A Compete Agile Purist Or Zealot
You Ain’t Gonna Get Technical Improvement At All
8. Don’t Over Do Or Under Kill
– Ahead Of Everything Else
– Adaptive and Resilient mindset
– Avoid Silos And Heroism
– Practice Joint Decision Making
– Hands On and Embedded
– Continuous & IncrementalTransformation
11. Common Missteps to FastTrack AgileTransformation
• Forklifting best practices
• Underestimating the need for an “Agile culture” -
• Ill-structured program governance
12. Common Missteps to FastTrack AgileTransformation
• Misaligned prioritization
rigid budgeting process
• No investment
30. “We need to deliver
more value driven
services”
“We need to offer
faster and more
responsive services”
“We need to reduce
our costs and
become more
efficient”
$
31. Incremental Development
Iterative Development
Scrum
eXtreme Programming
Kanban
Lean Software Development
Continuous Delivery
DevOps
Lean StartupFeature Driven Development
Home-brewed Small “a” agile Big “A” Agile Methods Leading Edge Agile
The agile ecosystem is diverse and complicated
What do each of
these really mean
to my
organization?
ImpactofChange
Medium
Low
Low
High
Medium
Medium
High
High
High
Process
People
Technology
Your agile isn’t my agile… the adoption of agile is uneven and inconsistent across IT organizations
32. The road to success?Take a different approach to agile change
• Being agile is about delivering greater business value and not just the process
• Your context matters, there is no one “right” approach to agile adoption
• The organization needs to own and define what agile means to them
X = agile method (Scrum, XP, Kanban, SAFE, DAD etc.)
X = Agile
33. Transformation Strategies
In your agile transformation you will spend much more effort addressing
people-oriented (being agile) issues than you will either of process (doing agile)
or tooling (supporting agile) issues.
Think of it like this: these three factors are effectively the legs of a stool, if you
don’t address all three then your agile transformation will fall over.
- March 21, 2016 by Scott Ambler.
(being agile) = BA; (doing agile) = DA; (supporting agile) = SA