Woz will be at Innovate 2013!
And so will the Jazz Jumpstart team

OMG, Woz is coming to Innovate!

No,  I never made a fish tank out of my Mac SE. I did own a Mac clone (Yay, Power Computing!), and have a broken System 7 watch someplace from that operating system’s launch. (I also have a Windows 95 key chain someplace, but that’s another story…) When MacWorld was in Boston, I’d take a day from work to wander the slow floor, check out the new gadgets and collect tee-shirts. These days, my work-provided lenovo ThinkPad stands out in a house full of Macs and iPods.

But Woz is going to speak at Innovate??!! I’m not going to miss that.

Rational’s two seasons

At Rational there are basically two times of the year: pre-Innovate and post-Innovate. Stuff needs to be wrapped up in May for the annual conference, or it has to wait until after. Sure sometimes there are other deadlines, but for some of us, the first week in June is how we measure the working world. I know some of our customers look at it that way too, asking for defects to be fixed before June, or using the conference to get some fresh ideas and work started for the rest of the year.

Innovate is where we join our partners to showcase products all across the Rational portfolio. Customers present on the cool things they’re doing, and some of us head down to Orlando, Florida (June 2 to 6 this year) to give presentations, workshops and take part in interactive discussions. Conferences have adjusted to the times over the years. I think my biggest MacWorld tee-shirt haul neared 14. At Innovate, there’s always some swag, but given I have to fly there and back, I’ll collect pens instead.

Jazz Jumpstart is all over Innovate

So maybe Woz gets a keynote under the Klieg lights, but the Jazz Jumpstart Team is all over Innovate, helping customers, meeting colleagues, saying hi to new friends, but most importantly, letting the world know just how awesome the Jazz products are and what wonderful things you can do with them. The best team in Rational is a big part of the Innovate experience. Here are some highlights:

  • SudhakarFreddy Frederick reveals how to best use RTC for Android development (Solving the Android Platform Development puzzle with RTC, MDEV-1120B, Wednesday, June 5, in Asia 3 from 1:45pm to 2:45pm)
  •  Ralph Schoon pulls back the curtain on All You Need to Know About Customizing RTC  (RDA-1051, Thursday, June 6,  Swan 9 from 11:00am to noon)
  • Rosa Naranjo provides Strategies for Planning and Completing and Successful CLM Upgrade (RDA-1481, Tuesday, June 4, Swan 9 from 4:15pm to 5:45pm)
  • Jorge Díaz explains Building Mainframe Applications with RTC Enterprise Extensions (SZ-1203, Thursday, June 6, Northern E2 from 9:45am to 10:45am)
  • Jim Ruehlin holds down the big CLM Process Enactment Workshop (WKS-1116, Tuesday, June 4, Swan 8 from 3:00pm to 6:00pm) and gets help from Jorge and Ralph too. (I get to count chairs, I think…)
  • Our team’s fearless manager Dan Tox Toczala and I discuss all about Maximizing your Jazz Environment and Performance (RDA-1327, Wednesday, June 5, Swan 9 from 4:15pm to 5:45pm). We have an interesting “gimmick” planned for this year, so don’t miss it.
  • You can also catch me co-presenting Jazz High-Availability and Disaster Recovery Levels and Best Practices (RDA-2485, Tuesday, June 4, Swan 9 from 1:45pm to 2:45pm)

These are just highlights: Check our individual teams’ blogs for what else we’re up to. Titles, days, locations and times can change, so keep an eye on the conference schedule and the TV monitors posted throughout the site.




Our changing audience

Really, who are you?
Not yet introducing the new jazz deployment wiki

In our corner of the world, some of us on the Jazz Jumpstart universe are wondering who will spill the beans and mention the new jazz Deployment wiki first. I don’t think it will be me.

We’re all working on a new way for the Jazz ecosystem to present information, specifically deployment information. Not just “Insert tab A into slot B” types of material, but the more opinionated, specific stuff you’ve told us you want to hear. We have folks working on Monitoring, Integrating, Install and Upgrade, and other deployment topics. I own the Performance Troubleshooting section.

When the actual wiki rolls out (and I can actually talk about it), I’ll talk about some of the structure and design questions we wrestled with. For now I want to talk about one of the reasons why we’re presenting information differently, and that’s because we think our audience has changed.

IT used to be simple

Ok, so may IT was never actually that simple, but it was certainly a lot easier to figure out what to do. One of IBM Rational’s strengths is that we’ve built strong relationships with our customers over the years. Personally, a lot of the customers I know (and who I think know me) started out as ClearCase or ClearQuest admins and over time have evolved now to Jazz/CLM admins. Back when, there was pretty much a direct relationship with our product admins, who in turn knew their end users and had ownership of their hardware environments.

This picture describes what I’m talking about (they’re from a slide deck we built in 2011 to talk about virtualization some of which lives on elsewhere, but these pics are too good to abandon):


The relationship between Rational Support / Development and our customers remains strong and direct. Over the years it’s the context of our customers product administrators that has shifted in many cases:


Consolidation, regulation, governance, compliance, etc., have all created additional IT domains which are often outside the customers’ product administration. There are cases where our relationship with our customers’ product administrators remains strong but we’ve lost sight of their context.

Here’s another way to look at the old model, this is specifically around hardware ownership:


Back in the day, our customers’ product administrators would request hardware, say a Solaris box (yes, I am talking about many years ago…), the hardware would arrive and the Rational product admin would get root privileges and start the installation. Nowadays, the hardware might be a VM, and there might be all sorts of settings which the admin can’t control such as security, database, or as is pertinent to this example, VMs.



This is a long winded way to say that we’re well aware we have multiple audiences, and need to remember that product administrators and IT administrators may no longer be the same people. Loving a product and managing how it’s used isn’t quite the same as it used to be. We’re trying to get better at getting useful information out there which is one of the reasons for the new deployment wiki.