Welcome to the crazy world of Dev-Ops, where the tales span the spectrum from gruesome, grizzly to the heavenly and flowery bliss!

The silo’d structures, the agonizing buy v/s build debates, the departmental handoffs, tooling and of course the cultural barriers, which all add fuel to the story unfolding in our brave new dev-ops world. But sometimes there are silver linings and the heavens part way for the shining stars to reveal their true glory.

Join our session to listen to the tales of our (not so) successful dev-ops, and learn the lessons from our experiences.

 
4 favorite thumb_down thumb_up 6 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Dev-Ops Introduction and Challenges [5 minutes]

         The challenges would includes the following broad categories -

        * Collaboration – How to change behaviours and build bridges across Dev-Ops teams?

        *  Process Flow – How to identify bottlenecks and amplify awareness across Dev and Ops?

        *  Technical – What technical changes (including automation, tools, architectural etc,) are required to support this new culture?

        *  Metrics – What to measure (or not to measure)? What improvement experiments to run towards continuous improvements?

  • Tales from the dev-ops trenches [10 minutes]

* Collaboration – How to change behaviours and build bridges across Dev-Ops teams?
The high level changes required for bringing about Collaboration required using multiple levers, including Systems Thinking and TOC, telling compelling stories to both parts of the organization, and socializing at multiple levels with senior management boldly coming forward to show support.

* Process Flow – How to identify bottlenecks and amplify awareness across Dev and Ops?
The end to end process flow emphasised delivering Value to the customer, and primarily used value stream mapping (vsm) to identify bottlenecks, and socialize the Ops pain points across the dev teams. The collaboration track ensured Ops participating early in the life cycle as a valued team player and providing insights to development.

* Technical – What technical changes (including automation, tools, architectural etc,) are required to support this new culture?
Release Management and Provisioning automation made top priority, with consistent tooling across projects, and leverage scale efficiencies. Early stage architectural checkpoints expanded to include Ops related metrics with Change Agents at multiple levels enrolled for consistent messaging and empowerment to increase awareness early in the SDLC.

* Metrics – What to measure (or not to measure)? What improvement experiments to run towards continuous improvements?Simple metrics made visible across the board, and some of them included Cycle Time, MTTR and built in feedback loops for quantitative and qualitative removal of impediments.

  • Lessons learned [5 minutes]

 

Learning Outcome

  • What is Dev-Ops and why it is needed
  • Understand the new reality for Technology and Operations teams
  • Gain insight into the problems solved, new problems faced, team skill gaps
  • Impact on business and change in organization culture
  • How-to apply some of the lessons learned

Target Audience

Dev-Ops engineers, Ops engineers, Technology engineers, Operations Manager, Technology Manager

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Asheesh,

       While I appreciate the intro, you mark this topic as advanced and I am trying to find out what in the talk is advanced.   Has this been presented before?  If so, may I see the previous deck?  There isn't much to go off of in your outline or abstract.

    Best,

    Joel

    • Asheesh Mehdiratta
      By Asheesh Mehdiratta  ~  2 years ago
      reply Reply

      Hi Joel,

      No this experience report has not been published till date, and the hence the deck is not available. To elaborate - this report will be a compilation of experiences across multiple teams, globally distributed, of varying sizes and different levels of project complexity, and who are currently at various stages in their DevOps journey. To give a little flavour, the talk will aim to (un)cover the following questions faced by each team, and their lessons learned:

      ·         Collaboration – How to change behaviours and build bridges across Dev-Ops teams?

      ·         Process Flow – How to identify bottlenecks and amplify awareness across Dev and Ops?

      ·         Technical – What technical changes (including automation, tools, architectural etc,) are required to support this new culture?

      ·         Metrics – What to measure (or not to measure)? What improvement experiments to run towards continuous improvements?

       

      The talk does not cover the DevOps basics, and hence can be covered under intermediate or advanced tracks. Please suggest if marking this as Iintermediate make more sense. and I’d be happy to make the change.

      cheers,

      Asheesh

       

       

      • Joel Tosi
        By Joel Tosi  ~  2 years ago
        reply Reply

        Hi Asheesh,

           Thanks much for the reply.  I understand the choice of tracks now, so thank you much for that.  

        In the 'lessons learned' you called out above, I appreciate the 4 main points.Could you add those to your session abstract as it would help people reading about your session to have  a better idea about the session.  Also, could you elaborate on them some - you bring up points but don't mention anything, i.e. how did you identify bottlenecks and what did you do about it?  What was challenging about that?

        Best,

        Joel

        • Asheesh Mehdiratta
          By Asheesh Mehdiratta  ~  2 years ago
          reply Reply

          Hi Joel,

          I have updated the session proposal now with additional details as suggested. Thanks much for your feedback.

          best,

          Asheesh

  • Sonik Chopra
    By Sonik Chopra  ~  2 years ago
    reply Reply

    Hi Asheesh

    Thanks for the proposal and i am sure the audience will benefit from this considering you will be sharing the real life examples. With two speakers for this big topic, I would recommend it to be a bigger session rather than a 20 mins one.

     

    Regards

    Sonik Chopra

    • Asheesh Mehdiratta
      By Asheesh Mehdiratta  ~  2 years ago
      reply Reply

       

      Hi Sonik,

      Yes, the proposal is a little tight for 20 min's and can be easily expanded for a bigger time slot - 30/45 mins. Hope that helps.

      best, Asheesh

       


  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Krishnamurty VG Pammi - 6 X 2 Planning Errors in Scaled Agile Delivery Model

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Beginner

    2 major errors across 6 agile planning events give us 12. Learning “what not to do”, can sometimes help us identify risks early in the cycle so that, as a team, we can effectively respond to these risks.

    Agile planning happens at multiple levels. In scaled agile delivery model, effective outcome of one planning event can influence the other significantly either positively or negatively.

    Come and learn top 12 experiential insights. These will help you alert your teams on “what not to do” during Scaled Agile Planning events. I tried capturing top 12 errors across 6 planning events namely Strategy Planning, Portfolio Planning, Product Planning, Release Planning, Iteration Planning and Daily Planning.

  • Liked Prasad
    keyboard_arrow_down

    Prasad - Speed 2 Value.. helping large Enterprise IT to be in the game..

    20 mins
    Experience Report
    Advanced

    Technology has blurred the lines between the digital and traditional methods of dealing with a consumer of any Global Enterprises. The Business Process and IT is no more separate, in most of the industry verticals the Business is driven by IT.   Constant Innovation around IT has become the new normal to the Enterprises to meet rapidly changing consumer expectations and behavior dynamics.

    More connected consumers, automated processes, and sophisticated analytics place unprecedented demands on IT functions. Many Enterprises are struggling to cope, and they seek to deliver on new demands by adding piecemeal elements to their existing operations. This is easier said than done. Reinventing the IT function at Global Enterprise requires far-reaching changes, from talent to infrastructure, tools, delivery models, partnership model.

    This experience report  brings strategy of 2 speed IT, through which Infosys helped its Global top 10 clients to 'renew' its IT related to Digital & Mobility space using Agile as a key lever.

    This session gives you experiences, practical on the ground challenges, stakeholder and vendor complexity and approach and journey towards Speed 2 value. Also I am pairing with Alok Uniyal who is senior leader at Infosys and a CIO coach who helped 50 plus clients to transform their IT organization in last 20 years.

  • Liked ShriKant Vashishtha
    keyboard_arrow_down

    ShriKant Vashishtha - Distributed Agile Patterns

    60 mins
    Talk
    Intermediate

    Way back in 2008, when I started working in Agile, there was enough material available on Scrum and. However when it came to distributed aspect of it, people were still struggling with it. Based on working for years in this fashion, I realised that communication, trust, transparency and innovation are the core fundamental values towards successful distributed Agile implementation.

    In other words, as most of the problems were caused by softer aspects of skills (misunderstanding, miscommunication, non-availability of people, mistrust etc), humanizing the distributed team experience looked like the key for successful distributed Agile implementation.

    Based on working with distributed teams over the years, we discovered some distributed Agile patterns. Some of them got blogged from time to time. Those already available in form of blogs are as follows:

    The session is to share the these patterns and more (when to go for distributed Agile and when not etc)

  • Saket Bansal
    Saket Bansal
    Lead Trainer
    iZenBridge
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Why organizations are adapting towards agile? Is it to get most out of their resources or is it about doing the right thing?

     

    Traditional mind set of achieving high productivity and using resources efficiently does not change easily, even when organization moves to agile they remain more and more worried about the team velocity. When I meet agile practicing companies or I attend event on agile I find that most of

    the focus is on delivering product backlog efficiently. We see lot of talks on how to make team more self-organizing so that they can do the things faster.  Even after moving to scrum or agile we keep ignoring the warning

    “There is nothing so useless as doing efficiently that which should not be
    done at all.”  —Peter F. Drucker

    When most of the organization starts with agile they takes it as an engineering process, and most of the team focuses too much on velocity, while to get maximum out of agile we need to look at Enterprise Agility, we need to look at an organization’s entire value stream—from idea to implementation, from concept to consumption.

    My talk would be focusing on need of organization agility and will introduce one of the monitoring tool “Life Cycle Profitability “which can help organizations in getting answers of questions like :

    • Should we delay the release by one month to fix the defects ?
    • Should we reduce the cycle time by adding one more team?
    • Should we delay the release to add functionality?
    • Should we delay the project by one month to get more innovative ?

    Life Cycle Profitability is based on principle “Take an economic view” introduced in book:The Principles of Product Development Flow , Donald G. Reinertsen . In my talk I will be showing how we can convert proxy variables like cycle time , velocity , technical debts  into Life Cycle Profit.

    I presented part of this concept in one of the conference and got good response, but I will create fresh presentation for this talk, since this time I will put more focus on expanding the model to calculate the Life Cycle Profit.

  • Liked Asheesh Mehdiratta
    keyboard_arrow_down

    Asheesh Mehdiratta - Will the Real Slim Shady please stand up?

    20 mins
    Talk
    Intermediate

    Guess there's a Slim Shady in all of us…but the real slim shady - Product Owner role - today is mostly ignored and misunderstood across most organizations. This talk highlights the confusion and the need for recognizing the product owner role as a ‘first-class’ citizen across the industry.

     The session will help you take a closer look at your current product owner team, and compare with an ideal product owner role, and in the end suggest possible ways to align your product organization better. If you are already a product owner or managing a team of product owners, you need to join this conversation and pick and/or suggest some of your own remedies.

  • Liked Asheesh Mehdiratta
    keyboard_arrow_down

    Asheesh Mehdiratta - Self Organizing: How to Lean-in to difficult conversations?

    20 mins
    Talk
    Advanced

    Leaders today are looking at “self organizing” agile teams to WIN ALL the battles on Auto-Pilot. Nice try is all I can say !!

    ...though some teams surely do succeed (lucky guys?).  But most teams are not so lucky, and get constrained by the organizational systems, processes, boundaries, and need an outside-in perspective or a divine eye to kick start their next improvement journey. Sometimes a leader takes on this divine role to guide them on this journey.

    This talk aims to provide the leaders a toolbox for using Lean conversations, to spark their next team improvement journey, by designing improvement kata’s, while slowly inching the team forward towards nirvana !! Divine Bliss !! .... So if you are a leader looking at learning and implementing the simple techniques of guiding the team on a self improvement cycle, leading to true self organizing team, join us.

  • Liked Fred George
    keyboard_arrow_down

    Fred George - Enabling Emergent Technologies

    Fred George
    Fred George
    Consultant
    Fred George Consulting
    schedule 2 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    The latest new, cool tool comes along. Will you be allowed to use it? Probably not! So how can you change that?

    This presentation looks at the introduction of new technologies at three companies, The Forward Internet Group in London (a start­up originally, now grown to 400+); MailOnline, the online version of the Daily Mail newspaper from London (a very old organization with an existing IT shop); and Outpace, a Silicon Valley startup.

    In both cases, Programmer Anarchy was introduced. This managerless process (not unlike GitHub in its value propositions) empowered the programmers to make technology choices and to freely experiment with new technology. In the case of Forward, massive growth and profits ensued. In the case of MailOnline, re­development of core systems into new technology has been launched, and expectations significantly exceeded.

    This presentation will touch on the various aspects of implementing Programmer Anarchy at MailOnline:

    • Team building through programmer training

    • Pilot project without managers, BA’s or dedicated testers

    • Reinforce the model with new HR structure emphasizing skills over titles

    • Create self­organizing teams of 5­8 developers (multiple such teams)

    • Charter teams with a specific project, and let them deliver

    • Avoid artificial schedule pressure

    The intent is to provide a possible roadmap to get your latest technical toys moved into production systems.