The software industry has always been about invention, reinvention, revolutionary ideas(or not as the case maybe) and fads. There was a day when everyone strove to follow the waterfall SDLC model. With countless job creation functions, what wasn’t there to like? You could get paid, enjoy a relatively good standard of living, despite the fact that you never released a piece of software that came anywhere close to satisfying anyone’s expectations.
What wasn’t there to love about the Big Upfront Design Process. Questionable vision, poor foresight, non existant customer requirements sprinkled with the “latest” technology and the outcome was almost always an unmitigated disaster. You’ll hear about the London Ambulance service and their system developed on windows for workgroups in the early 90s. It serves them right for trying to build a massive software system with jesus tape and intel 486s.
Disasterdev thankfully was not involved in that particular party. Thats not to say we didn’t have our own fun with waterfall. During our se jour with Aspiretrix, we had plenty. Aspiretrix replete with zero customers and modest funds, attempted to ride out the dotcom bust. First step was to stop company lunches. This was a blessing in disguise, there are only limited options with peanut butter, cheese, ham and surinamese chili paste. In addition to expense reductions, our team was relocated to an old sausage factory near the centre of Amsterdam. At this stage P2M was in widespread adoption and two of the developers who had some social “issues” had moved on to their own “agriculture” business.
Given the market at the time, Aspiretrix had fundamental issues. They had a product, that no one wanted, could easily be reproduced by competitors and it lacked innovation. The COO was not happy. What was he paying people to do, other than drink coffee and surf the web. So Aspiretrix began to look at their methodology. This was a relatively easy process, since there was none. Waterfall was without doubt the dominant methodology of choice for all struggling companies. In fact Disasterdev suggested, adopting the Rational Unified Process, but since that had a tooling and licensing cost….due to Budgetecture reasons, we instead had to make do with pretending to use Waterfall.
Requirements where fabricated, customer interaction imagined, solutions created and the outcome of this process typically resulted in a PDF on Aspiretrix’s corporate site. In the rare case that we created a prototype solution, it was typically the case that it could currently serve up to 4 users at a time. We had a philosophy, “It scales on my machine!”, a proven process. Our motto was if nobody used our system and no one was willing to invest in validating our architecture, it probably wasn’t worth it….so it proved to be.
The downside to having an office in an old sausage factory that was scheduled for destruction, is such property is in hot demand. One weekend a small legion of squatters broke into Aspiretrix’s corporate HQ and seized control of the warehouse section of the derelict sausage factory. The following Monday, after the local authorities had reassured the company founders that the squatters might be there for some time, we where summoned to an all hands meeting. With the back drop of the squatters fortifying their new home and people sporting mohawks walking across the roof, we heard the CEO and COO speak at length that we should not be afraid and that everything was being done to ensure our new neighbours found somewhere else to leave. The companies senior architect spoke of how most likely the squatters would last longer than the company itself, obviously only to the developers, since such public statements where never appreciated, regardless of their accuracy.
4 Weeks later, Aspretrix let go 30% of their staff. 12 weeks after that, they let another 40% go. The company in the end relocated whilst the squatters remained. The moral of the story is that sometimes a person with a shaven head and a mangey dog knows more about life than you do.