My previous post on value billing illustrated that billing software projects by the hour hurts productivity. In this post, I’ll take it one step further by arguing that hourly billing hurts the project itself.
In my previous post on value billing, I explained how I first came to realize that billing for software projects by the hour was fundamentally flawed. In this post, I reveal a paradox which I hope will help illustrate my point.
This post is the first installment in a weekly series on value based billing for software projects as previously described here.
In this post, I’m going to walk you through the real-life situation that made me realize that something was fundamentally wrong with the concept of billing software projects by the hour.
Last week, the folks at Boston-Area FileMaker Developer’s Association (BAFDA) invited me to talk about value billing for software projects. The session was basically a Q&A free-for-all, nicely moderated by organizer Kevin Cunningham. A range of business topics came up, including incorporation, liability, client red flags, etc.
The discussion eventually came round to the financial aspects [...]
It’s really hard to explain why Twitter is awesome, and frankly, I am getting sick of attempting to do so. IMHO, Lane Hartwell said it best:
It’s not the links or the deep wisdom or the celebrities or the customer service stuff supplied by the companies on Twitter that makes it amazing. It’s the connection I [...]