A lot of enterprises have trouble in starting to practice DevOps, steps like making a "DevOps Team" are common amongst large enterprises. Needless to say such teams see a lot of resistance, not only on the tooling but processes and practices front also when they try to practice DevOps. Starting to do DevOps is not as much about removing things from the system and put in something dramatically new as it is about creating an ecosystem based on well know principals of managing operations and the relationships between those who develop to those who manage. This ecosystem has to evolve into a state of being and is not built up by adding random pieces of automation or throwing in a new profile of engineers.

We need to simplify our thought process and look into the basics for the three ways, what is CAMS and how to go about bringing in all the four pillars into practice for benefiting from DevOps as a practice.

The talk aims at explaining how DevOps practices in-fact benefit from tapping into existing Lean, and ITSM practices hence making the transition with lesser heart burns and frictions. 

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This talk is organised into the following sections

  • What is DevOps?
  • The Three Ways
    • Systems Thinking
    • Amplified Feedback Loops
    • Continuous Learning and experimentation
  • CAMS
    • Building a Culture
    • Building Automation
    • Measure what matters
    • Sharing is not that bad after all
  • Where to start?
  • Some wisdom from
    • LEAN
    • ITSM

Learning Outcome

After this session the participants will have:

  • Understood the business value of improving the flow between Dev and Ops
  • Acquired a high-level understanding of DevOps including cultural, practical and automation aspects
  • Discussing the benefits and results realized by organizations adopting DevOps
  • Explored the relationship between DevOps, Agile, Lean and ITSM
  • Understand ongoing opportunities for knowledge about emerging DevOps best practices

 

Target Audience

Developers, Ops Guys, Project / Program Managers, Business Stakeholders

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Joel Tosi
    By Joel Tosi  ~  1 year ago
    reply Reply

    Hi Anadi,

        Thanks for the submission.  This seems very introductory - is there anything new or experience based in here?  Also, do you have any reference videos or slides we could check out to see your presentation style?  Thanks much,

    Joel


  • Naresh Jain
    Naresh Jain
    schedule 1 year ago
    Sold Out!
    45 mins
    Keynote
    Advanced

    On Agile teams, collaboration is the way of life. Our leaders want their team members to work closely with each other, have shared goals and even think as one entity. Why? Because we believe that collaboration leads to happier, more productive teams that can build innovative products/services.

    It's strange that companies use the word collaboration very tightly with innovation. Collaboration is based on consensus building, which rarely leads to visionary or revolutionary products/services. Innovative/disruptive concepts require people to independently test out divergent ideas without getting caught up in collaborative boardroom meetings.

    In this presentation, Naresh Jain explores the scary, unspoken side of collaboration and explains in what context, collaboration can be extremely important; and when it can get in the way or be a total waste of time.

  • Liked Vinay Krishna
    keyboard_arrow_down

    BDD - an effective way to collaborate among 3 amigos - Testing is just a by product

    Vinay Krishna
    Vinay Krishna
    schedule 1 year ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    A common misinterpretation is that BDD is another way to automate the functional testing or just a synonym to Acceptance Test Driven Development (ATDD). However, it’s not correct understanding. BDD doesn’t talk about testing rather it focus on development which is driven by expected behaviour of application/system. It helps to share the understanding by examples among three amigos (BAs, Developers and Testers) and helps to explore unknown. It describes what business/end users want the system to do by talking through example behavior.

    In this workshop, the actual concept of BDD is explained using case study of various real-time projects. It also covers the myths, challenges, benefits and best practices along with tools used to adopt it.