This article discusses some of the earliest attempts at crowdsourced QA and extreme agile development that predate the agile manifesto and where they went wrong.
Today I was cleaning out an old filing cabinet, you know, the cabinet we all have that is full of hanging files that we have not touched in 10+ years. It had to be done. Well, I came across an archaeological find. Nothing as good as a dinosaur bone, or anything cool like doubloons. It was a "Get Online" disk from the 90's. Yeah, now we use them as coffee coasters, they used to come in the mail every day, and there is no real value to them. But there is a lesson...
In the old days, these proprietary services were the internet. Sure, there were those of us who had other dial up connections, and low numbered CompuServe accounts (big shout out to Columbus, OH), but for the masses, it was one of these dial up guys or nothing. The internet today is the legacy of proprietary internet dial up providers, you could argue for others like BBS, but the proprietary guys brought it to the masses. They also had their development teams keep floppy disk makers in Ferraris far longer than they should have been.
You see, the mindset in those days was, don't do quality assurance (QA), instead, let's croudsource it. BTW, crowdsource is a modern word, in a historical context. Back then it was a given that software was unreliable, and we all expected there to be bugs. I never worked for any of them, but I had friends that did, and the engineering teams knew that what they were releasing was not really ready for release. Each week, there was a new release to fix a few bugs, and another million disks sent to the world either on a magazine, of direct.
Guess what, it worked! For a while at least. Constant release and no/minimal QA, did eventually lead to better software, but at what cost:
So what can we learn from this. Well, they were actually on the bleeding edge of several things... Crowdsourcing, they were doing it in a massive way before anyone else had thought of it. Agile, they were doing agile and iterative improvement before those words were coined. And that perception is a key element to long term survival.
Sure, you can take advantage of your customers for a while, and rely on them to act as your testing organization, but it will fall eventually. Then you are in a hole and have to fight your way out. Had there been a structured QA program in place, we might still have seen them make a ton of money, and they might be the organization deciding how we use the Internet to this day.
Our mission to helping our customers - large corporations, small businesses, professional services firms, government agencies and individual developers – with the means to effectively and affordably manage their software development and testing lifecycles, so as to decrease the time to market and increase return on investment.
At Inflectra, we are fully committed to provide our customers with the very best products and customer service. We believe in going the extra mile to ensure that each customer is satisfied with our software products. We have the experience and the commitment to deliver the products customers need to deliver their projects and assure quality every step of the way. (Learn More)
We are so confident that you will be fully satisfied with our products that we offer a 30-day, unconditional, money back guarantee! (Learn More)