On TechRepublic: 10 most annoying default configurations
BNET Business Network:
BNET
TechRepublic
ZDNet

June 30th, 2009

Failing with online backup

Posted by Michael Krigsman @ 4:03 pm

Categories: CIO issues, Enterprise 2.0, IT issues, SaaS, PaaS, and SOA

Tags: Online Backup, Carbonite, Mozy, Backups, Michael Krigsman

Seeking to back up 350GB in safe, reliable, off-site storage, I tried Carbonite and Mozy, two of the most respected names in the online backup market. Both products failed miserably to achieve my goals, each one in a perversely different way.

Carbonite offers a simple, set-and-forget solution that should make life easy. In my case, something bad happened along the way because I can no longer restore files reliably. This screen capture shows what happens when I try to restore files using the company’s remote access feature:

As you can see, Carbonite can’t find my selected file. Would this message inspire confidence that your backup is safe?

Carbonite tech support was quite helpful trying to diagnose and solve the problem. However, my luck ran out after support submitted the issue to the developers for further research and fixing. At that stage, support essentially said the developers will handle my issue when they want, with no time horizon and not even a pat on the back.

Based on that interaction, I decided to try Mozy instead.

Mozy takes a somewhat more configurable approach to its backup software, which I like. I transferred the first 200GB of data to Mozy with no problems and reasonably fast upload speeds of 1.5Mbps. Recently, however, my upload speed decreased to a level where large backups are no longer practical. This dialog box shows my current upload rate, which is slower than a dialup modem:

Read the rest of this entry »

June 29th, 2009

Enterprise 2.0: The Kumbaya irony

Posted by Michael Krigsman @ 4:11 pm

Categories: CIO issues, Cultural issues, Enterprise 2.0 Conference, Enterprise2conf, IT issues, Project management, SaaS, PaaS, and SOA

Tags: Enterprise 2.0, Tasks, Groups, Current Resource Allocation Process, Dissenters, Michael Krigsman

Last week I attended the Enterprise 2.0 conference in Boston. It’s one of my favorite events, primarily because so many online friends attend from around the world and I enjoy their company. Despite overwhelming good will among participants, the conference exposed gaps between expectations and reality that continue to plague the Enterprise 2.0 world.

Enterprise 2.0 aspirations. Enterprise 2.0 suggests a network of organizational activities involving collaboration, cooperation, and engagement as part of a broader ethos of social interaction in business. Professor Andrew McAfee, formerly of Harvard Business School and currently with MIT, coined the phrase Enterprise 2.0. Andy recently blogged about implications of this new system of thought on managing organizations and leading teams.

Andy’s blog elaborated on a piece in the Wall Street Journal by Gary Hamel, which describes “12 work-relevant characteristics of online life.” The post provides a convenient summary of an Enterprise 2.0 view of management:

Read the rest of this entry »

June 24th, 2009

Computer errors in public places

Posted by Michael Krigsman @ 7:14 am

Categories: IT issues

Tags: American Airlines, Board, Photograph, Computer, Corporate Governance, Productivity, Business Operations, Corporate Law, Michael Krigsman

Over the last few weeks, I’ve spent much time in airports and hotels to bring you, dear reader, strange and fascinating tales from the world of IT. During my travels, I keep an ever-watchful eye for interesting and bloggable tidbits. Fortunately, I hit pay dirt twice and have photos to prove it.

First, here’s a photo of the session announcement board at HP’s Software Universe 2009 conference, held at the Sands in Las Vegas. Note, this is a Sands issue and has nothing to do with HP:

…and a cropped, rotated version showing the error:

Read the rest of this entry »

June 22nd, 2009

HP connects IT investment, value, and transparency

Posted by Michael Krigsman @ 3:39 pm

Categories: CIO issues, Governance, Hewlett Packard, IT issues, Project portfolio management

Tags: Hewlett-Packard Co., Information Technology, IT Investment, Project Portfolio Management, ROI Analysis, Brian, Project Management, Tools & Techniques, It Operations, It service Management

Last week, I attended HP’s Software Universe 2009 conference to participate on a panel discussion around success strategies for deploying project portfolio management (PPM). I used the opportunity to speak with HP executives about their vision for the future of PPM and its relationship to enterprise value creation.

To understand the company’s PPM product direction, I spoke with four folks representing HP’s views on features, strategy, and customer implementation:

  • Paul Muller, VP for Strategic Marketing
  • Ken Cheney, Director of Products, IT Financial Management
  • Bruce Randall, Manager of Product Marketing, PPM
  • John Wills, Practice Principal for HP’s Business Intelligence Solutions group

HP’s primary strategic message about the future direction of PPM involves helping IT departments improve their ability to quantify project costs, benefits, and derived value, which Paul described this way:

We automate the spreadsheet Kung Fu that IT often uses to analyze financial data. Our goal is reducing decision-making cycle times and creating transparency that quantifies the business value of IT operations.

Ken Cheney elaborated on this message:

Many organizations find it difficult to get an accurate handle on IT costs. We link IT with the business services it delivers and assign value to help IT appropriately price these services. The future of PPM is helping organizations clearly see the total cost of ownership of all IT services.

HP’s strategy positions PPM as a building block in a broader IT financial management offering, as the following diagram illustrates:

Read the rest of this entry »

June 15th, 2009

Pentagon kills $6.3 billion missile technology project

Posted by Michael Krigsman @ 6:06 pm

Categories: CIO issues, Governance, Government projects, Project failures, Vendor relationships

Tags: Northrop Grumman Corp., Pentagon, Government, Supply Chain, Vertical Industries, Business Operations, Michael Krigsman

The Pentagon canceled Northrop Grumman’s Kinetic Energy Interceptor program amid accusations by Defense Secretary, Robert Gates, that the system’s design would not accomplish key military objectives.

It’s not an IT failure, per se, but certainly a great example of poor fit-to-purpose between technology and business requirements, leading to project abandonment and failure. Northrop Grumman had completed approximately $1.2 billion of work at the time of cancellation.

The Pentagon said it terminated the project for the “convenience of the government” and not because of problems with Northrop.

Northrop Grumman describes the system:

KEI is the Ballistic Missile Defense System (BMDS) element that is being designed to destroy enemy ballistic missiles during their boost and early midcourse phases of flight. It is also the first ballistic missile defense weapon system to be developed without the constraints of the Anti-Ballistic Missile Treaty.

Reuters said Gates stopped the program because:

Read the rest of this entry »

June 12th, 2009

TechCrunch Research: Big deal or not?

Posted by Michael Krigsman @ 6:22 am

Categories: Consulting, Uncategorized, Vendor relationships

Tags: TechCrunch, Advisor, PROJECT FAILURES ANALYSIS TechCrunch, TechCrunch Research, Investment, Finance, Michael Krigsman

TechCrunch, the opinionated startup-focused blog network, has launched a low-cost analytic research service. Given the company’s high profile, this research offering cannot be ignored. However, does this new TechCrunch initiative provide value to buyers or threaten established analyst firms?

TechCrunch describes its 1Q 2009 Report report this way:

[It] provides key take aways and statistical support for the major trends of Q1. The report covers trends in start-up foundings, products, financings and exits across a variety of technology sectors: consumer media and entertainment, social networking, cloud computing, mobile communications, search, advertising and ecommerce, consumer electronics and clean tech.

The report costs $149 and partially overlaps the outstanding, web-based MoneyTree Report, which is free and has been around for years. PriceWaterhouseCoopers and the National Venture Capital Association sponsor MoneyTree.

THE PROJECT FAILURES ANALYSIS

TechCrunch keeps its finger on the pulse of startups, writing with a colorful (some say arrogant) tone and style. This formula has propelled TechCrunch’s popularity and influence among those following technology startups and investment.

Read the rest of this entry »

June 6th, 2009

Field guide to interpreting CIO-speak

Posted by Michael Krigsman @ 7:51 am

Categories: CIO issues, IT issues, Uncategorized

Tags: Apple iPhone, CIO, Information Technology, E-mail, Strategy, Open Source, Online Communications, Management, Michael Krigsman

Do you need a universal translator to interpret and understand your organization’s CIO? Well, you’re not alone. Fortunately, blogger Thomas Wailgum comes to our rescue with a post explaining key CIO phrases.

I added quick reference categories to Thomas’ list and formatted it for convenient reading. Use this handy chart as a field guide to communicate more effectively with the CIO in your life.

One little note: CIOs are known to be a bit…shall we say, prickly, at times. Therefore, in the interest of politeness, and also not being fired, I suggest keeping this chart under wraps.

As a small mea culpa, I’ll share the words of Twitter user Mark O’Neill, who said to me, I sentence you to be taken from this place and made a CIO. May God have mercy on your soul.

What the CIO says What the CIO means
iPhones We think iPhones for our workforce – even though they are more expensive than the smartphone we have standardized on – might be something for us in the future. We’ll roll out iPhones when monkeys fly out of my butt.
Relations with the CEO The CEO and I have a great relationship. I can go into his office any time and talk about what’s going on in IT and how we can better meet the needs of the business. We found Terabytes of porn on his PC, and as long as he’s in charge, I’ve got a job.
Social media I’m currently talking with our executive board, legal team and CMO about the trade-offs of letting employees use social media at work. My 13-year-old daughter is talking me through what Facebook is.
Recessionary spending Despite the recession, innovation is still a key function in our IT department. My budget just got cut by 30 percent, I had to lay off 60 people, we canceled 10 core IT projects—innovation?! How ’bout just keeping the lights on?!
Vendor relationships With our core enterprise vendors, we feel like we have a true partnership, with lots of good communication. We despise them and beat them up on pricing every chance we get.
Security I’m not sure how our customer database could have been compromised. We had all the relevant security controls in place. I’m shocked we’ve been able to remain ‘breach free’ this long.
Responsiveness E-mail that to me. I’ll take a look and get back to you ASAP. Send it to my e-mail address, my secretary will print it out for me, highlight the important parts in neon yellow marker, then I’ll dictate my response back to her, she’ll type it into my e-mail account and send it to you next week.
Open source We’re very interested in how open-source technologies can help us reduce our overall vendor spend. Are you out of your freakin’ mind? Open source?! You’ve got to be kidding, right? Never!
IT / Business alignment We’re always working on the challenges of business-IT alignment. Everyone hates me and my staff.
[Image via iStockPhoto]

June 5th, 2009

21 ways to flog dead horse projects

Posted by Michael Krigsman @ 9:42 am

Categories: Uncategorized

Tags: Technique, Horse, Productivity, Performance Management, Workforce Management, Training And Certification, Human Resources, Michael Krigsman

After writing my last post, which was on this same topic, I learned about 21 special techniques organizations use to deny their true state of failure.

This is from the Humor Archives blog, but it’s actually not funny at all. In reality, this list is a sad and accurate commentary on denial in its various forms and manifestations:

  1. Buying a stronger whip.
  2. Changing riders.
  3. Say things like, “This is the way we have always ridden this horse.”
  4. Appointing a committee to study the horse.
  5. Arranging to visit other sites to see how they ride dead horses.
  6. Increasing the standards to ride dead horses.
  7. Appointing a tiger team to revive the dead horse.
  8. Creating a training session to increase our riding ability.
  9. Comparing the state of dead horses in today’s environment.
  10. Change the requirements declaring that “This horse is not dead.”
  11. Hire contractors to ride the dead horse.
  12. Harnessing several dead horses together for increased speed.
  13. Declaring that “No horse is too dead to beat.”
  14. Providing additional funding to increase the horse’s performance.
  15. Do a Cost Analysis study to see if contractors can ride it cheaper.
  16. Purchase a product to make dead horses run faster.
  17. Declare the horse is “better, faster and cheaper” dead.
  18. Form a quality circle to find uses for dead horses.
  19. Revisit the performance requirements for horses.
  20. Say this horse was procured with cost as an independent variable.
  21. Promote the dead horse to a supervisory position.

I just can’t believe the insight and accuracy of these observations. Please share your stories of organizational denial and corporate silliness.

[Thanks to Sarah Runge for bringing this list to my attention. Image via iStockphoto.]

June 5th, 2009

Kill your dead horse failures fast!

Posted by Michael Krigsman @ 5:16 am

Categories: CIO issues, Governance, IT issues, Project management, Uncategorized

Tags: Project, Investment, Workforce Management, Finance, Human Resources, Michael Krigsman

Some projects will never (as in no chance, baby) achieve intended goals, despite substantial investment of time, resources, and political capital. Even so, many organizations find it difficult to terminate these inevitable failures because of fear, denial, shortsightedness, or lack of consensus.

A post from the Self Improvement Revolution blog hits directly on difficulties associated with ending failures mid-stream:

But the resulting mindset for the project effort can often be so focused on getting the project back on track that it pays no attention to the fact that the project may very well be a dead horse that is still being flogged. It is wise to be open to the possibility that the project is a like a horse that will never run again. So stop flogging it!

It often takes courage to close a project prematurely because often you are likely to upset someone further up the hierarchy. Closing a project early is not for the faint of heart who are afraid to upset the boss, which is why independent consultants often step up to the mark and do the necessary.

There are many large smelly projects that were the brainchild of a C-level executive still laying in dark corners of companies. They have often become irrelevant, expensive and a complete waste of time and effort. No one has the courage to get the executive in question to face up to the fact that their project was not the best idea after all.

There’s truth hidden in the hyperbole of this excerpt.

Allowing a dead horse project to run its course means greater expense, more wasted time, and continued investment of political capital. As a result, the consequences of termination only become worse over time. For your own sake, kill these failures sooner than later.

[Image via iStockphoto.]

June 2nd, 2009

IBM: IT failure and social media disaster

Posted by Michael Krigsman @ 9:26 am

Categories: CIO issues, Enterprise 2.0, Failure 2.0, Government projects, IT Devil's Triangle, IT issues, Project failures, Tools, Uncategorized

Tags: Consultant, Information Technology, Social Media, Customer, Twitter, IBM DB2, IBM Corp., Lois, Michael Krigsman

IBM’s recent DB2 fiasco in the Philippines is a textbook case of Devil’s Triangle relationships causing conflict between a technology provider, third-party consultants, and a customer.

Although the situation is interesting, I never expected it to bubble over onto Twitter, demonstrating poor social media practice in addition to vendor/consultant arrogance.

The Twitter connection began when I tweeted a general request seeking an expert to explain technical aspects of DB2. IBM’s customer, a Philippine government agency, raised questions about DB2’s suitability to task, making the technical aspect relevant:

A consultant with DB2 expertise re-tweeted my request. So far, so good:

An IBM DB2 executive responded with the implication my request was somehow wrong, unethical, or not straightforward. Yes, the tactic definitely caught my attention:

Read the rest of this entry »

Michael KrigsmanMichael Krigsman is CEO of Asuret, Inc., a software and consulting company dedicated to reducing software implementation failures. Click here to discuss this post with him on Twitter. See his full profile and disclosure of his industry affiliations.

Email Michael Krigsman

Subscribe to IT Project Failures via Email alerts or RSS.

SponsoredWhite Papers, Webcasts, and Downloads

advertisement

Recent Entries

Most Popular Posts

advertisement

Archives

ZDNet Blogs

White Papers, Webcasts, and Downloads

SmartPlanet

advertisement
Click Here