 things that the speaker can actually make it. So what we have decided to convert this into is three lightning talks And I think three of them have already signed up here. So we'll just go one after the other It's a five minute talk per person after five minutes I will the timer will actually go off and you're supposed to get off the podium, right? And we have three tomorrow also. There's one more slot like this where we are doing more lightning talks So if you have more ideas, you want to come up and speak for five minutes Please do come in this room during that time. So actually on the schedule It does show that there is a lightning talk session tomorrow. Okay, so without any delay, I guess we go And if you want to do you can do Hello Yeah, I like so I just wanted to you know share about what actually success means in an agile world So, you know in a waterfall world we define success in a lot of terms like you know delivery time and Lot of funders are there. So basically So how do you define success? So I read a book like the art of agile development and in that they have defined three types of success So one is organizational success and one is technical success and the one is a personal success so and three of them are equally important because Without a personal success, you know, you cannot motivate yourself and you cannot you know motivate your in a team and employees and without a technical success your one day or the other your project is going to you know break without because of its errors and the last the personal success and Last the most important thing the organizational success the organizational success is the key factor because you know Organization is funding for your project and you know like the value you provide to the organization through the you know Your work is the most important thing Because if you don't provide any value to the organization then you know whole purpose of doing that project itself is of you know no use So and how agile help us. So, you know like For organizational success and technical success agile, you know provides us various methodologies like you know scrum and XP and all those things because One of the things for organizational success is you know You know if you are creating it, you know website for a particular concept and by the time you you know You go through all the processes and finally deliver the project if there are you know a number of other Participants, you know in the market then you know the profit what you thought of getting initially would have you know You'll never get that profit. So instant, you know deliver the most, you know valuable things and then you know like The most liquid features and then add on based on a customer feedback and user feedback then it will be more Valuable because you need to change You need to you know adapt or you need to change the requirements of the market and make sure the Organization gets a value to the delivery of that project and then comes a technical side the technical side is You know, it's also very important and so, you know, let so the XP practices So helps you a lot in you know Making sure the your code is better and you know, you understand it. Well, and you you know The court should be strong enough and free of errors and all those mispair programming and all those XP steps will come into that and last but you know like Also important thing is the personal Success part, but you know like unlike organizational success and the other one technical success agile doesn't provide much you know like methodologies or you know practices to get Personal success, but what I feel is like, you know, you actively participate in all the you know methodologies and all the things you follow In the other things, you know either experience that you get you can take forward. I know that will be a very good, you know Learning curve but and so Actually, what I would like is you know if I had time so I would So like to hear and learn about How within your scram teams you or within your you know organization within your agile project How you try to get that motivation? How you try to get the personal success because that is something which noticed not defined like the other things so you can Talk to me after this or you know, I have a blog called Java jee.com So you can just I have This as a small blog In the extract session so you can just come into it or just talk to me or Share across what you do for you know, like getting that personal success. It's Chad Wildingdon I work for ThoughtWorks and We just only announced the day before yesterday that one of our products go Is now on the path to be open source and is freely available And I wanted to tell you about why that's actually a great thing and why it's important and why we did it So I think most people in the room probably know what continuous delivery is if you know what continuous delivery is Can you raise your hand? so Jez Humboldt is here and has obviously with David Farley written a book about how to Improve your software development processes such that your code is always ready to be in production and how that changes Kind of the cycle time of getting an idea and something built and putting it out for customers to use Well when Jez was working on that book He was also building a product and we built a product to support the ideas that we thought were really important So deployment pipelines as a concept this idea that you want to build code You want to integrate it and test it like you would do in CI But then you want to do a bunch of other things to it as it goes down to production So you may want to do integration tests in a completely different environment Or you may want to do security testing or you may want to check that this Version of a service works with another version of a service or it's dependent on this component There's a ton of different things that you do and actually making a Bit of code actually be ready to be deployed in production and go helps you automate and Control and manage all of that and give you great visibility into it So we open sourced it and we did that because we thought okay CD is really important We want see you be meet mainstream we want every team on the planet to be doing continuous delivery and Thoughtworks has a kind of history of thinking that way with continuous integration It was a practice a manual practice, and then we built cruise control, which is the first CI server So that people could actually do the practice for real and we feel that goes the same thing for CD We feel like it's the tool support in the infrastructure to do it So it's open source you can go check it out. You can download it for your project You can start using it just to do CI as a basic thing, and it's at www.go.cd And the code is not available yet, but it will be and we want contributors So if you've got an itch to scratch and you're thinking about wow, we're doing some dev ops in my Organization and we've got a bunch of different things going on and wow, it would be great if go supported this We love for people to contribute their time and their code and their thoughts. So That's it nice Why are you following a giant? Because it's tradition. It's trendy Okay, so Actually being geek is sometimes expensive. I'm not a geek yet, but I would like to be a geek So when I looked at most of the gigs they were using Mac So I bought a Mac and then I decided okay till I became a geek at least I caught on Mac Okay, so the warning so yesterday I was thinking myself as an intermediate in agile and I've reduced my level to begin after some speaks so Basically some of the things which I might talk here Might not make sense. Okay, so bear with it The problem we see is when we start practicing agile as tradition or as trendy because it's trendy or Because it looks geeky to practice agile Is will be tailoring the practices to fit into our comfort zone Will not be really understanding or will not be really looking at how we had to do the things are what's important What's not important, but mostly because it looks trendy traditional and geeky will tailor fit it to our comfort zones For example TDD it's all about how we do it Right, you can make a test pass if your intention is just to make the test pass Instead of going into why that test is failing because of race conditions or if you just increase the timing Or if you put a delay if the test passes, there are a lot of ways of making the test pass But it's how we do it. How do you basically why do you want to or how do you uncover the? butts inside and Basically along with agile It's very important for us to consider the continuous improvement aspect right people practices and performance this forms a triangle It's very important for us to consider this aspect and have a feedback mechanism and work continuously on it If you take for efficiency quotient as an example Why do you want to stick on to that? It's not your spouse to hang on forever, right? It's just a efficiency quotient. Why don't you move on it? Why don't you move further ahead on it? Why don't you look what's your efficiency quotient now and why don't you do something to increase it? Why don't you talk about reducing the turn around times? So basically I believe whatever you do if it's not personal it's not hundred percent basically you won't be putting hundred percent any work And I very much firmly believe that the value stream in place is the value stream You can deliver if you don't have the right value stream in place Don't even expect to deliver the value stream to the customer So usually it will be always less than the whatever value stream you can deliver it will be always less than the value stream in place That's how the That's the fact actually So when you start practicing agile, so you should be ready to face the challenges, right? It's it involves lot of human factor So you should be Ready to you know, you should be ready to face those emotional challenges and you should be ready to convince people Somebody will be ready to do the things somebody will not be ready to do the things that's a fence criteria becomes big bottleneck over there and The least thing you had to do here when you want to practice agile or when you want to practice anything is at the end, you know don't lie to lie to yourself at least be open to it and see where you stand and Know how exactly you're improving things and stuff like that or how it's helping you or how it's not helping you That's very important aspect, right? You should be able to make a progress and that's the reason we all here today So you want to learn something and we want to move on from where do we exactly stand? otherwise, you know, you just basically like if you are following agile for the sake of tradition or For you know for the sake of just because it looks trendy or for the sake of you know It's it's cool and it's geeky to follow agile We just look like the same way. I look like here today Anybody can have any kind of feeling about me right what this guy is doing here. This is agile international conference and he's standing here and With all these funny attire and stuff so if you're following agile for this for the sake of tradition or for the sake of You know being geeky or being trendy you exactly look like the same way. I look like today So understand it and then you know Follow it analyze it think about it come back, you know criticize it criticizing is very important aspect for us to go forward criticize it Thank you You