 Good afternoon ladies and gentlemen in order to help as many of your fellow participants if there's a seat next to you That's available. Please raise your hand so that the people walking in have a seat to Sit in thank you right We pretty much have to start because this session is exactly one hour All right, so welcome everybody This is the session about 12 best practices from Wunderkraut It's a slightly different session from what we usually see in in Drupal cons. It's gonna be 160 slides So prepare we also have 12 people speaking here and it's auto-advanced So, you know, if we fall behind schedule, you know, we are screwed. So it's it's bound to be fun So my name is Vesa Palmo. I'm the CEO of Wunderkraut and I'll start with not really a best practice just an introduction to us and and the format and so on So if you've ever done ignite before this is a format, we didn't actually invent it We just borrowed it and this is what we are using today. So Wunderkraut is Europe's largest professional services provider for Drupal We have quite a few countries as Tony is actually missing our latest one around 140 people and offering end-to-end services Today it's gonna be 11 topics after this 11 great speakers Let's see how we get people moving back and forth a lot of slides Some seconds per slide and so on. So this is bound to be fun The topics are all here. I don't have time to read all of them So you'll you'll get to see them very soon But I promise you won't fall asleep because the topics are really really from like anything and everything some of them technical some of them like completely non-technical and That's me. So I'm gonna thank you and gonna invite our next speaker on stage So we can actually practice it this a bit and see how it goes. So I'm two seconds early So welcome Florian So my name is Florian and I was not told that I would have this next slide coming up Which is pretty much saying well what I'm going to be talking about and who I am. So hello My name is Florian. I am the co-founder of the German office and I'm going to be talking about speaking up My Drupal Khan speaking career started in 2008. It was Drupal Khan Seget I was talking about simple test a very hot topic at the time and with me on stage I had some of the most brilliant people in the Drupal community So we really knew what we were talking about The problem is that I hadn't really prepared this presentation and the presentation was a catastrophe and I think the most entertaining thing that happened during the presentation. We found a core bug during the demo So this is not exactly the the kind of presentation that we would like to give So fast forward a few years later two years later. I'm wearing the first ever Wunderkraut t-shirt at Drupal Khan Copenhagen token talking about features also very exciting feature and I Very exciting topic and I prepared. I really prepared this time and what happened Well, people came to talk to me after the session people. Well, we got clients from that presentation and People from all over the world ask me for a copy of the slides for next year to really well to give that presentation somewhere else So if there is one tip that I can give to anyone who wants to give better presentations Practice practicing is the one thing that will give you better presentations. You know, there's plenty of gimmicks But yeah, you need to practice. What happens when you practice? Well, every time you practice you end up telling the same story over and over again and Telling a story is actually something that's really important because it is what helps you take your audience from one place that you define To another place that you also define and on the way there you build a narrative that make sure that you are really Keeping your in your audience involved with you. And it's the same thing that we do when we are using User stories with our customers to really focus on what is important So when you're using a user story, you're really defining a narrative and it lets you put everything Aside everything that does not really matter And when we work with customers, this is also the one thing we do We focus on the features that are really going to be valuable for their business And it means that they are going to be successful again same principle when we are speaking up on stage and When we're doing business This is not a slide and The thing is that well when we're talking about public speaking we always focus on the slides The slides really don't matter, you know, it's what you are saying that matters But yet we always see slides like this one You know when everything I read well everything I say is on this slide You can read faster that I can speak you get out of sync with what I am saying and then you get Yeah, so if you're using slides like these what you're doing You're being a cop out because you are not doing the work that you should have done preparing your material and you're letting your audience do that work Yeah, what's up with that and so the best tip that I've ever heard about Creating slides that really engage your audience put only one idea per slide nothing more and This idea is actually something that's very similar to what we do Well during this crumb or using a can band board we are actually focusing on one thing at a time So we do one thing when this is done we move on to the next point So you're really minimizing the bandwidth of communication that you have with your audience This is also something this is not supposed to look like that when you're using gantry based strategy you You actually want in the end to have something that's very linear That does not show how all the people were working together at the same time But you really want to make sure that you have something that makes sense So remember the slides are there to support you, but you are giving the message And our point that's also very important. We do review for Codes, but we also should be doing reviews for presentations So ask your colleagues ask trusted members of the audience about feedback what was good What was not good also take a critical look at yourself because Having this kind of review. It's really what helps us improve as individuals as companies and also as a community we want to get better all the time So as a summary practice tell a story Focus on the value that you have to give to the audience Remember the slides are not necessary and Also review and improve because this is what is going to make you a better speaker. Thank you And we are waiting for the auto advancing. So thank you, Florian Okay, now we can start. Okay. I'm a lot of my cat. I'm from the Helsinki office. I'm working as a service manager And again, we are waiting for the auto advancing Yeah Okay So I have very simple and very irritating subject question Why I'm sure that you will make better business by asking the question why from everybody But you will surely irritate everybody way by asking the why so the why is very powerful question You can find out things you can improve yourself. You can improve a business. You can improve your clients business You can understand things better We use the why question inside the wonder crowd so we could say the one why to rule them all There are many tools like I said internal external self-development tools and it's really really like the cornerstone of our our whole thing It's not technical thing. It's just to understand things better in the internal tool We can use it as quality assurance in a root cause analysis and as a learning tool So basically everything is something related to learning new things how to make your business better If you think about quality assurance a team releases something and and and you think that you have a better solution for that Just ask why they did it and if they don't have it like a reason for that Then you can say maybe we can do it this way again And the root cause analysis. I don't know if you are familiar with the five wise but it's a technique that you can proceed further with the Problem and find the actual root cause to fix the problem. There is like Very very short example taken from Wikipedia proudly invented elsewhere It's just to understand to proceed the why questions enough and in the end like as we see we find a Reason that replacements parts are not available because of the extreme age of the vehicle So instead of just fixing that the reason that we found we actually find the root cause and and fix it permanently As a learning tool the team and organization can learn from what failures by asking why Just ask like why did you do this when we have failed? Don't blame try to learn and educate people As an external tool, it's really really Important that you understand your clients needs so that you are not just providing that what client wants But you're providing what client needs and that's why you need to ask why and they surely will be irritated when you start asking many times So why why why why? When when you are asking why you need to be polite and not aggressive from the client side Because you need to find out the business reason if you if you are like Trying to be Very aggressive. You're not coaching the client. Just you're just irritating But if you if you do it in the right way, you are irritating and coaching so You need to ask just simply ask why questions a lot from the client and as a self-development tool It's very similar than for the for the team perspective You can ask why is from other persons if you don't know something Like like for example when learning you do a failure and you don't know why you did try asking Why you're from yourself like the five-wise techniques or or take a colleague and let him ask the questions as an outsider So you start learning from it So Also also when we think about this company and especially in Wunderkraut where we are flat organization Everybody kind of get decides kind of gets a possibility to management decisions in certain kind level So we need to understand like what's this are thinking about stuff And so we can make the decisions on the same same level and also When when you are talking about again, this goes to the clients when asking why you can also Evolve you yourself your your own own stuff by asking why an understanding client needs so simply What to remember about this just three things. Oh Here it comes. So it's powerful tool for internal External and self-development. That's all you need to need need to know about so ask why to succeed and Again the last slide and remember to ask why Thank you and thank you again. I guess I'm going to thank him again So thank you again, you can call him. He has a mobile So next up. That's me who the master. I'm the city of Wunderkraut Belgium And I can talk for a few seconds more but basically my subject will be about evolution in Websites basically the fact that Websites are not a big bang story. It's just the first step in the long story of keeping involving so basically it comes down to Support and maintenance basically within the whole stack of user support application support operation support and end user support We're focusing on on the green stuff at the top. So basically application support consist of corrective stuff, which is basically bug fixing Adaptive stuff is basically in adapting to IA 9 and 10 and 11 Preventive stuff is doing core updates and perfecting stuff is the stuff that I want to talk about Basically perfecting a website basically means that once you have a website released You're totally not finished clients want to be able to react on Changes and basically on measurements. So you need to have an empty slide which comes next and then talk about Temporary campaigns small improvements Basically all kinds of work. I'm focusing up everything between five and ten days of work This is what I call evolutionary stuff everything which is smaller is basically support everything is bigger is a project So how small I just explained and one extra thing is also Clients need that change very fast and that's the hardest trick because everybody can make changes But can you do it within two or three weeks like the client? requesting So and the other thing is Clients would like that the changes have been made by the Original dev team because they think if if we put it to the support team the quality will not be okay enough So they want your original team to fix the stuff and at the end as a result They prefer to have the same single point of contact the one they had during the build They also want during the evolutionary phases in the two three years afterwards So what does sales and finance and pipe project management want basically they want less overheads They don't want to deal with small request and then having purchase orders and then having a request and then waiting for Anyone they basically want to start working. So they need framework agreements the business developers They basically want to just not be called whenever a client asks Oh, I like to have a Twitter integration, please And then they have to go to the dev team and stuff like that. They just want to foster the relationship with the client the developers themselves They like to take ownership basically the fact that They built something they are proud of it And they want to keep on keeping the same quality what let that they had at the beginning of the project So different stakeholders different needs leads to most of the time challenges challenges are fun and The way we solve that is by putting in I think an extra empty slide and Then planning basically the biggest challenge is in planning and in the extra overhead for finance The planning issue is basically being able to have Ten days of deaf work available within a deaf team within two to four weeks If you have a bigger organization, it's sometimes hard to cope with and the other thing to as a whole The challenge is one person keeping the overview of the whole project So basically if you have a builder and a business developer product owner support team You need one person to rule all the information and that should be a single point of contact for the client Our solution is everybody knows this stuff called evolution. Basically. We have a product. We call evolutionary support Together with support contracts that gives the client basically fast response Ability to have bug fixes fixed by either support team or the deaf team and they can really ask now for small changes And they're sure that they can get it fixed. So it's the solution itself is basically You ask a guarantee from the client saying give us 50,000 euros or 20,000 euros of anything in advance which gives us the correct way to handle and basically Keep people ready on the bench. What who's happy the clients business developers and sales in the finance Most interesting thing is at this point. We have a few unhappy people at this point the developers are unhappy because Basically, what happens if you have five projects finished and you have to evolve five sites in the end You're basically only keeping track of old websites. You want to do new stuff As an example, we have built natural momentum, which is a big site We did one responsive site with restful integration and took half a year to build in the evolution The stuff what we take up there is Facebook apps improved webforms perfect six Yeah, you can read yourself basically the client is happy and they say we can embrace change And that's the real thing you keep in mind here The same thing culture net also belt inclined a lot of projects. These are projects. So we've built in a few weeks and Then there should be an extra slide explaining stuff like a picture with small children and Basically what we did there was we have multiple large sites as projects you can read A lot of APA integration took months to build. What do we do during the evolution? Any new API integration we have we pick up in the after lounge My name is school demister and I thank you for listening to my talk I'm introducing Reinhardt the German guy The other German guy. Hi. Thank you Florian, I hate you I didn't show my slides to you before this so I'm Practically having all I'm going to say on my slides. So but we'll clear that up afterwards I'm going to talk a bit about sales and the way we do sales by Stopping to focus on price instead focusing on value a quick story Florian What usually happens is that client send us in huge RFPs like they can be like just some designs or like hundred page documents And we look at all the specs we estimate like hell there's concessions here on triple con on the art of estimations and We come up with a price and the price is usually way too high because the developers Put everything in there and we know that other shops will probably offer for less That's usually the case. There's markets where there's really tough price pressure and So what do we do? We kind of start lowering our prices cutting corners trying to find things we can do on the cheap or Maybe do later and so forth and in the end we still lose the bid So that's kind of a bummer In this usual way of reacting to to customer proposals so What's wrong with just offering with just making really good? Say cheap offers to customers. That's the question. We've been asking us a lot The really problem the real problem with that is that it's basically a race to the bottom There's always somebody else who's going to be cheaper than you some small deaf shop some people working with guys from India or someplace else that are Shops that are desperate because they don't have enough business. So they'll be offering on the cheap and we are basically we'll never Score against them. So what we do is we try to change this whole conversation this whole process of of Selling web projects the question we first ask ourselves is what do our clients really care about? They tell us a lot what they care about they ask us questions about like something like daily rates hourly rates our Internal processes and stuff like that. They want implementation plans from them in their proposals. They want huge Forms to fill out especially in the public sector if we if we have tenders there They want gam charts project plans and so forth, but we think that's not really what they should care about. So we Very often don't really do these estimations, but we start asking questions We've heard one very good question earlier from illy. It's the why question We have another very good question in the sales process and that's the how much question that should be asked a lot That's the several how much questions you can ask Like the most important one or the most powerful one is the question how much additional profit Will you as a client make by implementing this or that feature that is in your proposal? so if you really start thinking about That forum you put in your proposal will that really create? Revenue for you will that really create profit for you or how much money can you save by implementing this or that can you? Save money on maintaining your website and there's a ton of other questions that I've put up here That that should be asked from the client very early on in the process and once we've asked these questions Then we start asking ourselves. We start doing research We look at the client's business or try to find out as much as we can about the client's business Look where there's a potential for profit for the client. Look at where's this? Oh, I'm talking too fast Okay, we look at all all kinds of At the customer's business and then we start talking to the customer and make them come up with value estimations How much is that value? How much value is is for you is for you in that feature How much in that and if they can come can come up with with real values then we assist them in that basically there's two ways of Profiting from from this kind of of a sales approach on the one hand there's a customer that profits because he's for we make him focus on the actual value of his ideas and We make him re re re reexamine his project very very early on in the whole process and for us the main profit is that we only work on stuff that Creates real value for the client because nothing is more frustrating for their developers than working on stuff that they know is worthless and We usually get very satisfied customer from that and in the end everybody profits that was my talk. Thank you I don't even know who's up next, but I thank myself I Think Steve can that be no We'll find out in a moment Yeah Jonas Hey, so I'm Jonas I was like putting up all these lights and I heard yesterday that I should be talking here also five minutes So I'm why my thing is about spicing up your work life And it's what quite visual because I didn't have much time to prepare really like a Talking presentation, so we will look at some pictures and stuff, but I will mention this company culture that It's you cannot it cannot be forced really you can make work groups and stuff, but it just happens in the end anyway and There are no like You cannot really use policies to make a company culture. You can have like some there's some examples and In the end these are just they can be obvious or somebody has to be really stupid if you don't like understand Well, what is the best way for you to work? So you need to trust your employees that they will do the right thing anyway So these are better like these are not policies But these are things you can do and then the company culture come on like comes From the people how they behave and what they do So small differences between people make them special, but big differences make them unique There are no two identical persons so why would you have some stupid form where you try to fill all of them and So here are some tips how we have kind of spiced up our work life in events and office and That just kind of creates the company culture slowly So You can get a training from a dog. This was from our scrum master training and Then or you can listen to a training with the dog. This is real listening to our internal trainings you can be inventive in the office like It was a pretty funny moment You can get a helicopter to the office fly around. That's like the best thing You can share a beer with colleagues That's also really relaxing or you can sunbathe with a colleague or with several colleagues This is from our summer days You can take a swim in the sea and or you can just in a pool or Or or in the Chacuzzi by the sea Which is nice also You can go to amazing events. This is from developer days Barcelona and Or you can learn how to make kick ass cocktails. We had this kind of a course on how to make some really good cocktails And Yeah, and of course you have to drink them You can telecommute from exo-git location. This is me at paradise beach at bouquet and you can go on a battle boat ride and I hope the video works do it like a boss This is from Munich where you can change your boring black bike into a Punderbike This is my own bike which We took it down to PCs and painted all the pieces separately and then put some nice stickers on it And now it's I go to or off work every day You can reward employees with small kids or big ones and You can do something different together Like I don't know orienteering or silly games Especially they are funny when you do them together because after all The teamwork is the Key to everything. So if you don't know how to work with your work mates, then it's gonna be difficult time in the company This was a truly annoying game Okay, thank you that was my session probably a little bit shorter than others and yeah Well, there's my information You can call me Yeah, you can join me in bouquet next year if I go back Next up is David. So very stuffy Hello, ladies and gentlemen, I'm David Corbaccio. I'm a senior developer in wonder crowd. I'm Spanish But I'm living already five years in Finland and I will talk about Parkinson's law It's about time management and I Will present you now the law Work as pants so as to fill the time available for its completion for example this session is a It's a perfect example of the law We have been given five minutes to make the presentation if they will If I will be given one hour to talk about Parkinson's law I will feel it, but it's only five minutes. So there's no time to waste four minutes now It's a natural human behavior is it let the work to fill the time that we have so you can have some Negative effects or consequences One of them could be analysis paralysis is like when you over analyze your problems For example in developer if they say, okay, you have three weeks to To find a perfect solution for image carousel, but I could be three weeks easily Feeling that time researching It's easy to say, okay, I will do it later. It's not expected from me to do it today So I will do it tomorrow last minute panic Yeah, so to say well, this has to be done in six months So it's okay. We have time Typically I saw in waterfall projects where it's really far deadlines No, I cannot do it until this other person finishes work. Then I will do it. So there is always waste of time and multitasking is It's overrated All of these are negative consequences or Interpretations of the Parkinson's law But you can use this also to your own advantage doesn't mean that has to be negative I will give you some tips, but of course you can think about the consequences instead of over analyzing a Wonder card we try to To do it fast to get ready soon the solution and if it fails, okay, we fail fast iterate if you know the the book the lean startup it goes It it goes a lot about these practices and how to do it Yeah, this is obvious It's a lot of studies that have been about how kills the productivity to switch from project to project So try to be fast This fits very well with agile methodologies like make short directions like one week put goals so Makes things easier Lesson is I don't know if it's bad It's not because I'm there I'm from the country of the siesta But you know only do things if they really have a real value to the customer don't do things I will be nice No, just as you see almost all All these applies better to a job methodology. So so I think it's a natural natural combination so Instead of reinventing the wheel try to collaborate speak up for example Drupal 8 has been We have forgotten the I can't getting Well, it's not a silver bullet. It doesn't mean that okay. We have a project. Let's put the deadline for tomorrow So that's that's perfect. No, it has to be You can afford someone to put to to put the deadline you have to let The the team to to decide the work then in the iterations the parking lot will kick in Yeah, balance it. Don't don't just say yeah, this is short deadline. It needs to be quality and maintainable Yes, I wanted to present you this law and that you think about it like how to use it to your benefit and Add it to your tool that I will present now the next speaker from Canada Drake Thank you. It's my first time so be gentle I was actually a little worried if somebody else's name is gonna come up and here I am with the microphone on stage So what I'll be talking about is Drupal front end without tears I am Canadian. I was born in Russia. I grew up in Canada But I currently work in the Helsinki office and I've been living in Helsinki for two years now over there I am the what I call my title is UX designer But I'd like to come myself a front-end guy because in an agile world You kind of end up wearing many hats and oftentimes they're kind of stacked one on top of the other and My slide is not auto advancing. So Well, there it goes Hey, so Yes, this talk has been be a bit more practical in a sense that I'm not gonna philosophize and Sort of try to change who you are or what you think But I'm gonna tell you what I do and what I found works for me because when I joined the company Basically, I knew very little about Drupal. My background was pure graphic design So you know illustrator Photoshop and such and here I am, you know in front of a computer, you know command-line coding stuff and What do we do basically you sink or swim right and I kind of chose to swim and I swam for it And this is what really really helped So one of them basically if you're not using a CSS preprocessor right now really you should be because they're not going anywhere They're here to stay and obviously the top ones are sass and less sass is kind of slowly killing less in my opinion because sass has a More active community, I suppose and there's more tools available that build on top of it tools such as these frameworks that live on top of sass they are Compass that is compass is a true framework and bourbon and bourbon is more of an extension of sass So think of it as bourbon is like more of a hipster version of compass and compass is like kind of this big bad Kind of Microsoft thing mind you all of them are Both of these are very hipster and very cool and very new and very well documented and the very active community behind them So advantages of using compass are it is much wider used Including in the Drupal world. There's a we'll get to this later, but there are a few sort of new Modules and themes that rely on compass quite extensively. There are a lot of extensions to compass itself So if you remember compasses itself an extension of sass while compass has other extensions built on top of it So it's the opportunity there is massive you can build your own custom little sort of toolbox and learn it well and rock the world with it and Bourbon the other one sass is a bourbon is a sass mixing library. So it basically just extends sass for you making CSS 3 especially stuff a lot easier. So it's a lot newer. It's a lot leaner a lot better I guess a lot kind of hipster, right? So it's really good for really like cool new CSS 3 stuff So if your client doesn't care about IE 8, you know, go ahead, you know, knock yourself out He was bourbon and you'll have a good time So that's so when it actually comes to working on Drupal sites Like somebody previously mentioned, you know, there's no point in reinventing the wheel There's lots of other good wheels, you know done for us and they all quote perfectly well So why not use them? So one is to pick a good base in this case as a front-end guy I'm talking about a base theme because I think these days very few people actually start seeming from scratch It's a really good idea to especially the agile will to start with a really good base These are the ones that we end up using most often. So they are Omega Omega right now is on version 4 So if you've had an exposure to Omega previously with version 3 But it's zones and regions in a crazy UI configuration screen You probably felt a little bit intimidated and almost like the system thinks it's better than you are right? It kind of makes you feel stupid. Well, Omega 4 it goes away with all of that stuff And it's a lot leaner a lot meaner a lot faster So I could vouch for Omega 4 go ahead and use it other two were Aurora and Zen Zen probably most of you know Old school, but it works. It's like an old reliable Toyota and Aurora is extremely new There's only like 700 800 sites reportedly using it I'm one of them and Aurora is tied into compass really really really deeply basically Aurora and compass they go hand in hand So these are Extensions of compass that I personally end up using practically all the time in every single project and these things are priceless I'm sorry. I'm gonna have to go back one. I'm cheating here because I have to I have to I have to Just you know, take a picture of this screen, you know, if you're a front-end guy they are breakpoint singularity GS is a grid system and Modular scale makes it a lot better to scale your stuff and RGB AP and G is a quick little neat mix and if you have to support I eat ate it basically makes I ate aware of RGB a colors so really really really cool. Sorry. I cheat it. I cheated there. We go happy theming I hope you are able to take something home knowing if at least one person learned something new then I've won Thank you I also have a mobile we all do the next step is to mr. Steve parks Thank you very much. We'll see if this is broken now. Otherwise, you might have me for about an hour So it's you know fingers crossed so first up what I want to know is has anyone ever heard of a web project? That has run late over budget or maybe not delivered what the client wanted is anyone ever seen any of these in the press Anyone ever heard clients complain. Yeah, what's going on with that? So we wanted to do healthy web projects to try and help clients understand What it is that makes a web project successful because so often their processes the things they demanded Even as part of their procurement process or their contracts with the very things that made everything go wrong now This is in beta. So we're still working on this but we wanted to present it today and you can find out more details about that web address and We're going to present some of the ideas that are the ways that we're trying to experiment with to explain common sense I agile processes and so on to clients So the first thing with a web project is you have to begin with the end in mind So you've got this kind of fat little turnip here who wants to be a slim small little radish Maybe it's in time for a holiday to fit into its swimsuit something like that. It wants to look trim and buff So it has an objective in mind and web projects are just the same You really have to have a very clear objective for the project that everybody knows what they're aiming towards There is no magic pill though. That's the other thing so many times You know you hear clients saying oh no, but this vendor has promised me this magic pill is going to solve all the problems So often true of proprietary vendors. Oh, just drop this into your process. It'll work like magic There is no magic pill to having healthy websites healthy web projects It does take actual real hard work hard graft and also the knowledge about the ways in which you work Just like keeping fit. You can't have the diet pills You just have to actually eat well and exercise and eating well is important So first of all, don't put too much on your plate Eat in meals don't eat your year's worth of food in one meal break it up into meals the same as web projects We have sprints we sit down and we have meals and we only put a certain amount of our plate on our plate at time Also, what's important is what you eat first Remember what you mum said eat your greens first Save dessert till last and only dessert if you're hungry It's also important to eat free range because you know what you eat is just as important as how much you eat and free range Of course is open source. It's software. That's free to roam And that means that you can get any agency to come in and work on this software You're not tied to a vendor a big problem that often happens with web projects Is that a client is really tied in to one vendor or one piece of software and it's so difficult to change that a Healthy web project the software is free to roam from one agency to another But of course, it's really important to know what goes in to the web project Do you want horse meat in your website is the basic answer here? So when you are talking to agencies when you're recruiting people You have to know that the knowledge is there the expertise is there and you have to know that when your website is being built It's being built with the right attention to quality. So if you're buying, you know a 99 Pence or euro cent tin of something or if you're buying a cheap lasagna, then you'll end up with horse meat in it And you have to exercise look at this healthy carrot here. You actually have to get out and do this stuff It's no not enough just to have the theory You have to put it into practice that means going down the gym It means having an exercise regime that means, you know, you do have the proper sprint planning meetings You do have your proper backlog grooming. You do have your daily stand-up You do the exercise and you do it every day every sprint and you keep repeating this so that you're always following the best practice to get in trim It's also important to know about progress Now in terms of web projects, of course, we use story points to kind of keep an eye on the value We deliver think of these as like calories So when you're trying to get in shape and nice and buff and trim You watch the calories that you eat and you watch the calories that you exercise So when you're on the exercise bike like at our stand, it can calculate how many calories you're burning Now the calories you burn Give you information about how much you can eat and if you try and eat more than you're going to burn off in calories Then your web project is going to get very overweight in fact So this is where you can find out more about some of these concepts about healthy web projects for explaining them to those Who are new to agile and it's just a simple way of getting clients and others Up to speed on some of these kind of best practice ways of working and there's more information on the website There's also these booklets at our stand. So go by the stand and pick one up straight afterwards It's just out the door in the hallway there And that is our concept of healthy web projects and we'll also give you a free beer because you know You need a treat every now and then So this has been me speaking and the next speaker i've been told is really rubbish because Oh, it's me again. So I pulled the short straw and what we're going to talk about here is managing risk So you see I said I might go on for a bit longer than the others We're going to talk about managing risks on web projects because that's another key process Part of making them making them happy and healthy web projects And so many times we introduce risk It just by not kind of planning enough and you see all these Web agencies that say yeah, we do agile agile means not planning No, it doesn't agile means planning just as much This is the view from someone's flat window It's a hospital where they had a problem with people parking on the pavement all the time They called these workmen to install the bullards to stop people getting their vehicles on and off the pavement Can you see the problem with their planning? This this person was when they were posting the photo wrote up about how Entertain it was trying to watch them get it out And then also there's the problem of not listening to users too many times we go away and we think yeah I know what to deliver code code code you go back you go tada and you show them their garage with steps and So you've got to always involve the users throughout in order to remove some of the risk in the way that you manage your web projects because Tadah development does not work You've got to always be working iteratively always involving the users throughout the entire process So that you know you're delivering what they need and remember I mentioned measurement in healthy web projects Always be stopping and looking at where you're going You know where we had the objective to go And how far we are towards that and are we headed in the right direction? Because otherwise you get to the last you remember that last 10 percent for project problem Have you ever had this where you kind of yeah, we're 90 percent there just the last 10 percent to go. Oh shit And that's very much the feeling these guys on the bridge have here And you hear about this so much on projects where it just doesn't end up quite meeting where it needs to quality control Is very important because bugs will slip in in all sorts of places And so therefore you need to build into your process the assumption That there are going to be bugs don't just hope and leave it till a bit of testing at the end You want to be having automated testing you want to be having peer review Quality has to be a key part of your risk management process because otherwise you end up looking like Wankers okay, so you've got to have all that quality control throughout your entire process that did go on air But don't fill your dev team up with silly rules or you're trying to achieve this quality You're trying to reduce risk Don't have pages and pages of silly rules. This is about simple concepts You've got a good team. You've got professionals. So it's just about having the standards that very clear definition of done This is the way that we test things. We have peer review. We have these processes So you have those in place and you don't make silly rules But then also don't try and pretend everything's all right if you identify a risk It's really important that you try and you communicate it very clearly to the whole team To the client and you're very frank about it. Don't just try pretending, you know, how's the project going guys? Yeah, it's going great. Thanks very much You actually want to say okay, we need to have a meeting with you tomorrow because we've just discovered that this api doesn't have proper documentation This is going to knock this back etc be very frank have the tough conversations early and a way of doing this We do this on a regular basis with Clients we have a steering group that's every second sprint Where we bring in very senior people from the client side and we set them down and we walk through the progress of the project Of course and we walk talk through some of the progress towards objectives, but every time we review the risks and We've at the beginning of the project listed the the risks that we've identified down the side here And then during the project every Two sprints were reviewing the movement of these risks around So you're measuring the impact you're measuring the probability And you're plotting on them on the scale and seeing where they were at the last meeting So which risks have increased number four failure of existing systems? We identified that some of their legacy stuff was really really flaky and the risk went up Risks that are reduced migration that's dropped a long way because we've been through sort of the discovery phase in the first sprint So this is a really simple way of communicating risk to a client and making sure that you're tracking it throughout a project So i've been steve parks. Thank you very much. Good afternoon And like all the speakers i'll be at the stand later on come and have a chat. Please welcome james nesbit Hi So my name is james nesbit. I'm also a canadian like greg. I don't work in the finish office. I work in the Lafayette office and What i'm going to do is i'm going to talk to you give you a brief retrospective of my first year working for wonderkraut Not so technical much more personal So i'm relatively typical canadian like greg and we tend to like the simple things in life We're pretty fond of wandering around and we like to hang out and interact with people and Really good food is really important to us. So I guess that's really why i like to travel a lot I've been around it's kind of my reputation and i really like to move around for both Business and for pleasure. That's me at the protest in Athens in the middle Good fun i'm also Naturally, you can assume i'm also a pretty big fan of technology Big fan of drupal been working with drupal for a long time probably 10 years Probably not a significant contributor, but i think i know the tool relatively well So people in lafayette are usually the first question they ask me is a why are you in lafayette of all places The answer is pretty simple 2008 in spain. I met this lovely lady and we kind of been following each other around ever since Eventually we decided we should probably try and settle down and she's from lafayette. So i went to lafayette Where i was very happy to find that they also like the very simple things in life like food and getting around And interesting social interactions with each other And so i really hoped that what they really needed there was somebody like me And so i tried to find something to do and i checked out the local drupal user group And they were planning on hostering uh boot camp Went in signed up gave a presentation managed to not get kicked off the stage and Felt pretty good about it. So I thought i'd go back to the company that was hosting the Boot camp which was mera. That's these guys this group of miscreants Asked them if they would sponsor me. They said yes And i was the brand new member of meata latvia with the finished partner Uh, what happened next was the 15 minutes later. I wasn't working for meata. I was working for wonder crow It's about how long it lasted so everybody of course is aware that this is a merger between four groups in europe Creating one of the larger Web shops in europe I went from this company in lafayette to this great big company all across europe But uh, we grew in size we grew in developers and we still had this fantastic perspective of Being these small groups these small offices sometimes groups across offices And uh, we didn't take ourselves too seriously. We weren't trying to be suits and ties We had fun with what we were doing and talking about stupid things But we did take projects seriously and we took clients seriously Our focus was having happy clients and successful projects not trying to be too smart but trying to do well Uh, so how did it go for me? Uh, naturally, of course, I came here to tell you that it went really well Uh, it didn't it started off really poorly I dropped the ball in my first project and I had a really hard time stepping into this agile stuff Instead of just talking about it, which was much easier uh, I uh, I wrote too much code. I spent too much time planning and It didn't matter so much because the company they actually invested in me. Uh, there was lots of training and uh, Lots of support especially from my colleagues, uh, which was really helpful, especially Taking me out of the town and making sure to get me drunk at least a few times Uh, but inside the company what they did is they got me involved in really interesting projects Despite my initial failures. I worked with really interesting clients small companies big international companies massive migrations custom mapping, uh, apis and javascript and so on And for me what was really important is I got to work with that really cool stuff that I always read about But I never had time to do inside business. I only got to do this hobby projects I had to get on these technologies right away and learn them and learn them really fast in the beginning of project If I wasn't used to it For me, I really appreciated that it was fantastic and it led to a lot of advancement for me I started writing really good code. I started getting really good feedback from customers And I even managed to uh, to win the lafayan employee of the month award two months in a row Something else big happened. Yeah, I managed to marry that girl from lafayas. It was another big accomplishment for me Anyway, enough just about the history, uh Really, I think that I have a good understanding of what it takes to uh, to try and work abroad Especially really far away and the number one thing is to make sure that you challenge yourself You don't just walk away from challenges. Uh, if you find something it could be an interesting opportunity Jump on it And when you are abroad make sure that you keep finding interesting things to do both inside your career and outside of your career Because everywhere you go, there's always something to do and most importantly Remember the local because you only get so much time in any place And if you're going to go somewhere and work for a period of time, make sure you take advantage of that opportunities You might never go back. You might never get access to those same people or those same resources again You might never have a chance to try and learn that language again So that's really my concept of what it's like to go really far away from home And get invited into another family. So I really recommend everybody try such a thing Take a risk and be like me. Jay Nesbitt occupied I think that's the last speaker so Yeah, I hope let's see if that was all of it. We'll we'll see it in a minute So, um, there's one more thing Feedback we this is a new thing. We tried it for the first time. No idea how it went So we really appreciate new feedback on this. We try to fail fast So give us feedback and we'll keep on improving this stuff. So thank you everybody Oh, okay. Yeah, sure. We have some time for questions and answers it seems so Any questions from the audience for any of the speakers? Or was it too much? Oh, yeah, we have only one minute. So come to our booth and ask the questions there