Surviving DevOps: bringing everyone along on the transformation journey

Managing Director at Two Hills Ltd
Jun. 7, 2017
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
Surviving DevOps: bringing everyone along on the transformation journey
1 of 18

More Related Content

What's hot

How Agile Leaders Improve Results With The Responsibility ProcessHow Agile Leaders Improve Results With The Responsibility Process
How Agile Leaders Improve Results With The Responsibility ProcessScrum Australia Pty Ltd
Three Secrets of Agile LeadershipThree Secrets of Agile Leadership
Three Secrets of Agile LeadershipPeter Stevens
Olivia Liddell - Southeast PHP 2018 - Overcoming Your Fear of FailureOlivia Liddell - Southeast PHP 2018 - Overcoming Your Fear of Failure
Olivia Liddell - Southeast PHP 2018 - Overcoming Your Fear of FailureOliviaLiddell
Olivia Liddell - Nebraska.Code() 2018 - Overcoming Your Fear of FailureOlivia Liddell - Nebraska.Code() 2018 - Overcoming Your Fear of Failure
Olivia Liddell - Nebraska.Code() 2018 - Overcoming Your Fear of FailureOliviaLiddell
9 elements of the future of work9 elements of the future of work
9 elements of the future of workErik Korsvik Østergaard
Managing for Happiness by Jurgen AppeloManaging for Happiness by Jurgen Appelo
Managing for Happiness by Jurgen AppeloAgile ME

Similar to Surviving DevOps: bringing everyone along on the transformation journey

Creating meaningful lives.2Creating meaningful lives.2
Creating meaningful lives.2Tedy Stoyanova
Jak być zarąbistym developerem w oczach szefa i ... klientaJak być zarąbistym developerem w oczach szefa i ... klienta
Jak być zarąbistym developerem w oczach szefa i ... klientaWojciech Seliga
 The Change Challenge  The Change Challenge
The Change Challenge Lois Kelly
Retaining Employees in the UpturnRetaining Employees in the Upturn
Retaining Employees in the Upturnkatesweetman
Organisational virusesOrganisational viruses
Organisational virusestheStrongMessage.com
Good to great strategic business planningGood to great strategic business planning
Good to great strategic business planningRandall Chase

More from Rob England

Business agility in Vietnam Business agility in Vietnam
Business agility in Vietnam Rob England
Managing agile teams v1Managing agile teams v1
Managing agile teams v1Rob England
DevOps 101DevOps 101
DevOps 101Rob England
Agile at work within industry and business v5Agile at work within industry and business v5
Agile at work within industry and business v5Rob England
Bringing humanity to work Bringing humanity to work
Bringing humanity to work Rob England
England 20181023 does18 usaEngland 20181023 does18 usa
England 20181023 does18 usaRob England

Recently uploaded

Knowledge graph use cases in natural language generationKnowledge graph use cases in natural language generation
Knowledge graph use cases in natural language generationElena Simperl
who we are - values.pptxwho we are - values.pptx
who we are - values.pptxLauraGarceran
Die ultimative Anleitung für HCL Nomad Web AdministratorenDie ultimative Anleitung für HCL Nomad Web Administratoren
Die ultimative Anleitung für HCL Nomad Web Administratorenpanagenda
Cloud Composer workshop at Airflow Summit 2023.pdfCloud Composer workshop at Airflow Summit 2023.pdf
Cloud Composer workshop at Airflow Summit 2023.pdfLeah Cole
Industry 4.0.pdfIndustry 4.0.pdf
Industry 4.0.pdfTery Lockitski
BuilderAI Proposal_MalesniakBuilderAI Proposal_Malesniak
BuilderAI Proposal_MalesniakMichael Lesniak

Recently uploaded(20)

Surviving DevOps: bringing everyone along on the transformation journey

Editor's Notes

  1. © Two Hills Ltd 2017 Created and published by Two Hills letterbox@twohills.co.nz www.twohills.co.nz PO Box 57-150, Mana Porirua 5247 New Zealand licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Content must be attributed to "© Copyright Two Hills Ltd www.twohills.co.nz” Images copyright CanStockPhoto.com
  2. reskilling yourself and others in this new age. In this improvement we transform the way we work.  DevOps provides the approach to improving our way of working, and the navigational stars to steer by (the unicorn exemplars to aspire to). Such transformation is essential to make people's lives better.  So be careful our attempts doesn't make  people's lives worse, or worse still damage the culture of the organisation. Let's ensure we lift everyone, or at least as many people as we can.  We can make life better, the results better, and  customer satisfaction better. David Habershon Dawie Oliver Jason Cox Scott Prugh And my own personal journey
  3. Generations ago, the career ambitions of an intelligent and ambitious geeky young man (we’re talking pre-women’s–lib) might well have included such demanding and technically advanced professions as steam engine driver or typist or telephone operator.  The technically inclined among their children and grandchildren aspired to be business machine mechanics, electricians, and then computer operators.  A generation ago, leading edge roles for young persons included programmer, or – for the elite – systems programmer or database administrator.  Then it was network administrator or communications architect or web designer. The relentless advance of the technological revolution over centuries creates an interesting phenomenon in the technical professions that doesn’t happen (at least as markedly) to other professional areas such as law or finance or even medicine: jobs become commoditised. In part this is because they become semi-automated, or at least the interfaces become easier to learn and use.  Database administration is not the arcane art it was with say IMS[1] or IDMS[2] [you kids go look them up].  Even Oracle is easier to run… slightly.  Anjd MS-SQL is a doddle, comparatively. At least as important is that the technical sophistication of each generation of workers stands on the shoulders of those who came before.  A typewriter isn’t any easier to use today than when first invented.  Word processing is much more complex and intellectually demanding than hammering away at mechanical keys.  Yet my son was using  MS-Word at age 6. The third factor at work is that elite specialist technical professions hide their IP behind a shroud of mystery and jargon.  They maintain a Masonic priesthood.  Only the invited get the training.  Over time this gets stripped away as the knowledge is taught in mainstream education.  Think MCSE. Fourth and last is that some jobs just fall from prominence as they get displaced by new technology: think CICS programmer.  Yes I know the few that remain command high prices but this is a market aberration because too many dismissed it too early and the IBM mainframe stubbornly refuses to die (might be something to do with the way it continues to offer efficient, effective, robust processing of transactions year on year).  CICS programming is probably not a smart career choice, and eventually the occupation’s value will fall to zero. There is a great risk exposure here for technical people.  One day you are the highly-paid hero.  Then your kids go to school, you build a new house, you change companies a couple of times… and you turn around one day and the salaries are falling as every kid out of college can do your job. This is a particular danger for those who launch out as consultants based on an extremely marketable skill.  That is fine if you are five years from retirement.  It is not so fine if you are young. The smart ones reinvent themselves.   They watch the trends, sniff the winds of change.  They take the opportunities that come along to learn new skills in the right directions.  They jump from the downhill side of one occupation’s lifecycle to the upward rise of another’s. So keep a weather-eye on your chosen occupation.  Have a plan for your career.  Make sure that plan doesn’t assume the value of your current skills will continue to increase, or even hold the same level.  Advanced technical jobs eventually become commoditised. [1] http://en.wikipedia.org/wiki/Information_Management_System [2] http://en.wikipedia.org/wiki/IDMS
  4. Questions Will your work be better in a year?  Better results? Better enjoyment? Are you working sustainably?  Can you keep working the way  you are indefinitely without accruing technical or cultural debt? Does IT deliver value faster than the business is ready for it?  Or is IT a constraint? If not, you need to be continually improving, as an individual, a team, and an enterprise. So What does a great day at work look like? How would your behaviour change when you trust me or someone else?
  5. There are times when people need a push. Judicious use of New tools as a driver for change Management decree Expose people to other worlds, create disaffection, pull for change Deep-ending: push them in the pool Change the policy and rules, and the related measurements Formal re-organisation to destabilise resistance Make sure it is judicious: apply the nudge only at times when minimal intervention will have maximal impact. Intervene: engage with nay-sayers, work with problem people.  “Run to the fire” - Meg Whitman, HP Give them opportunity, hear their story, empower them,.
  6. Change at a human rate. There is a need for management and change agents to be cognisant of the human rate of change: it is measured in years. It takes a year to see early results. The normal distribution: People change at different rates Some people need time to process and absorb new ideas. Some people can imagine, others need to see and touch it. That's ok: embrace diversity.  Welcome those conservatives who put a brake on some of our wilder ideas, and who stress test all of them.  Good ideas grow stronger when challenged: forge them in fire. In legacy organisations we have opportunities for conservative staff to have time to change.  Legacy systems and ways of working remain in parts of the enterprise for a while Give people time to understand and to choose to change.  At least a couple of months.  Some people need years.  Some don’t get it until after they leave.
  7. The irony of taking a big-bang, one-shot approach to Agile transformation seems lost on some people.  Iterate, increment, explore, experiment. There are times when the organisation needs a nudge, when a JFDI (Just Do It) approach is required,. But in general we should move incrementally forward, learning and adjusting as we go.  Anyone who says they can design, plan and predict large scale organisational change in advance is delusional.  We’re not psychic. Formal reorganisation is something we especially shouldn't rush into.  Separate the formal structured frontage work structures: use virtual teams, secondment, and other collaborative mechanisms to experiment with new ways of working before making any formal changes.   Make change as gradual as possible so as not to disrupt culture (unless it needs disrupting).
  8. Modulate the level of disruption, don’t get ahead of the teams. Give them space and time. Circle back constantly to pick up those falling behind, and if necessary slow programs down to let them catch up.  Check in with teams, MBWA. It is easy for a few early adopters to get all fired up and race off in the bus. Constantly circle back to ensure people are coming along Check your passion.  Don’t go full steam ahead. Don’t read into other people your own level of understanding.
  9. Hostility is a good thing.   Welcome it.  Passive aggression is far more worrying a signal.  Once someone engages emotionally with you, even if negatively, they are on the journey to positive engagement.  They have moved from zero engagement.  Remember models such as Kubler-Ross:
  10. Empowered people blossom.  let them know it is ok to experiment, to fail, to take initiative, to lead.  Many people are "victims of the system": they behave the way they do because of the unreasonable position they are put in: if you put people in an unreasonable system you will get unreasonable people. What are they like outside work?  Maybe they are not being their authentic selves at work.  Change the system, change the mood.
  11. The enterprise has a duty of care for its staff: to ensure as few people are left behind as possible.  It seems like 5%-20% don’t make it. Management’s role is to coach, develop, offer opportunities There is self interest here too: dont lose valuable skills and knowledge. People are on the bus or off the bus, but don't let anyone go under the bus.  Identify, support and welcome those who don't want to come along: make their exit graceful, painless and courteous.  They are doing you a favour. Ensure there are cultural change programmes and enough staff training.  Ensure inclusion and investment.