jump to navigation

First day at the technology conference June 12, 2007

Posted by Matsu in Information Technology, Management, Open Source, Software, Technology.
1 comment so far

Today I attended pre-conference meetings and then the opening events for the technology conference I am attending in Pennsylvania. So far, there have been two surprising discoveries.

First, this past year several of the other affiliated colleges and universities have struggled with staff cuts as they experienced varying degrees of enrollment declines (or in some cases a lack of growth – flattening enrollment). This has placed a great amount of stress on the I.T. departments as they either had positions eliminated or experienced hiring freezes.

Second, it was a pleasant surprise to find out that another school is using Ruby on Rails for some application development. In fact, they used that open source development platform for three different applications they developed in-house. I can’t wait to get my programming staff in touch with that other campus’ programmers who use Ruby. I’m sure they will have much to talk about and may even be able to exchange some knowledge. It is unfortunate that I couldn’t have my programmer(s) here to attend the conference with me. But, that’s a different story…

Tomorrow I give my talk on what CFO’s need to know about CIO’s. I hope it’s well received.

Day one is good. Looking forward to the rest of the week.

Advertisements

Two fun presentation topics… May 30, 2007

Posted by Matsu in Business, Education, Information Technology, Management.
1 comment so far

The second full week of June I am planning to give a couple of presentations at a technology conference that I think will turn out to be a lot of fun. The first presentation is titled, “Ten Things Every CIO Should Know About CFO’s.” The subtitle of that talk could be, “What it takes for CIO’s to successfully work with CFO’s.”

(For those readers who are not familiar with the acronyms CIO and CFO, they stand for Chief Information Officer and Chief Financial Officer, respectively.)

The second talk is the same thing from the opposite perspective. Yup, you guessed it, “Ten Things Every CFO Should Know About CIO’s.” If you have not figured it out, I work as a CIO and I report to the CFO. He will be helping me with the second ‘top ten’ list of things to know.

The particular conference I am attending is a joint conference of higher education CFO’s and CIO’s (and other IT managers), so the topics seemed especially appropriate. I’ll let you all know how it turns out. And, after the conference, I’ll post my two lists of ten things.

The Unconference – An open source style conference May 21, 2007

Posted by Matsu in Information Technology, Management, Open Source, Technology.
add a comment

If you are like me and attend several technology conferences each year, you find yourself wondering if you still get as much out of it as you used to, when you were younger and knew less. At regular technology conferences the usual ‘sage on the stage’ or ‘panel of pendants’ tell the audience something they already know.

Well, I just stumbled across an old blog post by Dave Winer who wrote about a new model known as the Unconference. The unconference is a conference where the audience provides the content and expertise (much like on an open source development project). Interesting concept. Think about it.

Tired of your I.T. person? May 10, 2007

Posted by Matsu in Business, Information Technology, Management.
4 comments

There is a commercial running on American television by an office supply company called Staples. They show this very young 20-something guy walking in, not appropriately dressed, then one manager says to another, “I thought we got rid of that guy.” The second manager responds with, “No, we can’t. He’s the only one that knows how to fix our computers.” Next, the I.T. guy enters his office and begins to play computer games while an employee asks him to take a look at his computer. The I.T. guy in the ad says he’s on a break and not to bother him.

Now, I believe that very few modern offices put up with that kind of behavior in any employee, I.T. guru or not. In fact, I work in I.T. and I would fire him. I would not want him representing my department. Nobody is truly indispensable and should never be able to get away with that kind of behavior. It shouldn’t be tolerated in any profession, much less the I.T. profession.

I imagine that most I.T. professionals, myself included are offended by this portrayal of an I.T. pro. It’s more than a little disconcerting that Staples chooses to portray the profession with such a negative stereotype.

That being said, there is some truth to the idea that I.T. people tend to be a little arrogant and are not always friendly with non-IT people. Some of us have to work at it harder than others, but we should all try to be more supportive and cooperative with those inside our organizations that are outside of our I.T. departments. After all, our job is to support them and we should do so without belittling them or making them feel like they (the non-technical person) don’t know anything about technology.

If you have not seen it before, I recommend that you visit the It Ought To Be Simple website. There is a wonderful essay there (actually more than one) about the negative attitudes and behavior of I.T. people. He makes some great points and we should all learn from it.

Upgrade now or upgrade later, that is the question May 6, 2007

Posted by Matsu in Business, Information Technology, Management, Microsoft, Software, Technology, Uncategorized, Windows/Microsoft.
7 comments

A good friend of mine has a favorite phrase, “Timing is everything.” While they may not be a technology professional, they certainly know the secret to upgrading systems — timing. Performing upgrades at the right time makes all the difference. So, when is the right time? When should you switch to new versions of applications or operating systems?

I am presently faced with that question where I work. Like the rest of the world, we must decide when it is best for our organization to upgrade to Microsoft Office 2007 and Windows Vista. Of course, they are two separate decisions as you can install Office 2007 on Windows XP and, as far as I know, you can also run Office 2003 on Windows Vista (though I don’t know why one would choose to do that).

While I talk about Office 2007 and Windows Vista upgrade in this post, these questions and decisions apply to all types of software, even open source software. The concerns and problems (or opportunities) are just as real with Apple’s Mac OS X and any flavor of Linux. So, you may want to continue reading even if you don’t use Microsoft Office or Windows.

To answer the upgrade question for your organization, you must consider both business and technology factors. But, beware! The one reason that should never be used when deciding if to upgrade is because it’s “new and shiny.” As in, “it’s new, it’s cool, so it’s got to be better.” Some technology professionals may fall prey to that siren call, but you shouldn’t. And, if your top management gives you that argument, be sure to give them a dose of reality by providing a list of pros and cons for the upgrade. That will let them know you are seriously considering it and looking at it from all of the angles.

First, let’s consider the business opportunities. Business reasons include performance improvements, which may mean higher productivity, and greater security, which may mean less risk (and in the case of viruses, it can mean less down time). Of course, there may be business reasons to upgrade because of new functions or features that provide an advantage over the current (older) version of the software. And, in today’s highly regulated business environment, it’s possible that the new version of software is necessary to be compliant with some new government regulation. Those are just a few reasons that an upgrade would be needed or advantageous.

There are also business reasons not to upgrade. For one, it may require the users to learn a new way of doing the same old things. What I’m talking about is a change in the software’s user interface. That is certainly something that applies when considering upgrading to Office 2007. The user interface is radically different from previous releases of Microsoft Office. Microsoft argues that while there is a learning curve to their new version of Office, once learned it is more intuitive and users will do things easier or faster. Hmmmm. It’s too early to say how true that may be. And, if you don’t have time for your users to relearn how to use a word processor or spreadsheet, then maybe you should wait for a time that would allow people to learn the new software without impacting (dramatically) their productivity. (There can be a whole blog post about training, so I won’t go into the many options and best practices here.)

Another reason not to upgrade is the cost. You not only must consider the upgrade license costs, but also any hardware costs (if better, newer, faster, hardware is required). That may not apply to Office 2007, but it certainly does apply to Microsoft’s new version of Windows (Vista). Probably the greatest reason that businesses are holding off on rolling our Windows Vista is the fact that newer hardware is a requirement.

According to this story by Cnet News, Dell and Intel are holding off on upgrading to Windows Vista. The reason for their decision is largely based on the stability and security concerns of a “1.0” release of software. Therefore, they are waiting for the first Vista update or service pack (SP1) before conducting a large rollout of Vista to employees. I think that it shows both a level of understanding of technology and the business impact to make that decision. And, I believe it’s the right decision for them.

While I have not highlighted technical reasons to upgrade or not to upgrade, they do exist. In my discussion of the business reasons they had foundations in technical reasons. After all, you can’t totally separate the technical from the business impact or potential opportunities. Just to cover all of my bases, you should consider the following technical issues when determining the best time to upgrade: license management (Vista is different and significantly increases administrative overhead just for taking care of licensing), impact on infrastructure (servers, network, directory services), and compatibility with existing systems (legacy applications, mission critical functions, etc.).

Of course, you should not make the decision to upgrade any application or operating system without thorough research. That means testing the applications on your systems (test systems, not live/production systems). After determining all of the upgrade implications then you must address any compatibility or performance issues that you discover. After all, you do not want to find out halfway through your deployment that some mission critical application or process won’t run. Only after a complete discovery of all problems should you consider the best time to upgrade your organization’s computers.

I have already stated that the timing must be determined by each organization because they all have different needs and issues. But, for my organization we have established some best practices when it comes to the timing of an upgrade. We have established a policy that we don’t install new application software on end-user’s computers until at least three months from the release (ship) date. And, for operating system upgrades, we extend that timeline to approximately six months. Again, this is a guideline or ‘rule of thumb’ but we tend to stick fairly close to it. By the time an application is three months old or an operating system is six months old the marketplace has found and possibly fixed any problems like compatibility issues, security flaws, and performance shortfalls.

One final piece you should consider relates to technical support. Waiting three or six months gives the technology support staff sufficient time to ‘play’ with the technology and become more comfortable using the new software. More experience and comfort with the new software translates into better support.

So, when do you plan to upgrade all of the computers in your organization to Office 2007 or Windows Vista?

ITIL as a strategic business tool April 22, 2007

Posted by Matsu in Business, Information Technology, Management, Technology.
add a comment

Most I.T. professionals are familiar with ITIL (the Information Technology Infrastructure Library) as a ‘best practices’ for IT operations but few have grasped the strategic advantage of ITIL for business.

The current edition of CIO magazine has this wonderful article which gives the perspective of ITIL as a strategic planning tool. Check it out.