Migration to Cloud is the need of an hour as it brings in the required agility to the way the applications are built and hosted. With ever changing business needs, Cloud enables the agility to deliver high quality software quickly and that too consistently. In the current market scenarios, it provides significant benefits to the organizations to be able to respond swiftly to changing business needs.

As a seasoned technologist, this talk will be my experience sharing on migrating a business critical enterprise application to be Cloud Native. It will allow me to take you to our journey and share our experiences/learnings on the way about how it brought a change in our mindset while designing the application to be fault tolerant and resilient to failures, what are the processes/tools that worked for us, what are the challenges that we faced and overall what have we actually achieved out of it.

All in all how it moved us one step closer to DevOps :)

We all know the importance of validating a feature before committing to getting it built. Validating assumptions help in avoiding the most frustrating and common problem – building something that nobody wants. However, validation is easier said than done. Building the right feature before we think of building the feature right is the key.

Being Agile, we always try to leverage the quick feedback loop and adapt based on the end-user feedback. That’s good but it should not be used to validate the assumptions and that too after implementing a feature based on that assumption. It’s very expensive 

A more powerful and productive technique is to leverage Specification-by-example in defining and discovering requirements collaboratively with end-user, even before start working on the feature.

This talk will focus on highlighting key aspects of effectively adopting SBE technique based on my own experience leveraging it successfully over and over again. It not only helps in grooming the feature requirement to tell a clear , simple and compelling story but it also helps in removing what is not needed.

Being Agile developer, have tried & tested various flavors of pair programming over the years while working in highly motivated self-managed team. Some experiments worked while some worked better :)

This talk is about sharing the personal experience of practicing promiscuous pairing which allowed the team to be always in the beginner's mind state and being able to push the boundaries consistently.