Consider the following scenario-typical in many application development
organizations. A major new release of an application has just gone into
production. Although the development and QA teams endured many late nights of
coding and testing, and consumed large quantities of delivered pizza, the
project missed its ship date. Still, customers are happy with the product and
are giving positive feedback. By many definitions, the team has produced a
Then, a new, large business opportunity requires the rapid implementation of
a significant new feature in the product. The tired and over-worked
development team struggles with how, or even if, it can meet the new
requirement. They are concerned that the new feature will break the existing
product and predict a lengthy development cycle.
Schedule overruns, tired staff, and difficulty in changing or adding
I'm not in love with "requirements". There are some who think that
"Requirements" are the be-all and end-all for building great software.
They're not wrong, but they are off by a third of a bubble.
Great software companies come from creating and bringing to market (with a
great "go to market" strategy) quality software that solves one or more
significant problems for an appropriately chosen target audience - and does
so measurably better than alternative solutions.
How does such successful software happen? Certainly not by accident.
Understanding the Target Customer
It comes from... (more)
The purpose of this article is to tell you how to take a perfectly good (or
even a great) product that you've potentially spent years and millions of
dollars creating - and thoroughly and efficiently ruin it in the shortest
amount of time possible.
"Why would I want to do that?," you might ask. Honestly, I don't know
why. But there must be a good reason because I see it happen with shocking
For those of you who have read my article "Are You Your Own Worst Enemy?,"
that article was written to help products succeed in the marketplace. I'd
advise you to ignore that ... (more)
Apple's Surprising Marketing Blunder
Along with hoards of other people, I upgraded my perfectly good iPhone 4 for
the new iPhone 4S. Why? Siri. Am I happy? No.
I "listened" to the iPhone 4S launch - from live blog streams. I was honestly
quite disappointed. A faster processor? The iPhone 4 was fast enough for
me. Same "defective" exposed-glass design that is guaranteed to shatter the
first time you drop it (my first iPhone 4 lasted two days). Heck, you can't
even show your new iPhone off because it looks identical to the old one. No
crowds of people asking you "what do you thi... (more)
The build vs. buy debate for integration software (both data and application
integration) continues - it's one of those debates that's been going on for
longer than most of us have been alive. Robin Smith from Virtual Logistics
grills Hollis Tibbetts on this topic in IntegrationTV's Episode Six.
Build vs. Buy for SaaS and Cloud Integration
I had a great phone conversation with (SaaS Integration pioneer) Boomi
founder Rick Nucci about a month ago on the build vs. buy topic -
specifically why some continue to believe that building their own integration
middleware stack is a good ide... (more)