To all technical members involved with building DevSecOps pipeline this talk is for you.

In today's competitive world, fixing problems in the pipeline is still a human task and how many times have we seen that when pipeline stops, notifications are sent out and then we wait........ for someone to identify, diagnose and resolve the issue. I am sure we have all been there and done that.

Is this good enough?

In my talk I will share some smart ways of infusing self healing into your existing pipeline. We all know it’s good to set thresholds and quality gates in the pipeline, so you can stop the pipeline when the threshold or the gate fails and notify appropriate stakeholders. But in this approach the problem is brought to the attention of the humans to take corrective action what if this issue gets self diagnosed and self healed by the pipeline itself!

Imagine that....

I will shows ways on how self-healing can be built into the pipeline by leveraging the data that gets generated from within the pipeline by converting it into information, and the information into knowledge, and the knowledge into insight to make intelligent data driven decisions and remediation.

11 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/Structure of the Talk

I will talk about some of the ways to implement self-healing feature into their DevSecOps pipeline to diagnose and remediate problems without human interaction.

Rough outline:

  • Introduction to the DevSecOps pipeline
  • Are Instant feedback loops good enough?
  • SMART ways to infuse Self-Healing into your pipeline
  • Benefits of data driven decisions and remediation
  • What next?

Learning Outcome

  • Data Driven decisions will never go wrong!
  • Limitation of Feedback loops
  • Why we need self-healing in our pipeline
  • Benefits and challenges of self-healing pipeline
  • Build your pipeline in small increments, think, Continuous delivery of continuous delivery pipeline

Target Audience

Attendees should be at least roughly familiar with their current continuous delivery process, or at least have a high level plan in mind.

Prerequisites for Attendees

Bring enthusiam!

schedule Submitted 9 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • George Dinwiddie
    By George Dinwiddie  ~  9 months ago
    reply Reply

    Hi, Rupesh,

    Your abstract seems long and rambling. Does it need to explain a thermostat? Missing in it is some indication of the appropriate audience for your talk. Who do you want to attend, what problem are they facing, and in what way will this talk help them solve their problem?

    The abstract is the place where you sell your session to the right prospective attendees. Help them recognize themselves and their situation, and tell them what benefits they'll get by attending. Give them enough information about the content to convince them that they'll get that benefit.

    On the other hand, the outline/structure is too thin to understand the session. The slides don't add much understanding of the content. And what is the "hidden secret?"

    The outline/structure is the place where you sell your session to the reviewers. Help them recognize that you'll deliver on your abstract. Give them details about the content and the way that you'll present it to convince them that you'll do a good job.

    See also for an independent description of submitting a successful proposal.

    • Rupesh Kumar
      By Rupesh Kumar  ~  9 months ago
      reply Reply

      Hi George,

      Thank you for your great feedback.

      I have updated my proposal with your suggestions.



  • 45 Mins

    Despite thinking that organizations are slow to innovate, innovation actually abounds at many companies. Kodak, DEC, and Xerox did not fail due to lack of new, cutting-edge innovation; they failed because their organizations were tuned to their traditional markets, and a failure to change their business models and organizations led to their eventual disruption.

    The key to achieving business agility lies in leadership that transforms organizations. Transformational leaders succeed by changing the system, leading with purpose, and steering from the edges. They own their responsibility and boldly lead their organizations into the future. As leaders, we can accelerate this evolution by enabling true self-management and team-based governance.

    Join Bob and Sanjiv to learn how leaders can transform organizations with a flatter organization structure, work anywhere flexibility, participatory profit sharing, and delegated hiring and firing. Explore the agile leadership journey needed for true business agility.

  • Liked Bob Duffy

    Bob Duffy - Fannie Mae's SDLC Journey from Waterfall to Agile

    Bob Duffy
    Bob Duffy
    Internal Controls Tech
    Fannie Mae
    schedule 10 months ago
    Sold Out!
    10 Mins
    Lightning Talk

    A well-defined Software Development Life Cycle (SDLC) is a requirement for many government institutions. However, the typical SDLC process is very "Waterfallish" by nature of it's phase gates and documentation requirements. This talk will explain how the SDLC at Fannie Mae has evolved as the company has transformed from a Waterfall to a lean Agile organization in alignment with Agile best practices.

  • Liked Matthew Kleiman

    Matthew Kleiman - Pair Programming: Better Than Adderall

    45 Mins

    Not all programmers are comfortable with coding alone for 10 hours a day. Matt Kleiman spent years programming inefficiently in a cubicle. His Attention Deficit Disorder (ADD) and other learning disabilities deterred his success on traditional development teams. Seeking out an environment that would nourish his strengths, he found Pivotal Labs. Pivotal's Extreme Programming practices empowered Matt. Attend his talk to learn how pair programming and test-driven development transforms ADD into an asset in the workplace.

  • Liked Leland Newsom

    Leland Newsom - Sprint with Agile, Deliver with DevOps

    45 Mins

    Enterprises want to deliver more value with higher quality at a faster pace. Many development teams have adopted agile frameworks to improve their ability to deliver software. This has led to a local optimization for the development teams and they have become good at delivering potentially shippable increments of their products, but from there, they typically see organizational constraints in moving it to the customer. The development organization is quickly adding features to the queue waiting to be released, but the operations teams are struggling to support fires in production, maintain stability, and provide the environments and infrastructure needed so development teams can move their new functionality forward. The operation team’s focus on stability usually minimizes the number of changes in production thus creating infrequent, large batches being deployed at a planned date. Can Agile and DevOps bring the development and operations teams together to remove the organizational constraints in moving the software to the customer?

    In this session, we’ll talk about the relationship of Agile and DevOps, not as an intersection, but as a progression of capability with development and operation teams working together to remove those constraints. We’ll discuss how using Agile and DevOps practices together, teams can release value faster, with higher quality, and in more stable environments making it safer to deploy.

  • Liked Beth Hatter

    Beth Hatter - Beyond Servant Leadership: The Evolution to Empathetic Leadership

    45 Mins

    The concept of servant leadership is nothing new in the agile community. Servant leadership shifts the focus of leaders from managing teams to empowering and supporting teams. But as the world continues to evolve, are we really forming the connections we need to have truly high performing teams? Empathy forms the foundation of connections between individuals, teams, and organizations, and is the key to successful in supporting the needs of our customers and society. To have truly high performing teams, we need to move beyond servant leadership to a more empathetic leadership mindset. So how do we recognize, nurture, and grow empathy and grow from Servant Leadership to Empathetic Leadership?

    This workshop will guide participants through several topics. We'll explore how empathy changes our thinking, how empathy and agile success relate, and how to build empathy within ourselves, our teams, and our organizations.

  • Liked Reha Malik Gill

    Reha Malik Gill - Examining the Agile Manifesto after 18 years- Is it resistant to change?

    Reha Malik Gill
    Reha Malik Gill
    Change Agent
    Fannie Mae
    schedule 9 months ago
    Sold Out!
    45 Mins

    In the February of 2001, seventeen independent- minded software practitioners got together and developed what we know as the Agile Manifesto. The purpose of the manifesto was to provide guidelines for agile adaptation in organizations seeking better and faster ways to develop software and to serve as the north star for teams, coaches, trainers and change agents seeking to implement the best agile had to offer.

    It has since been 18 years and the manifesto remains unchanged. Mainstream agilists and troupers are passionate about the comprehensiveness of the manifesto and believe that it is self-adapting to the needs of today’s software and solution development.

    So have things truly ‘changed’? Does the manifesto need a revisiting? Is it time to amend the agile principles and modernize them to today's growing software demands or is the manifesto truly adjusting and inclusive of all change?

    Let’s get together and refresh our understanding of the manifesto and the 12 original principles.

  • Liked Max Saperstone

    Max Saperstone - Test your tests: developer practices aren't just for developers.

    45 Mins
    The growth of automation testing in today’s software development organizations is changing the the way we test applications. Software development practices have matured over the last 30 years, to include all forms of testing to verify software quality. In the last ten years, there has been a huge spike in the adoption of automated tests, effectively replacing some of these manual testing practices, and supplementing many traditional testing activities. Many parts of the software development industry, however, are wary of replacing manual testingwith automated testing. Not only is there often a lack of confidence in the automation tests, many see automated testing as fragile, unmaintainable, and ultimately, something delivering a low return on investment. Max believes that by employing mature software development techniques, we can achieve robust, maintainable, tests, that deliver confidence of the application under test. In addition to discussing how to structure automated tests that are cleaner, more maintainable and efficient, developer testing, and deployment techniques can be used to programmatically verify test correctness. Drawing on his experiences building test automation, test frameworks and advising organizations to adopt test automation, Max will walk us through how to mature your test automation practices.