I have been meditating since quite some time now. Meditation gives me peace of mind. It allows me to be more conscious and aware of things around me. Interestingly, I have experienced the benefits in Coaching & Mentoring, in Testing and also in Automation activities on Agile projects.

In this talk, I will be sharing how Meditation helped me in Testing on Agile projects - while working on various activities that help my team build a Quality product. I will also be sharing experiences of the way we approach certain testing activities - and how that correlates to the conscious mind, or not! These experiences can be applicable to any role on Agile projects.

PS: I will be referring to some Meditation techniques that work for me. This is not about any religion / faith / practice.

 
 

Outline/Structure of the Talk

  • What is Meditation? Why do we do it?
  • How does this correlate to Agile Projects?
    • We will look at various activities done by teams working on Agile Projects - and how that can relate with, or not, with a meditative approach!

Learning Outcome

- An interesting correlation between Meditation & Agile
- Meditation can help get better at observing things around you, hence - get better in any role
- Meditation helps in technical activities too (include Test Automation)
- How Testing helps me become more Meditative! It may help you (in your role) too!

Target Audience

All Roles

schedule Submitted 3 years ago

Public Feedback


    • Liked Pooja Shah
      keyboard_arrow_down

      Pooja Shah - Release Status Analyser to bring more agility @ work

      Pooja Shah
      Pooja Shah
      Lead Automation Engineer
      MoEngage
      schedule 3 years ago
      Sold Out!
      20 Mins
      Demonstration
      Advanced

      Problem Statement

      Do you have a lot of automated Tests and so the lot many tests reports to analyse before taking call for release?

      Plot: Any huge impacting micro-service based product/project for which enormous tests have been already automated and your continuous deployment process requires all of those tests in "PASSED" state. Due to high traffic most of the day, releases are deployed at non peak hours. Imagine decided deployment time in production is 5 AM. (The feature and regression testing is done already but there are always some small last minute changes, so it’s better to have a double check on the frozen code to release)

      At 1 am: Final automated sanity checks start executing  

      At 3 am: Get the results, release engineer/ devOps gets notified of the state of the release, she/he looks at CI board and see several green and red builds. He/She now 1 by 1 opens all red builds, clicks on individual reports, console, screenshots....  more red builds- more time to analyse it...

      At 4.30 am: After gathering report on which test failed for what reason & who should be looking at them, she/he calls up respective owners to look out and state the reasons & take a call on the release

      At 5 am: The service owner says "let’s revert my feature to previous version and take the release live"

      Release Engineer again starts searching for files/mails where the last stable version is stored, spending more time again. It’s 6 AM now, she/ he deploys last stable service versions, runs the failed tests -> integration tests ...

      it already 9 AM, wooosh!, time runs really fast. Can't release now, peak traffic time.............

      Do you share the same pain?

      Before giving a +1 for the release, it becomes essential for the QA folks to provide proper feedback as quickly as possible. At the same time assessing n number of reports becomes an additional tedious task. So definitely there should be 1 dashboard which nicely displays the status with transparency and anyone should be able to tell whether release is good to go and if not, then why not. RSA which I have created on top of open-sourced technologies is a small effort towards achieving the same. Will take you through a live demo and discuss on how you can use it to meet your needs.

    • Liked Anand Bagmar
      keyboard_arrow_down

      Anand Bagmar - The What, Why and How of (Web, ...) Analytics

      45 Mins
      Talk
      Intermediate

      Analytics is changing the way products and services are being created and consumed.

      In this session, we will learn

      • What is Analytics?
      • Why is it important to use Analytics in your product?
      • The impact of Analytics not working as expected

      We will also see some techniques to test Analytics manually and also automate that validation. But just knowing about Analytics is not sufficient for business now.

      There are new kids in town - IoT and Big Data - two of the most used and heard-off buzz words in the Software Industry!

      With IoT, with a creative mindset looking for opportunities and ways to add value, the possibilities are infinite. With each such opportunity, there is a huge volume of data being generated - which if analyzed and used correctly, can feed into creating more opportunities and increased value propositions.

      There are 2 types of analysis that one needs to think about.

      1. How is the end-user interacting with the product? This will give some level of understanding into how to re-position and focus on the true value add features for the product.

      2. With the huge volume of data being generated by the end-user interactions, and the data being captured by all devices in the food-chain of the offering, it is important to identify patterns from what has happened, and find out new product / value opportunities based on usage patterns.

    • Liked Pooja Shah
      keyboard_arrow_down

      Pooja Shah - Can a bot bring Agility?

      Pooja Shah
      Pooja Shah
      Lead Automation Engineer
      MoEngage
      schedule 3 years ago
      Sold Out!
      20 Mins
      Lightning Talk
      Intermediate

      A typical conversation on a release day:

       Everyone on team running around with questions like how was it merged without review? why wasn't it caught earlier in the automated tests? is it not test covered? And the blame game starts which turns pleasant office premises into a really chaotic one as all starts behaving like Shakuni the bad critic ..............

      Does this conversation sounds familiar to you?

      yes, in fast paced organisations like us it is a burning problem. And we really wanted a monitoring system in the test phase itself that too using the same tools we use regularly and hence not costing us anything extra. This brings Agility within the teams by having everything & everyone on a single platform and help everyone feel what’s there in the black box.

      Points needed to ensure:

      1. Prevent direct push to the branches we want to protect
      2. No commits to go inside without tech/product review
      3. A common transparent place to quickly go through all commit links/description with timestamp to quickly know which can be the culprit commits
      4. Alerts to respective team members for any suspicious activity done by anyone
      5. Personalised alerts to the committer for reminding to follow the release process
      6. As the team size grows, assisting each one in the team on release process & progress is really a repetitive task and an unnecessary dependency

      In this talk, we will discuss about unleashing the power of Github & Slack to create a interesting code monitoring and talking bot which keeps everyone in a team updated on a single platform.

       

       

    • Liked Smriti Tuteja
      keyboard_arrow_down

      Smriti Tuteja / Ramalingam sankarasubramanian - How a flawed CI/CD process can blow you off

      45 Mins
      Talk
      Intermediate

      Everyone is aware about the benefits which Continuous Delivery (CD) and Continuous Integration (CI) can bring to any organisation but nobody talks about the day-today obstacles where if the process of CI/CD not followed seriously, can turn out to be a myth/fallacy.

      Things can go wrong if following things are not properly designed/configured:

      • End-To-End Pipeline setup
      • Deployment Schedule (Daily vs weekly vs fortnightly deployments)
      • Two-way compatibility (Code vs Schema change)
      • Trunk based development vs Multiple Branches
      • Discipline around feature Flags
      • Deployment Downtimes (blue-green deployments)
      • Discipline around Test Automation

      Join us and learn the loopholes and the barriers in the Continuous Delivery/Continuous Integration process as we share our personal experiences.

    • Liked Krishnakumar Chinnappachari
      keyboard_arrow_down

      Krishnakumar Chinnappachari - Coaching lessons learnt during Enterprise Agile Transformation

      45 Mins
      Experience Report
      Beginner

      Our Agile Transformation journey started about 20 months ago. In this talk I am going to share some of the key challenges faced by me as an Agile Coach and how did I over come them. As a change agent you will learn few critical tips or tricks from my experience and implement them in your transformation journey at your organization. 

    • Liked Pranathi Birudugadda
      keyboard_arrow_down

      Pranathi Birudugadda - Enhancing Agile Team Dynamics with tweaks in our day to day tasks

      Pranathi Birudugadda
      Pranathi Birudugadda
      schedule 3 years ago
      Sold Out!
      45 Mins
      Talk
      Intermediate

      Agile Teams are known to focus on customer satisfaction. However, the agile principles go beyond software development. It’s a mindset for people who need a management approach that builds consensus quickly in a fast-paced environment. The biggest challenge today in software development is not technology. What actually still stumps us is the people factor. Software Engineering has tried-and-true answers for most of what enterprise systems need. How to enable several engineers working together to achieve effectiveness is still an open question. Attempts at answering it pop up every day from different schools of thought. The more we try, the more we realize a fundamental truth: people teams are complex.

      The Project Management discipline has discussed the subject of team building almost to exhaustion. Organizations are hungry for a checklist they can apply to make people work better together. The truth is that experience shows you can't actually build a team. Building implies you can make a big effort to create a stable foundation that stays up indefinitely. A more appropriate term for teams would be to grow, meaning to cultivate.

      When I look back at how I have managed to cope up with all those challenges in my early career days, I realized a few things and activities have certainly helped me do so.

      In this talk, I will be discussing a few practices that can be included in our day to day activities that would help to grow the team dynamics.