 I think we have enough people, all right? We can start. I said I should wait. I was ordered to wait, so I know. I'm catching up on my Slack. Like, just hold off. Oh, wait, wait. It's hard to do a presentation when you're in your Slack. Is everybody here on the Drupal Slack, by the way? Does everybody here not know what Slack is? Maybe we should start with that. It's OK if you don't. Slack? There is a Drupal Slack. If you're not on it, I recommend you get on it. So you can find out what's going on in your particular neck of the woods or your line of interest. There's channels for project managers, just like there is channels for developers. Highly, highly recommend it. I think we're up to 5,400 or 5,000 users. So it's really handy when you're stuck at the middle of the night. It's 2 AM and your client is expecting something at 9. All right, let's get started. I apologize for the delay. For those that just walked in, I was asked to hold off starting for a few more minutes. There was a coffee break running a little long. Let me get started. You're in the Agile Sprint Tools rundown. How, when to use a mallet when you really need a Mjolnir? Everybody knows what a Mjolnir is, right? Of course. So Thor's hammer is called a Mjolnir. I don't have a picture of it, but it's pretty impressive. Have you ever watched any of the Marvel movies? He is the only one who can pick it up. And it's an appropriate title. So let's get started. Let me tell you a little bit about myself and what we're going to do here. This is a quick session. It's hopefully going to be 20 minutes, so we have enough time to do some talking and questions. My name is Chris Urban. I'm a manager in professional services in Aquia. I'm from Philadelphia in the United States. It's my first Drupal con and probably last in Europe. I've been playing with Drupal since 2008. Was anybody at the pre-note this morning? OK, so you know a little back story there. Oh, yes. I was wondering who that belonged to. I'm a certified scrum master. I'm a site builder. I'm actually a, don't tell anybody. I used to actually do some development a long time ago, which is how I got started. Like everybody else, you were looking for the perfect solution, tried building on yourself, played with Joomla, WordPress, Moodle, PHP, Nuke, NetNuke, whatever else was out there, and settled on Drupal. And I've just stuck with it ever since. It's my, by far, my favorite. I actually come from a marketing agency background, publishing, newspaper business. So all those frustrations with working with designers that are still locked in the world of print. I've heard it all. And this session is really to talk about some alternative tools to JIRA, which is like the big elephant in the room that everybody either wants to use is lucky to use or you can't afford to use. And if you're like a medium to small agency and you don't have the budget for it, there's plenty of other tools that are worth trying. So this session hopes to kind of go through a lot of these. And maybe this will spawn interest. You might want to go and play with these more. But nobody has time to sit down and install all this stuff and play with it. So that was the goal here, to kind of go through them all in quick succession, give you the highlights, the lowlights, what sucks, what doesn't. And hopefully one of these might deserve some attention from you and your project. So any questions before I begin? Okay. So we talked about it. What is there that we can use in place of JIRA? Now, I'm a JIRA nerd first and foremost. So I have a very heavy bias for JIRA. I respect the power and it comes right great responsibility. So I wanted to keep in mind, there is a list of assumptions and desired features. And I still haven't found what I'm looking for, but there is a lot that's out there that shows a lot of promise. So a couple of key things to keep in mind. I'm trying to rank what I've gone through with an eye towards you've been using Google Sheets or Excel. It's not enough. You don't want to go all the way into JIRA. You're already familiar with Agile, maybe Scrum or Kanban or both. And I'm giving a preference to stuff that's off the shelf, easily installable. Something I can host myself maybe. And most importantly, it's cheap. So it's free, right? Or it's a perpetual license. Or let's say the least preference per seat license. And that is actually the model we'll see a lot of. The X dollars or euros per month for 10 users, that sort of thing. In terms of a wish list, the things I was looking for, I want something that'll help me with project planning and ideally keeping track of the resources that are on the project. This is a high goal. It's a hard bill to fit. I'd like to have something that allows me to manage a backlog. So I have a lot of requests from my product owners. They wanted to get it into the upcoming Sprint or planned into your Kanban development. How do you keep track of that? And if you are running a Scrum Sprint cycle, an iterative development cycle, something that will allow you to keep track of the work in progress. Any sort of tracking of effort, if it's hours or points, just so that you have some feedback mechanism for your estimation process. Ideally, if there's any way to do reporting, so I can see who did what for how long when or where there were problems in the last Sprint to raise these in your retrospective. So now that I've given you my wish list, I'm gonna tell you off the bat. I've yet to find one that fits all of them, so don't be disappointed. This is part of the process. There are a lot of good candidates. I will say that, but there's still nothing that fits everything. All right, now this is gonna be fun. This is the first time I'm doing this in this kind of format, so if this is really cheesy, just bear with me, it's only 20 minutes. We're gonna do this like a radio station top 10 list, all right? So number 10, coming in this week in the Agile Sprint Tools countdown, number 10 is MyCollab. MyCollab is a Trello-like tool. If ever, is there any here for a million with Trello? Okay, awesome, so this is a good baseline. It includes a Gantt chart, milestones and time tracking, which is not in Trello unless not out of the box. It lets you do some issue management. You can install a community version. This is the keyword to look for here on Linux or Windows, but like JIRA, it needs Java to run. So don't consider this necessarily easy to install. So to understand like level of complexity, I have JIRA running on this laptop because that's the kind of nerd I am, but I don't encourage you to do it at home. They have, to give you a sense of the cost, $19 a month for 10 users, $100 a month for 60 users. So this is kind of in the size I'm thinking, a typical medium, small to medium shop, you've got a couple of projects going on. This is probably in your size range, but this is number 10 in the list. So it looks kind of familiar, right? You've got your dashboard on the left. You've got this kind of messages, pseudo Slack sort of tool in there. They separate bugs from tasks. I just picked this one screenshot. This is not a good representative example, but it has, it's okay, it's great. Now, this is really stupid, but for me, one reason why this is at number 10, if you go to the homepage, there's still a long Ipsum down at the bottom. So that to me is not a good sign. I've just, you know, if this were me, I'd be like, okay, somebody's got to get on this thing. So one reason this is at the bottom of my list. All right, number nine this week, this con. Assembler, anyone here use assembler? I mean, actually I should do this for each one. Has anyone here used or are familiar with my collab? Awesome, see, so now two tools you've never heard of, you don't need to go play with. Assembler has a really, one thing I like from the developer perspective, it has an interface, it has an integration with GitHub. It's slick looking. It looks nice, but it's expensive. So comparatively for the number of users, it's a little more pricing. This does have, I hope this is the animation, this does have some of the basic items here, so I've kind of put in the key typical tasks for a dummy project. You can see this Trello-like board, right? So to do, doing, done. You can, here instead of dragging the rank, you have to use this up-down priority button, but pulling them into the quote sprint is pretty straightforward. But overall, it's okay. It still doesn't have a lot of the features or things that I want from, let's say, a Jira. And again, I hate to say it like that, but little errors like that still pop up. But you have a pretty straightforward sprint board, and I'm trying to keep it as simple as possible. It includes all these other bug fixes categories, so it's really more oriented as like a support help desk kind of tool rather than a sprint tool. It does have this like overall reporting, so if you have, let's say, your entire backlog, the equivalent in Jira would be like a version reporting, and this calendar feature, which is pretty nice. That's another thing that is not in Jira. And some of the reporting that if you're familiar with Jira, straight, typical scrum level reporting. So reporting is good, the UI is okay, kind of expensive. All right, let's keep going. One more thing, oh, integrations. There's a lot of things that this connects with, and it comes with, so there's like a wiki. You have a stand-up tool, which is kind of nice. So if you want to talk to me about that and Slack later, I can tell you some other tricks. Twitter, I don't know why you want to connect Twitter to your Sprintboard, like, oh my God, we completed a ticket, whatever. But the development integration, the Git and SVN hooks are pretty nice. All right, number eight, rest your board. So quick little background, I did this session in an earlier version of this at TripleCon New Orleans so a year and a half ago, and I talked about this project then, and it's still worth being in the countdown. For a Trello alternative, this is a good one because you can self-host this on your own instance, and there's no restrictions. So it really is a more open source model than what Trello is. And this is even more timely because Trello's been acquired by Lassian, as you probably know. The only problem, and I don't know that they've still fixed this, is that there's some issues with performance in Internet Explorer, but if you're an Internet Explorer, you have bigger problems. So let's do a quick demo here. Again, the way this thing loads, it's very, very Trello-like, and in fact, what I do here is I load a JSON export from a Trello board. So I have the same list of tickets, and you can see your members of your team, what they've been assigned to, you drag them across the columns, you can add details, you can upvote, which is kind of nice. It gets the job done, it's good. One other nice thing, if I scroll back up, I hope I remember this, you can do, maybe not, you can do multiple selection of cards, which if you're in Trello, you know it's a pain in the ass, you have to go to each single one to assign them. Keep going, keep going. And the other nice piece that this does have that Trello doesn't have, is it gives you a list view and a calendar view also. So again, those two extra, so this is your traceability, your activity log, you have this kind of basic reporting, the list of tasks, your permissions, you can have email notifications, so it becomes very Trello-like, right, okay, there we go. And multi-select, so that's the task list, so I can do this as a bulk list, and then the calendar, so you can see when their due dates are scheduled. So you can publish this kind of information. Those are nice features, and a Gantt chart. So that's why this is number eight in my list. All right, keep going. Number seven, I have to sound like a DJ. Orange scrum, this is a new one. This is tricky to install. There's a free version, that's the community version, it's, I have still yet to get it installed on my laptop. It's tricky. There is a demo online that you can play with, so the screenshots I'll show you are from that, and it's a little bit different revenue model, or cost model, where they give you the basic set of tools and they charge you for the add-ons. So in that method, they can do defect tracking, or a Gantt chart, or the ability to do resource allocations, you have to pay per module. And they're not cheap, they're anywhere from, I think $50 to $100, or euros, whatever it is, per element, so it can get expensive pretty quickly. What is nice is that it has a template, so you can say a design ticket versus a backlog ticket, and structure the way people are entering in their stories differently, which is interesting. They give you the task list as well as a Kanban board, and it comes with apps to integrate with Slack and iOS and Android, which is kinda nice. Again, it's open source, so you could literally host it anywhere you want for free. You can do their hosting for, not too bad, you pay a one-time perpetual license for 10 users, or let's say $1,000 for 50 users, and it gives you a year of maintenance and support. So if you need any help getting set up, it's included. So again, 12 months, that's $10, $20 for 10 users, it's in the same ballpark, what I would expect. All right, so a quick walkthrough of what this thing looks like. Again, dashboard, you're seeing how these things look familiar. They kind of organize everything. They give you this summary reporting, which is kinda slick. You can keep track of all the milestones in your project by list, and then if you go up to the top, you'll see you can jump over to basically the Kanban view. So this is the Trello task board view that everybody's familiar with. And the same things work, it keeps you reporting, you can set up email, the whole nine yards. Again, you get it as a nice convenient task list. And that's it, so that's that one. And then the next slide, I should show creating a new ticket, I think that's what I did here. Gotta remember what I put in here. Oh, this is the, actually I don't want that one. There we go. There's a place for files, the add-ons. This is what's really cool. These are all the extra pieces that I was talking about, but you have to pay for that stuff. So in this demo, they give you a taste of it, essentially, but the Gantt chart is not included. You have to pay for that, but handy. All right, so that's that one. All right, let's take a break from the countdown and talk about some stuff that didn't make the cut because I tried to limit it to 10, which is really hard if you think about it. One of the projects I talked about last time, I still think it's interesting, especially you have a very developer-centric organization. This is about as simple of a project management tool as you can get, which is basically marked up text. And I took the slide out that shows it, but it's literally text using hashtags, add symbols, percent symbols to track and tag the different lines of work. And you would basically, I guess, commit the file to your repo, which is kind of meta, but you have everything tracked in one text board and it has a front-end renderer that turns it into something that's pretty nice. I don't think this is for your average team, but that's why it's kind of worth mentioning. Three more, and I just didn't get a chance to play with these enough, whether when I time I had, it wasn't as interesting or appealing to me. Pivotal trackers, one that I've seen used a lot, but this is like for really, really small teams. The costs for that go up pretty substantially. Mingle is worth interesting. That has a pretty slick UI too. And version one, I just haven't had a chance to play with it as much. So again, next time I do this talk, I'll try to cover those. This PDF will be added to the deck, so don't worry about scrambling that I'll write all these things down. And I'll give you the list at the end too. All right, number six on the countdown. Libre board or WeCan. So it used to be called Libre board before, and that's another resty board. You see where this is going? It is to Trello, so they became WeCan. And it is pretty slick. It runs on Meteor and Sandstorm, which means again, installation is a little tricky if you wanna do this yourself, and I wouldn't attempt it. What is interesting is that the way they build this, it's kind of like Steam. So instead of Steam for games, it's there, the Meteor Sandstorm platform for project management apps, which is kind of weird. It's not, I mean, it makes sense, but it's not what we're accustomed to. So if you go up to the apps up at the top left, you'll get this list of other things that you can install, download, and add on. One thing here, I wanna note again, this multi-selection. Like, why is this not in Trello? It's beyond me. You need a Chrome plugin to do it. Everybody else has it, but it's Trello pretty much. All right, next up, number five. I really love Aganti, and I'm really glad, A, I'm here in Europe because these guys are in Germany, and they have put a lot of effort into this tool. They're kind of like the dark horse in the background building this really, really simple tool. It's a Gantt chart, so it's the most basic project management tool. They have done a lot of improvement over the last year and a half. I've been keeping an eye on these guys, and it's really worth looking into. It's free. They have added synchronizing to a Google Calendar. They give you unlimited projects and teams. There's a full traceability audit for every change that's been done. You can draw your tasks now, which again sounds really mundane and basic. It didn't have it originally, and that was lower on my list because of stupid things like this. They've just added this maybe in the last three months. You can draw your task, and you can do the dependency chart, so X task is dependent on this one. And if you're planning out your project, that is really, really important. It includes a Chrome app, so you don't have to go to the site, and they support exports, which are really nice. They give you a lot of nice basic reporting. So for a small team, I would definitely look at this. This is really cool. This is one of their, this is the reports, doesn't really show you anything. This is a little bit better, so this is kind of how this thing looks. So what I'm trying to show is drawing an additional task, and you fill in the blanks as to what it is, and you can assign it, give it a deadline, add some other notes. If you drag it to make a dependency, it'll show up in the dependencies. It's got a nice UI, right? So adding a dependency is that easy. This was not possible three months ago. They are making a lot of progress, so if anything else, keep an eye on them, and come back and visit them in another couple months. But multiple teams, multiple projects, it's like, all right, that's why we're in the top five now. Number four, this is another one of my favorites. Tyga.io, this one is about as close as I can get to a true Jira replacement for a smaller team. It's Python-based, if you know Jira, you know how to use this. And again, one other, like from the developer perspective, having that integration with GitHub, or any other, like Bitbucket, any other repository is mandatory, so that you know what's going on. You can do this hosted for free, so you can try it out, basically, and then if you really want to use it, you pay subscription fee, again, the same kind of per month model. If you want to shell out 10,000 to support the development, you can get everything for 10K forever. They allow you to set this up on your own server, and they give you unlimited users and unlimited projects. So again, worth playing with. Setting up is tricky, is hard, because it's Python, it's not what you expect. But this is kind of a mix between Asana and Jira. So again, the list of activities, I go to my backlog view, I get the reporting to see what my burn down is like. Adding a story is real easy, right? And if I want to do multiple tickets, I just do one line per thing, and it'll automatically add them in. And now there's my stories, right? You can tag them, un-categorize them. You can customize the estimation, you can customize the workflow states, and it's got a pretty slick UI, right? So now I'm gonna add it to my sprint, and so on. And now if I go to the task board for the sprints, similar cat typical board set up, you can customize these however you want. It's not bad, it really isn't. And you get the nice reporting up at the top, which is like, how far are we? How many points burn down, and so on, and so on. So definitely worth, definitely worth looking at. Oh, block tickets, right, I forgot about this. So this is actually nice, and you can relate the tasks to each other, which is quicker by the search, which if you know Jira, everything is written the same way, you really can't do that. It's meant to be less ticket number versus the actual summary of the ticket, which is good, because it kind of reinforces the need to make the summary in English, not ABC-245, nobody knows what that is. And this is a, well, because I haven't burned anything down yet, but the reporting is actually pretty nice too. All right, let's keep going. I know there was one other thing I wanna make sure I put in here. Oh, and the team settings is really cool. It does it slightly differently. It's much more human organized, and the filtering is nice. I think I showed before, searching by user, and you can filter automatically what the tickets are, rather than having to go into Jira and create a quick filter, you can just do it on the fly. This also has plugins for HipChat and Slack, and again, I think I mentioned it, it has all the connections for Webhooks, GitHub, Bitbucket, and so on. All right, number three. Crocodile, crocodile, crocodile. Anyone here heard of this one? All right, so look at all the fun stuff you're learning. So this is yet another, after 10 of these early, okay, stop, please, another Kanban card system, but this, if the ones I showed you had a neat UI, this one is slick. What is really cool, when you join the project, they force, well, they don't force you, but they strongly recommend that you do a little onboarding game, so everybody knows what a ticket is, what's the point of a user story, where to put it, it goes in the backlog, you prioritize it, you plan out a sprint. Like all the basic concepts covered in the first 10 minutes. So this way your users are like, there's no excuse to not have them do their tickets right. I know it's never enough, but the fact that they made an attempt to make it a game, they actually give users points during the course of your onboarding, so you can make this a little competition, like who has the best score after the first week. I have not seen anybody else do this. For that alone, that's what gets us up into the number three spot. Another nice thing is that the triggers that they give you between workflow states, which I haven't seen, so if X kind of ticket goes between state A to state B, you can have it trigger an action, send an email, give it a flag, ping Slack. That's kind of nice, so all tickets going into QA could show up in your Slack channel. It's not cheap, but it's definitely worth investigating and it has a free trial, so it's worth playing with. So this is like a quick view inside of one of the backlog planning. Again, very simple, forgive me for this epic, I was just trying to fill something in, but very easy to start stubbing out a backlog, which is always to me one of the biggest challenges with a product owner based team, just put something in there. And now here you see the quick history of where it is, who it belongs to, and then I think I did this new epic. Okay, so then after I have my epic, you go up to the plan and you plan your sprint. So the tickets that I've added, and you basically pull them in and it does this little waiting crocodile thing. Now while this is going, you'll notice up at the top, you see that I have 1,225 points, because that was, I did most of the onboarding, so I earned all these points. And the first time you do a transition, the first time you write a story, the first time you close a ticket, you rack up all these points. So that gamification element, really, really cool. All right, one more. So this is the sprint level board. This is to just show you how you can organize and change this. You can customize this as you see fit. This is what comes out of the box, and you can change it exactly however you want. All right, so that was number three. All right, couple more that just missed the list. Ice scrum. So ice scrum is a French outfit, and how do I make this the right way? The intentions are good, but it's still clunky. It still needs a lot of work. It's Java-based. You can run it locally. Again, the install factor, really, really high complexity. There is a free cloud version now, which is nice. This didn't exist a year ago. You can set up one simple public project. If you want to pay for it, the pro version gives you an ice box and road mapping feature. So the long-term planning element is included, but it still needs work. So I'm going to say we'll revisit it. Another one is Gemini. This is another pretty good Jerry alternative. It has a very intuitive layout. Once you see it, you know where everything goes. The filtering is really nice, but, and it has an integrated chat, but the prices, it's kind of in the ballpark, but it's still a per user, not $10 a month for 10 users per user. This is really expensive. I think you can do better bang for the buck for this, basically. So the first one was like, it's not quite there. This one is just too freaking expensive. That one, the Gemini one looks a little bit like this, and it looks, well, I hate to put it this way. It looks like it hasn't been updated since 2003. This is like your Windows NT.NET looking tool. Blech. So that to me is like, yeah, not good enough. This is a.NET shop tool, right? This is not a Drupal tool. All right, one I haven't played with enough, but shows a lot of promises. Odoo, Odoo, Odoo? Will you marry me? Odoo, I don't know. This is another one that has that platform mentality of buying applications for the different pieces that you need. So you can get one for setting your own Salesforce type tool, another one for issue tracking, another one for manufacturing or inventory if you're doing point of sale. So this is a very broad platform view. I mean, and I say platform, like huge enterprise, not let's say the small, medium-sized agency that I have in my head as a target. It includes this Trello-like tool, which is kind of nice, and it has its own Slack light, but again, okay, the fact that you have your own Slack, Slack is good enough, you can do it for free. Why would you build your own tool? They include the time sheets and charting, which kind of tie into the inventory, manufacturing, point of sale, retail store kind of perspective. I think it's more than you possibly need. So that's why I didn't put it on the list. Weirdly enough, it's built in Postgres SQL and Python, which seemed kind of unusual to me, but whatever, I'm not a developer. What am I talking about? All right, number two. One thing everybody overlooks all the time, and so I'm putting it here in number two to reinforce it is pointing tickets. If you are still doing like the fist in Skype or everybody puts their hand up or everybody just types it into chat, you're not doing it right. It should be completely blind. Everybody votes and nobody can see what anybody else is doing. So I like pointing poker. There's a couple of these out there. If you haven't used it, try this one, and I'll show you how it looks like really quickly. You can figure out however you wanna do your sizing, if you wanna do SML XL for t-shirt sizing, or you wanna use Fibonacci or I don't know, letters, whatever you want, you can do it. It's very, very basic. You can go in and essentially start up a new session and you type in your name. You can join as an observer, which is basically the product owner not voting, and you can customize what the methodology you're using. So in this case, I'm doing Fibonacci sequence. If you're the first one there, you'll get an ID and that's what you share with everybody. So I'm in pointing poker slash one, two, three, four, five. Everybody logs in during grooming and you'll see everybody show up. And so what I would do is, and let me go to the next slide. So now I type in my ticket. I've got three people in here that have voted. I go in and vote and you see that we're not in consensus. I voted 13, the other two guys voted eight. So right away, you know where the difference is and you can call out that person in grooming and say, hey, why did you vote so big? Why did you vote so small? What are we not missing? If everybody is in the consensus, then it just says consensus and you move on. So you keep it very, very streamlined and there's a shock block at the top the time, how long it took to vote. So if you keep every ticket at no more than five minutes, you can blow through tickets in your grooming and that's how grooming should work. So that's why this is number two on my list because if you have a tool in your toolbox, this should be one of them. All right, number one. Take a guess what my number one is. I mean, come on. Don't say Jira. Trello, yes. Yeah, it's my number, it still is not my number one. You know why? It's easy, it's intuitive, it's cheap. It gets most of the job done. It's got integrations with all the other stuff. If you wanna go gold, it's still, it's not, and I have to double check that it's still $8 a month because I think it went up. But for the free one, it gives you all the important stuff that you need in one place, everybody can look at it, right? So I'm willing to sacrifice email notifications for having everything in one board that everybody knows what to do. The problem is it's missing traceability. It's not perfect, it's just number one on my list, but it doesn't have traceability, it doesn't have all that other stuff that is in the beginning of my presentation, but it does it, it does everything right. Everybody knows how to use it. So I'm glad, who's upset with me for making this number one? Okay, good, this is exactly what I wanted. I wanna instigate. So tell me why you don't think it should be number one. What do you hate about it? I know, see, that's the hook. There you go. I had you. Why? So the whole idea was that, yes, my number zero is Jira. Maybe I should say that one. Everything, the whole point of this was to be- When Jira is above the company people- Yes, my Mjolnir, Jira is my Mjolnir. That's exactly it. But I was trying to find, is there anything that comes close to it? This is probably the easiest one that will get me there. All the other ones have a lot of the pieces that go with it, but that's exactly, that's exactly the point of this. Now you see why this is such a hard deck to put together. So already, I talked about Jira. I talked about Trello. I'm not gonna show you this. Everybody knows this. You have encryption and the extra security that it now includes. You know what this board looks like. I don't need to, everybody knows what this looks like. I'm not gonna have to go through this. But what's more important, this is the thing you should know. If you don't know these, you're ready. If you know Jira key shortcuts, you should know these in Trello. How to quickly do stuff so you don't have to click on it. Hopefully everybody knows this stuff. Who here knows this already? Okay, good. So some of you, this will be good. Take this back and if you hover over a card and just hit space, it assigns it to yourself. That's like the easiest one. Label LB to switch between the boards so you can do everything quickly with a keyboard and then escape to get out of it. That's the one that I don't have in there. And the nice trick is copying and pasting from Excel. If you have a row-based list of tasks, copy it and it'll create all the tickets for you. Slurp it right in. Power user trick. So here's the list all over again in backwards order. Again, this is just my take, my attempt at this. There's probably other ones that are worth investigating but for the sake of time, this is a good place to start. So hopefully this will give you some good information to try and ask. So please, let me show you this. Oh, sorry, anybody else want? I'll put the deck up. See if I can do this. How do I go back? Oh, I get the spinning ball of death. Great. So while I'm waiting for this to come back really quickly, I have a boff later tomorrow on large-scale projects where I talk more about JIRA. So you're welcome to come to that. And I've got two sessions at the Acway booth today and tomorrow, one on JIRA tips and tricks. So that is, if you're interested in that, please come and check that out. That one is at 6.30, it's 18.30 tonight and I have another one that's on Wednesday. The large-scale projects, that's at 10.45 in one of the galleries upstairs. All right, and I can't go to them any more slides because I'm stuck. So I hope this was helpful for everybody. If you have any questions, come see me at the Acway booth downstairs and let's talk JIRA. Awesome, thanks guys.