Can a bot solve or prevent human communication problems?
Room F3 - Track 3: Talks
Developer, Test Engineer, DevOps, Product Managers and CTOs' love it
In this talk, we will discuss an idea of creating a code monitoring and talking bot which has potential to prevent or resolve communication problems throughout the sprint (QA-release) cycle. We will also be sharing exactly how I leveraged the power of existing systems to create it and know how you can also use and create your own personal 24*7 guard/assistant for your team.
Why should you attend this:
Imagine, it is one of your Release Day and the code started breaking all of a sudden, tested features not working anymore, and it is going to take time to figure out whom to reach & people start passing the buck?
Experienced such stormy sail on your release day? Amidst all this, losing time for release deployment as the traffic on your product is peaking up or exceeding the deadline promised to the clients. Manual monitoring doesn’t look a viable/scalable solution? Yes, in fast-paced organizations like us, it is a burning problem. Do you also feel the same?
Eager to know how? Come let’s talk and take a sneak peek at how we are dealing with these at MoEngage Inc. And yes, get to start using the solution open-sourced in almost no time. Wait! Did I tell you it is open sourced too :)
~ A little attempt towards making healthier work culture and keeping the smart brains happier :-)
Outline of Talk:
The talk is about a bot which can help your team “preventing last moment panic moments” and so helps all the teams be on the same page: