article

Bespoke software? Take two tablets and call me in the morning.

by

So far this year I have been to see several clients to review their approach to information systems. Almost all have struggled with the in-house development of software – in many cases a lot of effort has been put into developing in-house software, and although it must have sounded like a good idea at the time, they have come to regret it eventually.

In my humble opinion (and I haven’t really researched this one too much yet) there are usually several factors that end up ensuring that it all turns to tears:

  • It’s far too hard for internal software development staff to say “no” to any request for assistance from other areas within the business (and IT people are usually there to help, so they don’t like disappointing people).
  • Our natural optimism operates to say that to do the development work required will be much easier than it ever actually is. Eventually, we learn.
  • Developing software is really, really interesting. Documenting it and writing down what you did isn’t so easy – and besides, there’s always a new project to get to.
  • My final factor as to why an in-house development approach ends up giving corporate heartburn is that few organisations can afford to provide the real tools that are needed, and support the large development staff necessary to allow people to bounce ideas off each other. The natural evolutionary progression of this is that few good tools are available to the development staff – ergo, staff leave to go to more prosperous waters (and since it was never documented, it’s time to cue the violin music for all that investment that sails into the sunset).

For my clients, I often say to have a Bex and a good lie down before you embark on an internal software development project. And if it still sounds like a good idea tomorrow morning, then you should see your GP (because those symptoms are still persisting).

It’s not that all in-house software development goes to hell in a handbasket, but it is awfully difficult to do internal software development well on any large scale, and to have the discipline and the methodologies available is often beyond the capacity of a lot of my clients here. If you ever do think about writing substantial amounts of bespoke software, be sure to recognise the risks that come with that approach.

I am beginning to wonder if you aren’t better off adapting sometimes an open-source solution that does 80% of what you need for a small commitment of work (and my presentation on Tuesday night, again, talked about some of the issues you might come across there).

Hmm. I suggest I’ll need to write an article on this topic one of these days. Although, maybe I just did that.

Open Source Issues in Business

by

The presentation I gave on Tuesday night (regarding commercial issues with open source) touched somewhat on the legal issues around open source licencing, although not a great deal. I did, after all, only have an hour or so, and a legal issue is not always a commercial issue – until it all ends in tears and winds up in court, that is.

Part of my research found this paper on the web entitled “Open Source Issues in Business“, which looks at the legal issues of using open source in your business. It does have a US-law approach, which anyone in Australia will tell you is “interesting and unique”, which would not be a positive thing to hear if it was a first date. However, the US legal regime tends to want to impose itself wherever it can go, and is having a darn good go at it wherever a “free trade agreement” goes.

So, there it is – “Open Source Issues in Business“. It’s instructive to quote the conclusion for your information:

“Circling back to the two hypothetical scenarios posited at the beginning of this article of a company desiring to protect is proprietary software code and hoping to make a profitable distribution, and a company that simply wants to use open source software for its internal operations: in each case, the software may be “free” but free lunches usually come at some price and so does “free” or open source software. Both companies need to learn more before consuming their free meal, and to consider that various issues that we have discussed here.”

As always, feedback is welcome.

Information Systems In The Old School Yard

by

In another life, I worked for independent schools (Anglican Church Grammar School and St Margaret’s Anglican Girls’ School), and in so doing I came to a good appreciation of what schools try to do with what they’ve got available (i.e. a lot with not much). In my post-school career, I have had occasion to visit schools and evaluate how the schools organise and run their information technology.

Each quarter my firm (BDO Kendalls) publishes a newsletter specifically to the education sector. In the autumn edition, I was asked to write an article entitled “Maximising Education Technology“, and so here it is, published in all its glory.

As always, feedback welcome.

Information Systems, Security, and Fraud

by

I note that John Halliday (a colleague at BDO Kendalls – Director IS Audit) has written an overview article on information systems security and fraud. This is a good short article raising the link between IS security, governance structures, and organisational fraud. John is promising a series of articles in this newsletter, so I am sure there is more to come here.

From what I understand, this article also dovetails nicely with a seminar that was run on 18th April 2005.

SME IT Health Checklist

by

One of the things I do in my “spare” time is chair the Information Technology & Management Centre of Excellence for CPA Australia (since 2002). This has responsibility for looking at over-the-horizon issues in information technology (as they relate to the accounting profession).

One of the interesting articles we published recently (thanks to Shauna Kelly who wrote it, I did review it before publishing although I think my most incisive comment was “I see” and “Great!”) was an IT Health Checklist for SME’s. A good starting point, at the very least – unfortunately you’ll need to be an Australian CPA or know a CPA to get the actual PDF (hey, there must be a CPA around here somewhere)…