History’s 15 Worst Named Tech Products

3_Qwikster-400x224Check out the following post on Intertech’s blog…

What’s in a name? If we’re talking about some of the products on the list you’re about to read: some really bad ideas. While not all of History’s 15 Worst Named Tech Products failed because of their christening, they certainly didn’t help themselves out by choosing the names they did. From bad hygiene admissions to inadvertent racism, we proudly give you the worst of the worst.

13 Crazy Expensive Software Products

Crazy-Expensive-SoftwareMany people mistakenly believe that computers are what make the world go ’round – that we can’t do anything without them, and if they went away tomorrow, the world would slip into a cultural black hole. In reality, computers don’t make the world go ’round. Software does. And sometimes that software gets quite expensive. As you’re about to see, programs can cost anywhere from thousands to hundreds of thousands depending on the scope and specificity of purpose. Whenever possible, we’ve tried to slap an exact number on the product for you. At the very least, you’ll get an estimate.

Unfortunately, when you’re dealing with enterprise-type software, it’s impossible to find a hard number on the web. Quotes often vary depending on the circumstances. Still, if you left those types of software programs out of a list like this, it wouldn’t be an accurate representation. Our goal: to show just how valuable these 13 Crazy Expensive Software Products are to the companies and the people who use them. Here goes!

Prescription for a Healthy IT Project (Post 6 of 6)

Happy-Customers-Happy-Company_25877As I note in my book, “Building a Winning Business,” good customer-vendor relationships require both parties to participate, communicate and share responsibility for a successful outcome. Are you a good customer? This might seem like an odd question. After all, isn’t it the vendor’s responsibility to make the relationship work? While a vendor must go the extra mile, the customer also has obligations in making vendor relationships effective. While it might sound trite, I honestly believe the same qualities apply to a good customer as to a good employee, friend or even a spouse: trust, mutual respect and appreciation, and sharing that shows that each is committed to the success of the partnership.

On a practical level, this translates into the following behaviors on the part of customers:

  • Clearly communicate expectations. Assumptions are not helpful. Customers who share their expectations openly and early are much happier with their project outcomes.
  • Provide clear direction and feedback to the project team to control scope.
  • Understand that changes to a project that modify the original base requirements often are necessary to provide the best solution.
  • Take the initiative in quickly removing roadblocks for those doing the work.
  • Share responsibility for success of delivery.
  • Work to diminish political boundaries.
  • Be actively engaged in the process all along the way.
  • Do not overreact to minor setbacks.
  • Communicate on a daily basis.
  • Pay on time.

Prescription for a Healthy IT Project (Post 5 of 6)

img_rx_001

Once you’ve established the basic expectations and defined who has responsibility for what, it’s time to clearly define what’s in and what’s out of the project.  In the world of Agile, this is choosing what to tackle in a project’s backlog.

With a high profile and highly political project like the federal health insurance website, it’s highly possible that the project terms were changed frequently to appease political forces. A mistake made was to draw a line in the sand around a specific date.  While project management methods have changed over time, the old adage is still true, “Time. Budget. Features. You get to choose two of the three.”  If the project was handled properly, changes – and their implications for the timeline and budget –would have been handled correctly.

It seems obvious that when project additions occur (and always they do), give and take must happen. If there are additions, the client needs to expect more time and/or budget.  If not, more features obviously translates into the need to let go of other aspects of the project to keep the bottom line from increasing.

Perhaps most important of all, is the establishment of sprints. Sprints keep projects moving forward smoothly.  Even small projects should have several sprints.

Finally, success is a two way street.  Not all the responsibility for making things work lies with the vendor.  In my last post in this series I will discuss the importance of being a good customer.