This presentation will explain the characters of agile in any given organisation and also categorizes the stakeholders involved in any given engagement. This presentation will help in understanding the characteristics and recommends the mechanism to handle the various situation.

1. Agile & Generation(s)
DSK Chakravarthy

2. agenda
1. agile generations
2. stakeholders generations
3. agile 3.0
4. bonus

3. agile generations
history lesson ..
v1.0

4. agile 1.0
manifesto for agile development..
agile is not NOUN, but, ADJECTIVE
12v2.0

5. agile 2.0
automation
code base
testing
small
delivery
feedback
Continuous
improveme
nt
whole
TEAM
ceremonies,
practices, pipelines
test automation, continuous integration,
continuous delivery, feedback
People
Process
Tools
culture
devops
speed
skill
112++

6. agile 2.0 ++
devops
open source tools,
communities of best practices,
release management,
best practices..
10whatnxt

7. what next
9whatdone

8. do (vs) be
art of science ..

9. TODO : Do (vs) Be
we ARE
• Practices & Process
• SpeedToMarket & Value
• Quality & Quantity
• Engage & Inspire
• Consistence & Regular
we WILL
• Values & Principles
• Accepting & Adapting
• Propagate & Explore
• Delegate & Facilitate
• Push your boundary
• Play with Paradox
8whatdone

10. stakeholders
generations ..
everyone, involved in all phases of application development (or)
software development
oldies

11. oldIES – gray hair ..
Characteristics
• 80s and early 90s
• Command and control
• Carrot and stick mode
• My way (or) high way
• Penny wise, pound foolish
Recommendations
• Follow them
• Don’t fight with them, cos, you will
never win
• Fail, at their cost and accountability
• Learn from their failures
• Take off ___/ ̅ ̅ ̅ ̅
• from their thoughts
• from where they left
Individual / Energy Sources
..
7baldies

12. baldIES / Y2Ks : >17+ yrs
Characteristics
• It worked then, why not NOW
• Seek and straight
• Politicians at work (introduced the
term work politics)
• Maintain relationships at distance
(or) arm’s length
• Numbers matter more than anything
• Opinionated and Early visioniries
Recommendations
• InPerson / 1:1 / Walk unto them
• Don’t be honest
• Reciprocate & be responsible
• Don’t follow their failures
• Keep them informed all the time
• Use them as Change Agents
• Allow them to teach YOU & Others
6bloodies

13. bloodIES: 5 - 10 yrs (± 2 yrs)
Characteristics
• Contributors and Workaholics
• Early Adaptors & Taste Failures
• LeadByExample, IDONTCAREs
• Group-Learners and Extraverts
• Authentic and Self-Reliant
• Achievers at the cost of PERSONAL
sacrifices
Recommendations
• Don’t be diplomatic
• Be sincere
• Spend quality (PERSONAL) time and
allow them
• Encourage and Make them LEAD
• Be accountable for their failure
• Pool them to LEARN and facilitate
5boldies

14. boldIES : <5 yrs (± 1 yr)
Characteristics
• It worked then, why not NOW
• Seek and straight
• Politicians at work (introduced the
term work politics)
• Maintain relationships at distance
(or) arm’s length
• Numbers matter more than anything
• Opinionated and
Recommendations
• InPerson / 1:1 / Walk unto them
• Don’t be honest
• Reciprocate & be responsible
• Don’t follow their failures
• Keep them informed all the time
..
4whatdone

15. Agile 3.0
(old wine in a new bottle!!??)
back to basics .. earth is round..
Agile 3.0
(old wine in a new bottle!!??)
v1.0

16. agile 1.0 : Characteristics
• Management hierarchy is still linear
• Focus is still on DELIVERY
• Team doesn’t have the road maps of the application / career / company / etc.,
• Accountability is oscillating between extremes of RED colored projects
• Few POCs for overall project / product / company / etc.,
• Transparency is not a VALUE, but a hook to hang-on
• Retrospect's are just a ceremonies
• PM is SM & BA is PO
• 1 day is 1 Estimate Point
• Backlog grooming doesn’t have a meaning
3v2.0

17. agile 2.0 : Characteristics
• Management hierarchy is still linear, yet, new roles added, specific to agile
• Focus is shifted from DELIVERY to CI & CD, resulting DevOps
• Cross functional teams started forming
• POs started prioritize the backlogs, yet, BAs preparing the UserStories
• POs are still the Quality / Acceptance parameters
• Blame game is NEW retrospect meeting, commitment is still at DEFAULT
• Accountability is still with few VPs / DMs / Sr. PMs / etc.,
• Process, Process, Process .. Pile of metrics ..
• team / individual / cycle times / story points / ScrumOfScrums
• Inspect & Adapt is started, slowly though
• Sprint commitment varies due to ChangeRequests / Ad-hoc activities / etc.,
• Study state / Cycle times / Story Points / ScrumOfScrums
2v3.0

18. agile 3.0 : Characteristics
• Not ROI, but, ROC
• Move from VALUEset to MINDSET
• Coaching (vs) Mentoring
• Prevention (vs) Retrospection
• retrospect backlog / learning backlog / transition backlog
• Future vision
• Automation (vs) RPA
• Cognitive Agility (vs) Corporate Agility
• AI (vs) ML
• VUCA to FACTS (flexible, adaptable, community, transparent, secured)
1½++(vs)3

19. 1.0 => 2.0 => devops => 3.0
1.0 + 2.0 + devops
• too much emphasis on working
software
• automation centric
• evolve to RPA paradigm
3.0 / new age agility
• invest on people power
• cognitive value & relation centric
• build & nurture the FAIL culture
• elusive .. explore
0bonus

20. bonus
thanks