For Finextra's free daily newsletter, breaking news and flashes and weekly job board.
I'm reminded of the old quote, "Half the money I spend on advertising is wasted, the trouble is I don't know which half". A century later, most CEOs and CFOs would still agree with this saying. Unlike advertising and marketing, software development is lot
more dependent upon internal and controllable factors. Nevertheless, it's still not so easy to predict which feature will or won't be used in advance. IMHO, a real change in status quo will only come from a different business model rather than by tweaking
SDLC methodologies. As I'd said in my personal blog post SaaS Will Change The Outcome Of The Bloatware Versus Light Apps Debate, bloatware will automatically come down with SaaS.
Good post, although I think you probably have two or three blog posts in one. Requirements are absolutely key and the Pareto rule normally applies. 80% of the value will come from 20% of the requirements. I believe that agile development is the key to making
sure that the right requirements get the limelight.
Thanks for your feedback.
Whilst I agree that Software as a Service (SaaS) is one potential way that organisations can cut down on bloatware in many ways this just moves the waste problem to a different location. The creators of the SaaS solutions will also have to control the waste.
The creation of waste is not the sole preserve of corporate developers. Software companies are as guilty as anybody.
As I mentioned in my article, "Every advance for the future state of the world requires the presence of software yet to be written", which
means that we will write more and more software a long way into the future. This also means that we will continue to create more waste whether it is done in the cloud or on-premise unless we take action.
Despite the advance of SaaS corporations will still be developing on-premise applications for quite some time. There is still a reluctance for many organisations in Financial Services to host their systems in the cloud and so they continue to develop in-house.
The bottom line for me is that waste is created anywhere that software is written whether that is on-premise, in the cloud, on a mobile device or embedded in some other device.
TY for your feedback.
By "metering" both type and quantity of usage, SaaS obviously prevents waste by consumers. Since vendors struggle with frontended costs and backended revenues under the SaaS model, they simply can't afford waste.
I partially agree with your bottomline view. In the case of onpremise software, most of wasted functionality can be treated as such only after the fact, so I'm not sure how practical it is to avoid waste upfront before development. I admit that this is true
only for custom-developed onpremise software. With product software, it could be different: Some implementors succeed in preventing wasteful functionality by urging customers to go live on the base product and take up change requests for extensions and customizations
only 60-90 days after the software has been put to use.
Kynetix Technology Group
08 Aug 2012
This post is from a series of posts in the group:
This community aims to provide links, resources, book suggestions, tips and insights to facilitate learning and development of IT professionals in financial services, and to develop a forum for IT professionals to exchange views on various related items.