Ashish will be presenting the following session
filter_list help_outline
  • Ashish Kumar
    keyboard_arrow_down

    Ashish Kumar - Confused Tester in Chaotic World #ChaosTesting

    Ashish Kumar
    Ashish Kumar
    Agile & Lean Coach
    Siemens
    schedule 1 year ago
    Sold Out!
    20 Mins
    Experience Report
    Beginner

    "You can’t legislate against failure, focus on fast detection and response."

    You can think this as a fairy tale story -

    As once upon a time, in theory, if everything works perfectly, we have a plan to survive the disasters we thought of in advance.

    But big Question is How Did That Work Out ?

    We are here to answer that Big question with our session.

    While it is possible to sit down and anticipate some of the issues you can expect when a system fails it, knowing what actually happens is another thing.

    This really depends on what your tolerances for failure are and based on the likelihood of them happening.

    The result of this is you are forced to design and build highly fault tolerant systems and to withstand massive outages with minimal downtime.

    The prevailing wisdom is that you will see failures in production; the only question is whether you'll be surprised by them or inflict them intentionally to test system resilience and learn from the experience. The latter approach is chaos engineering.

    The important aspect of Chaos Engineering is Chaos Testing.

    Historically, the emphasis has always been on mean time to failure (MTTF); working hard to extend the time between system failures, with little emphasis on how fast a failure could be corrected.

    In today's world, the emphasis needs to shift to mean time to recover (MTTR), minimizing the time it takes to recover from a failure.

    At a high level, chaotic testing is simply creating the capability to continuously, but randomly, cause failures in your production system. This practice is meant to test the resiliency of the systems and the environment, as well as determine MTTR.

    Adopting chaotic testing will help improve your MTTR, improve organizational confidence in the resiliency of your production environment, and it will also keep you out of tomorrow's headlines.

    A case study to showcase the real world how can we handle our failures By testing proactively instead of waiting for an outage.

    The product understudy over here is one of the key products serving the major contact center industries across the globe.

    The impact of outage in an contact center with 40K+ agents specially during peak seasons is huge. Contact center are considered as backbone of industries like e-commerce, telecom, travel etc. and dealing directly with people.

    How we ensured a seamless takeover between contact centers across the globes even if an entire high availability contact center goes down. The established calls in an scales of multiple thousand also recovers in fraction of milli seconds. And how this all was achieved by testing all the unknowns in an controlled environments continuously.

1. What got you started/interested in Agile?

I'm all about improving communication in teams and in creating the right environment for teams to flourish in, and I involve them in this journey; one where they can feel free and confident to learn, grow, question, challenge, and celebrate together.

2. What do you think is the biggest challenge faced by the Agile community today?

to ask for a change is easy, willingness to change is not and to lead a change is out of question.

This commitment from organization is missing resulting in failure of transformation in lack of sustenance.

To enable the sustenance is biggest challenge in my undersatnding.

 

3. Tell us about the session(s) you will be presenting at the conference and why did you choose those topics?

The prevailing wisdom is that you will see failures in production; the only question is whether you'll be surprised by them or inflict them intentionally to test system resilience and learn from the experience. The latter approach is chaos engineering.

The important aspect of Chaos Engineering is Chaos Testing and i wanted to highlight the same with few case studies.

 

4. What are some of the key takeaways from your session(s) at Agile India?
  1. Case Study - What we learnt with a leading contact center product in while testing in production 
  2. What are the advantages and challenges of Chaos Testing? 
5. Which are your favourite sessions at Agile India this year? (Sessions that you are looking forward to attending)

Shane Hastie - The Ethics of Agile Coaching

Jeff Patton - MVP and Why we confuse Building-to-Learn with Building-to-Earn

6. Any personal remarks/message you want to share with the Agile Community?

let's use the great platform of agile india to share and learn together what we are practising.

help