 I have Jerry and Gautam here from Solutions IQ who would be helping us in this today's session. And I hope, I mean did anyone of you get any intimation to you know to carry your diving suits? No? Okay, don't worry even if you don't have, it doesn't matter, we'll really explore a lot in this one hour. So what I would be doing in this one hour is I will make you all to really deep dive into this limitless sea of retrospectives which has been one of my interest area for a couple of years. So I am Madhvi, I am from Solutions IQ, I am from Hyderabad and I work as an agile consulting coach for SIQ. So that's about me and Jerry would you like to just introduce, okay, so Jerry is our no he is a coach and he is agile consultant at SIQ, he is CSC so he will be helping us in this session too. So how I have divided this one hour session is the first 15 minutes I would be doing a retrospective surgery where we will talk about the common symptoms, the common smells that we come across while doing the retrospectives and what was my approach of tackling them and then the remaining 45 minutes you all would be doing a retrospective surgery wherein I will be giving you some real life example scenarios and you will play with it, okay. So retrospective surgery, why am I calling it surgery, any thoughts post-mortem, okay, any other thoughts, why surgery, yes Jeff, okay, good, thank you, so difficult, good, so assume no you have a patient suffering with the diabetics and he has a tumor in a hand, okay and he comes to a doctor, what would a doctor do, would he directly take him to the operation theater and operate, no right, what happens if he does that, that might be his last day, right. So what does a doctor do typically, he tries to assess, he tries to do some preliminary investigations, find out the background of that particular person, what are his ailments, get some preliminary information and then he will suggest a suitable surgical procedure that will suit him, right. So that is the same case even in software engineering, when we are working with teams when we are trying to you know use some method or a technique, understanding the background and the context of the teams is very, very important. So we as crumb masters and agile coaches when we are working with the teams we need to really understand what is the context, what is the background, what is the situation that we are posed with and then try to use a suitable technique or a method that will actually suit the given scenario, got it.