 I'll start, I'll start, I'll start, I'll start. Okay, today I'm, this one is I took, my map I took when I, Craig Rauman did the keynote. So he talked about scaling background and how may, sorry, and meaning of customer collaboration, so competitive game to, collaborative game and more, more, less, less, using those pictures and large-scale framework like this. So my mapping is just a note-taking technique, it's a radically growing picture, to keep one, keep your ideas in one big shape. Okay? What was my joke? I won't tell you right now, but I didn't think it was a good joke though. Yeah. And I'll, I'll show you when, oh, others, like this one. This one is the, I wrote about the design pattern. In order to remember those patterns, we use shapes, colors and things like that, so that your right-hand brain works well with the left-hand one and others. Okay? This is a plan of a project Christmas. I don't know if you have Christmas in this country. Okay, sorry. Let's say we have five branches, like when, what, why, who, where, result. This framework is called 5W1R. Do you know that framework? 5W1R? Yes, 1R, yeah. This framework is, I took from Busan's book, Tony Busan's book called Mind Mapping for Kids. It's interesting because result is very business-oriented framework, but not hell, but result. It's very funny. When, what, we are gonna do retrospective, we are gonna do keep, problem, try, retrospective, and after that we'll do the party, and why we're gonna do that, and who is attending the party, where to do that, and the result we expect is customer satisfaction, buildability, and those things like that. So keeping things in one picture and using shapes. As you know, right-hand of your brain is very good at colors, shapes, music, and smells and things very, your sense, your sense. Left-hand is very good at logics and orders. So right-hand of your brain working parallel signal processing to your brain, and you are one of the world at a time. And left-hand orders it to make a logic. So using ManMap, you can work, you'll work with your brains well. So I'm gonna show you one example of how you use ManMap. City library, meeting minutes. I wanna do this, okay? What I usually use MyMap when we use, when I use this in meeting, we take memo notes using this projector with the team, and this is the MyMap thing for my meeting notes. So it has time and place and attendees and conclusions part is not filled yet. To do is not filled yet, and agenda's going to be here. So when you start the meeting, you can add items while you speak and collecting ideas and discussion like this. So that everybody can be on the same page. And you can sometimes do add icons here. When you like topic 17, you add this icon, or at 16, you can add this cloud. Or if you have some items, 17 is very similar to topic seven, you can add those links and something like that. Because this is a tree structure, as you see, you can, sorry, you can drag and drop, I just copy that tree and I paste it into Excel. Why do you think it happened? It's like this. So when you see this, it's a tree structure because so you can have the center and time and place, attend the conclusion to do an agenda as a memo. So this can work as a instant note for the meeting. I will show you another example. This is a, sorry, some part is in Japanese, but this is a elitist or software qualities in six categories and other subcategories. It looks like a tree, right? So if you copy this, and I'll go into another mind map and I will say software quality. And I'll paste this, the qualities into this one. Where's the paste, edit, paste? Do you know what happens? It's like this. It's very natural way of treating trees. In mind mapping, you can move around those trees. If you think the security thing is not a functionality and it should be maintainability, you can just drag and drop this branch into here, which you cannot do in Excel. The tree structure, so it's like, works for me as a whiteboard. You can drag and drop your concepts and making groups and things like that. Okay, one last demo I would do if I have time. Who's next? Okay, okay, just one demo. What I'm going to do is to keep using, in agile project, writing UML is not very often. So what I'm gonna do is writing a mind map and you can drag and drop into use cases or classes or other concept diagrams. Okay, I will do this in this Christmas project but I'm not sure. Okay, so you can use a, I will use this use case diagram. You can drag and drop anything, actually anything from, okay, I can drag and drop who into, sorry, this is a class diagram. I will make an use case diagram. So that I can drag and drop this development team here as a actor like this and retrospective. This one here drag and drop as use case and then make a use case diagram. And those things here development team members is has a link to backwards link to this mind mapping so that you can trace your ideas between classes or UML diagrams and mind mapping. Oh, I'm running out of time so that's it. Thank you very much. If you are interested in my tool, please contact me or pass me your business cards or something, anything's okay. Thank you very much. A deployment pipeline is because that's what Go, our agile release management tool from ThoughtWorks Studios helps you with. Okay, so I'm sure in every project there are set of developers who are checking in code. What you desire is that all this code should be continuously integrated, run your unit tests, acceptance tests, at the end of it give you packages which you can easily deploy. So Go is a tool which helps you with that. So that essentially helps you orchestrate a deployment pipeline. What a deployment pipeline is essentially this diagram. This quickly tells you that. So there's a commit stage where you can compile your code, run unit tests, create your installers, then acceptance test stage which runs your user acceptance tests, functional tests. Now as soon as this is passed, you want to test out your product, right? So you can simultaneously deploy to two environments, one for UAT, one for performance testing, do all your testing there. And once you are completely confident that this is passing, you can deploy it on to production. So this is your basic deployment pipeline. So in this case, what happens is it increases confidence in your production readiness. So as soon as my these two stages are green, I'm confident that I can deploy to production. And it also gives continuous feedback, right? So at this point if something fails, I can immediately fix it here, run my pipeline again and so on. So it's very fast feedback for everybody on the team, not only developers, your testers, managers, ops people, everybody immediately can see what is going on in my whole life cycle. So that's what Go helps you do. Yeah, like I said, fast automated feedback on production readiness of your applications. Whether you change your code or whether you change your configuration or infrastructure, anything changes in your whole system, it will immediately show you what's going on. So I think I might have less time for demo, all right. So yeah, so reliable releases, you can make this whole process repeatable. I can click a button for any version of code and it will give me my installers immediately and be able to deploy immediately to production. Also operation gets tools to enable reliable frequent releases. Yeah, that's essentially the same. It simplifies release management to a very high level because you have total visibility to the status of the application. At any point of time, I know exactly what version of a project is deployed onto, say, QA environment or messaging environment or production environment. I have complete control over the system because you can either make it automated or manual as you require. And end-to-end traceability, if something breaks, I know what check-in actually broke this test, who checked in, at what time, and so on. So especially for distributed teams, this is really useful. And a faster feedback for deployment. So I'll just take you through the demo now. So I won't be actually, all right. So I need to change the, yeah, so this is a typical dashboard on Go. So you can see that you have different pipelines. This is essentially called a pipeline, a management build. It has three different stages. So there's a compile stage, a unit test stage, and a packet stage. So we know that all the three have gone green. You can click on changes. You can see, git is the version control being used. A guy called Pawan checked in. This was the command and this is the git shove and the check-in was made and so on. Gives you all the details. Now whenever a new check-in goes into this version control, immediately this pipeline is going to get triggered. If I have time, I can show you how that happens. The pipeline will get triggered. All the stages will run and immediately you have packages at the end of the pipeline. If something fails, it will become red. This stage would be red instead of green. So if I click here, oh man, okay. I need to change the resolution, doesn't go right. Oh, okay. So when I clicked on a stage, I go to the stages history. On the right-hand side, I can see all the different runs of the stage. That'll show you when it had failed, when it had passed. You can see the status of every job. You can, so every stage has a set of jobs which can run parallely. So as an example, suppose I have a package stage. In this stage, I want to parallely create installers for Linux, as well as Windows, as well as macOS and so on. So I can have three separate jobs which will parallely create the packages for you. So jobs help you do that parallely. And essentially, yeah, once you're playing around with this, you can see a lot of information which this tab gives you. It gives you what are the check-ins which were made. It also shows you what are the tests which had failed. So I can go to another setup of mine and show you. So for example, this unit test stage, it had failed a particular time. When I go on to that stage and go to the tests, I can see that the total number of failures was one, errors was one, and a test called A and B is what failed. One had an error, one had a failure. And this actually shows you a failed build history. That is, if the same test had run and failed a few stages before this, it will actually show you the history round there. It failed in, say, version five. It also failed in version three. So it will actually show you the history, and who had checked in when the failures had happened, and what are the check-in and so on. Now here you will notice that everywhere, this complete visibility to anybody who like, if I go to the dashboard, anybody seeing this is going to come to know that when this particular version had gone in, there was a green pipeline, all the tests had passed. It's good to go to production, right? Now you can also create dependencies here. So suppose I go to, I can, yeah. So here you will see, right? So this management build pipeline, there's also an integration pipeline which depends on this build pipeline. So when this went green, this had, the next pipeline had run and had gone green. So this bookstore integration pipeline depends on the management build pipeline. You also have a feature called trigger with options. This is, if I click on this, it shows you a list of all the previous check-in which had gone in. So you don't always necessarily have to build only with your latest version. We have the flexibility to build with any previous version. So if suddenly, if suppose you have deployed your latest version to production, and you need to roll back, you can go and select any previous version and trigger your pipeline again. It will roll it back to the previous version. You can select whichever one I want here and trigger the pipeline. I can also, this is a very unique feature in Go is, I can compare the changes which were made in two different runs of my pipeline. So if I click on compare here, right? So I can see that between version five and version six, this was a new check-in which had gone in. So suppose I deployed my product to production, say a week earlier, and I deploy again today, I can see the differences between today and the week before, and see that exactly these three features is what has gone into production. This is very easier for managers, et cetera, to track. So this feature helps a lot, not only the developers, but everybody on your team. I think that's the salient features of Go. If you need more information around this, you can come to our booth. We are giving away trial versions of the product. And you can install it, play around with it, and see how it helps you achieve CD. Along with this I would also like to show you. Yeah, so basically a lot of customers are using Go for continuous delivery. So I just wanted to quote a few customers who have recently spoken about Go in conferences and also blogged about it. So the CTO of amazon.com recently mentioned that a customer is using Go over AWS and how they are achieving continuous delivery. Ancestry.com is also another product, sorry, customer of ours who actually uses Go with Chef and with Windows. So like you might think that maybe Go cannot be used with Chef or Puppet, but it can very easily be used with that. And he says that yeah, you just have to click the magic play button and any version gets deployed. And yeah, couple of more talks around continuous delivery by customers who use Go. You'll also find blogs about people using the product on the internet. So yeah, they basically help you, oh okay, I'm sorry. All right, so yeah, so I hope you will use the product for continuous delivery in your projects and yeah, come to us for any more information. Thank you.