But, yeah, on the other hand that's just the usual business software story. 10x budget overruns are probably not called for.
- Have bloody awful UIs
- Aren't extensible
- Need a massive amount of expensive consultant days to setup
- Are very brittle
- Have an overwhelming list of features which make them very hard to use
- Have bizarre restrictions on certain data (e.g. max 100 chars for a comment)
- They're not capable of talking with common system X
- Don't expose an API
- Have atrocious db structure making reporting extremely expensive in dev time
- Use a home rolled DB (oh. god. no.)
As for the problem of timekeeping being extremely complex, it's not at all. It's difficult, but solvable with one or two decent developers/project managers in a few months. I know as I've seen it done twice now.
It's only extremely complex if you try and include every weird quirk and feature that every client has ask for. Sometimes the solution isn't extending the software, it's changing the business process or simply leaving them on the old paper system.
If you take a 37signals-esque path you've got something that'll sell to 80% of businesses, let niche software cover the rest.
It was actually my first task that I ever did "for real", though we did only the raw recording; the processing was done by older code that had all the quirks built in. It was a success, too. The problem itself is easy, but it's definitely in the class of things that can be made arbitrarily hard by added requirements with no thought given to costs/benefits. Fortunately on my project, the devs and the management were on good terms, so much thought was given to cost/benefit tradeoffs, but I can easily see cascading failure in a different environment. Even the easiest software projects can and are sunk by that.
Er, has it occurred to you that the insanely convoluted world of NYC government might constitute a niche?
The brazenness...only in NYC.
Also, if you ever get in the position of saying "X is extremely complicated and I can't explain it to you" it is because you stand to benefit by designing a system poorly, or you aren't bright enough or don't have the experience to realize that you can reframe the problem. Algebraic geometry is also complicated, but these days there are plenty of books that will explain it to you, and the tools (like sheaves) are well-established and standard.
Obfuscation is the MO of installed, configured enterprise software. If there were an incentive to create a simple, effective solution, then, lo and behold, one would be created. The incentive is almost never there.
Take Unix for example. It is simple and effective (and flimsy as all heck) but before it came along, obtuse operating systems were the norm. It is worth pointing out that A) Thompson and Ritchie are geniuses and B) there was no financial incentive.
http://www.citylimits.org/news/article_print.cfm?article_id=... (article from 2005 when it was only 6x over budget)
The City of New York employs about a quarter of a million people, which is around the same size as General Electric or GM, worldwide, performing a wide range of job functions.
Also: the particular system under development included hand scanners, so you should include developing for that.
For that reason, I just started a new startup company: TimeKeep NYC. We specialize in timekeeping software for NYC area cities. Looking for employees now, especially ones who aren't snitches. Based on past products in this market, I think we can do quite well.