1 00:00:00,000 --> 00:00:08,000 We are at RSDC 2008 in Orlando, Florida, of course, and we've gotten a fancy room recorded here. 2 00:00:08,000 --> 00:00:11,000 You can see we've got some metal statues and pictures. 3 00:00:11,000 --> 00:00:12,000 Very nice. 4 00:00:12,000 --> 00:00:14,000 Exactly. And would you like to introduce yourself? 5 00:00:14,000 --> 00:00:18,000 Sure. My name is Mike O'Rourke. I'm the Vice President of Product Development here at Rational. 6 00:00:18,000 --> 00:00:21,000 So what does that mean your responsibilities are exactly? 7 00:00:21,000 --> 00:00:24,000 Well, so I'm responsible for the core products at Rational. 8 00:00:24,000 --> 00:00:31,000 Core products meaning there's three areas of development, one being the telelogic acquisition, which isn't fully integrated yet, 9 00:00:31,000 --> 00:00:36,000 and the other really being the system Z and I areas, and that's owned by Hayden Lindsey. 10 00:00:36,000 --> 00:00:44,000 I own pretty much all the kind of core Rational products across the development lifecycle from requirements to change and release management 11 00:00:44,000 --> 00:00:49,000 to testing, portfolio and project management, so really the full lifecycle. 12 00:00:49,000 --> 00:00:50,000 And you came in through BuildForge, right? 13 00:00:50,000 --> 00:00:53,000 I did. This is my second go around. 14 00:00:53,000 --> 00:00:54,000 Right. 15 00:00:54,000 --> 00:00:57,000 What's that Al Pacino line and Godfather, they won't let me go. 16 00:00:57,000 --> 00:00:58,000 They pull me back in. 17 00:00:58,000 --> 00:00:59,000 They keep pulling me back in, yeah. 18 00:00:59,000 --> 00:01:02,000 I was originally, I was early on at Tivoli. 19 00:01:02,000 --> 00:01:05,000 I came through that acquisition and this time through BuildForge. 20 00:01:05,000 --> 00:01:10,000 So one of the big announcements here at RSCC was around Team Concert, of course, continuing with the jazz metaphor for everything, 21 00:01:10,000 --> 00:01:13,000 which is sort of the first go around of commercializing jazz. 22 00:01:13,000 --> 00:01:14,000 That's right. 23 00:01:14,000 --> 00:01:17,000 And you want to just quickly explain what sort of Team Concert does? 24 00:01:17,000 --> 00:01:18,000 Sure. 25 00:01:18,000 --> 00:01:23,000 Jazz is the platform, kind of the integration platform that we have that provides a set of capabilities, 26 00:01:23,000 --> 00:01:31,000 things like collaboration and security and project management and dashboards and a variety of other things. 27 00:01:31,000 --> 00:01:36,000 So the goal over time is that all rational products will essentially be jazz. 28 00:01:36,000 --> 00:01:38,000 Our first product, as you mentioned, is Team Concert. 29 00:01:38,000 --> 00:01:42,000 And what Team Concert is really focused at is just the developer side of the house. 30 00:01:42,000 --> 00:01:48,000 So the developer being the applications the developer typically uses are an SCM, a Source Control Management System, 31 00:01:48,000 --> 00:01:52,000 a Work Item or Defect Tracking System, and a Build System. 32 00:01:52,000 --> 00:01:57,000 And so we've taken those three applications and essentially plugged them into the jazz framework, 33 00:01:57,000 --> 00:02:05,000 where they get to now share all that information across the jazz framework as well as become kind of automatically tightly integrated. 34 00:02:05,000 --> 00:02:13,000 And so Team Concert is really the first jazz-based release, but we've got other things like quality management for the testing community, 35 00:02:13,000 --> 00:02:18,000 as well as requirements definition for the requirements or project management. 36 00:02:18,000 --> 00:02:21,000 So where does an IDE fit into that? 37 00:02:21,000 --> 00:02:25,000 Because I think you talked about version control and task management and the third component, 38 00:02:25,000 --> 00:02:28,000 but where is sort of like sitting down and writing the code fit? 39 00:02:28,000 --> 00:02:34,000 Well, so if you think about an IDE, what an IDE is about, whether you're choosing Visual Studio or you're choosing Eclipse, 40 00:02:34,000 --> 00:02:39,000 and for some people, not even an IDE, just a nice visual web-based interface, right? 41 00:02:39,000 --> 00:02:42,000 What it's really all about is kind of integration on the glass, right? 42 00:02:42,000 --> 00:02:45,000 Help me make all -- I don't want to change windows. 43 00:02:45,000 --> 00:02:48,000 I don't want to do all those things. I want it to come together in the glass. 44 00:02:48,000 --> 00:02:55,000 What jazz and Team Concert are about is taking that same concept and making it available to the team, not just to you, on a server. 45 00:02:55,000 --> 00:03:02,000 So whatever your IDE is, whether it's Visual Studio or Eclipse or web-based, all of those have, if you will, 46 00:03:02,000 --> 00:03:05,000 a view into those integrations and capabilities. 47 00:03:05,000 --> 00:03:10,000 So if you're using Visual Studio, if you're using Eclipse, you can still use all the capabilities, 48 00:03:10,000 --> 00:03:16,000 the integrations of Team Concert through your own IDE, but now you don't get just desktop integration. 49 00:03:16,000 --> 00:03:19,000 You get server and team-based integration across the world. 50 00:03:19,000 --> 00:03:24,000 So I'm sort of assuming that Team Concert reaches into Eclipse or Visual Studio with the plug-in or whatever you call it. 51 00:03:24,000 --> 00:03:25,000 Absolutely. 52 00:03:25,000 --> 00:03:26,000 That's the integration mechanism. 53 00:03:26,000 --> 00:03:27,000 That's the integration into the IDE. 54 00:03:27,000 --> 00:03:28,000 Right. 55 00:03:28,000 --> 00:03:37,000 But the server aspects of, you know, keeping conversation logs and collaborating and security and agile planning 56 00:03:37,000 --> 00:03:39,000 and all those kinds of things are kept on the server. 57 00:03:39,000 --> 00:03:43,000 More generally, not necessarily just with Team Concert, but for rational more generally, 58 00:03:43,000 --> 00:03:48,000 I mean, would you say that there's -- what's sort of the breakout of the constituency that you have as far as the developers? 59 00:03:48,000 --> 00:03:50,000 Is it way heavier on one side? 60 00:03:50,000 --> 00:03:55,000 And I've been trying to make myself remember this now, but with TeleLogic, you have sort of the embedded -- 61 00:03:55,000 --> 00:03:57,000 The embedded systems type developers, right? 62 00:03:57,000 --> 00:03:58,000 Yeah, yeah, yeah. 63 00:03:58,000 --> 00:04:01,000 Where they're dealing with both hardware and software and meshing the two together. 64 00:04:01,000 --> 00:04:02,000 Right. 65 00:04:02,000 --> 00:04:05,000 And that was the thrust behind buying TeleLogic. 66 00:04:05,000 --> 00:04:14,000 I would say typically the rational tool set and certainly the way where we sell to is typically what you might call the corporate developer, right? 67 00:04:14,000 --> 00:04:15,000 Right. 68 00:04:15,000 --> 00:04:16,000 Or the IT developer. 69 00:04:16,000 --> 00:04:21,000 They're developing to deliver to an in-house production system, right? 70 00:04:21,000 --> 00:04:22,000 Right, right. 71 00:04:22,000 --> 00:04:23,000 They're not reselling the stuff or selling it, I guess. 72 00:04:23,000 --> 00:04:24,000 Right, right. 73 00:04:24,000 --> 00:04:33,000 Now, we have a variety of our tools that also get sold to ISVs, but I would say ISVs tend to more generally be partners, 74 00:04:33,000 --> 00:04:38,000 where we're in their partner program, they're in our partner program, we tend to swap code. 75 00:04:38,000 --> 00:04:45,000 We don't tend to get the higher dollar, higher value of return for those folks, even though, obviously, software is their business. 76 00:04:45,000 --> 00:04:46,000 Sure. 77 00:04:46,000 --> 00:04:48,000 But I think what we're finding is software is pretty much everybody's business. 78 00:04:48,000 --> 00:04:49,000 Right, right. 79 00:04:49,000 --> 00:04:56,000 And so, you know, where we tend to focus on is in the corporate areas and now with TeleLogic, the systems areas. 80 00:04:56,000 --> 00:04:57,000 So, being from BuildForge. 81 00:04:57,000 --> 00:04:58,000 Yeah. 82 00:04:58,000 --> 00:05:04,000 You know, I'm always curious in asking sort of like what the next sort of broad innovation in some category is going to be. 83 00:05:04,000 --> 00:05:10,000 And it seems like, and maybe you have a different view, but it seems like in builds, managing builds, 84 00:05:10,000 --> 00:05:17,000 just the idea of a continuous build was a pretty, you know, a simple idea, but a pretty big innovation that occurred. 85 00:05:17,000 --> 00:05:24,000 And, you know, I'm curious if you're seeing or thinking about any of the next like simple big ideas that would be wide affecting in the builds. 86 00:05:24,000 --> 00:05:30,000 A couple of them that we're thinking of, one of which is that what we're finding is, if you think about when the build happens, 87 00:05:30,000 --> 00:05:36,000 either for the developer or for, you know, the company or for the project, that's when everything comes together, right? 88 00:05:36,000 --> 00:05:37,000 Yeah. 89 00:05:37,000 --> 00:05:41,000 That's when you find, you're pulling DLLs, you're finding source code that may have been pulled from open source, 90 00:05:41,000 --> 00:05:46,000 third parties are delivering things to deliver your final set of executables, right? 91 00:05:46,000 --> 00:05:57,000 So what better time than to start checking overall code health, things like which teams are actually delivering higher quality code versus other teams? 92 00:05:57,000 --> 00:06:02,000 Those are the kinds of things you don't get if you're doing things on an individual desktop by desktop basis. 93 00:06:02,000 --> 00:06:04,000 You have to get it kind of when it all comes together. 94 00:06:04,000 --> 00:06:08,000 Sort of doing analysis, if you will, at the group level instead of, yeah. 95 00:06:08,000 --> 00:06:15,000 You know, static trend analysis, looking for everything from memory leaks to is this open source, those kinds of things. 96 00:06:15,000 --> 00:06:16,000 Right. 97 00:06:16,000 --> 00:06:17,000 So that's kind of one side of it. 98 00:06:17,000 --> 00:06:21,000 The other side of it is really this notion of, so now that I've got a build, what do I want to do with it, right? 99 00:06:21,000 --> 00:06:23,000 So now that I've got something, well, I want to test it. 100 00:06:23,000 --> 00:06:26,000 I want to deploy it to a set of systems. 101 00:06:26,000 --> 00:06:36,000 Unfortunately, those set of systems, just take any of the rational products, could be anything with, you know, five different flavors of an operating system, 102 00:06:36,000 --> 00:06:40,000 four different databases, two different LDAP integrations, whatever it might be. 103 00:06:40,000 --> 00:06:42,000 So how do I provision that? 104 00:06:42,000 --> 00:06:43,000 How do I ship it there? 105 00:06:43,000 --> 00:06:51,000 Because many organizations are spending 30, 40, 50% of their time, that back into the cycle, doing nothing but taking machines up and down. 106 00:06:51,000 --> 00:07:04,000 The more that you can tie that build process into the automated provisioning, deployment, reservations, finding the right systems, getting it there and executing the tests, 107 00:07:04,000 --> 00:07:10,000 you know, you can save huge volumes and then, obviously, dramatically decrease how long it takes for you to get to build. 108 00:07:10,000 --> 00:07:11,000 Right. 109 00:07:11,000 --> 00:07:12,000 Absolutely. 110 00:07:12,000 --> 00:07:18,000 We see the build as being a very critical place in the development lifecycle where so many things are coming together. 111 00:07:18,000 --> 00:07:22,000 And if it's done wrong, it's going to hurt you for the rest of the development lifecycle. 112 00:07:22,000 --> 00:07:23,000 Right, right. 113 00:07:23,000 --> 00:07:24,000 Well, great. 114 00:07:24,000 --> 00:07:25,000 Well, I appreciate you spending so much time with us. 115 00:07:25,000 --> 00:07:26,000 Well, thanks. 116 00:07:26,000 --> 00:07:27,000 Thanks. 117 00:07:27,000 --> 00:07:28,000 Appreciate it. 118 00:07:28,000 --> 00:07:29,000 Good stuff.