One of the biggest challenges I have is to get people to think incrementally and iteratively when developing software. When you have spent an entire career focusing on end-goal fixed product definitions, its hard to understand it’s all about a vision, the journey and the decisions you make on the way.
While assisting one of our clients in their quest to automate the construction of their environments both locally and in the cloud I came across a tricky problem that requires a little bit of background description.
Before you start reading please be forewarned that this is not as exciting as some of the previous blogs on this site (in particular the piece about submariners and torpedoes), nor does it offer leading edge insight into anything in particular. Therefore read on at your own risk!
Former American President Calvin Coolidge once remarked, “They criticize me for harping on the obvious; if all the folks would do the few simple things they know they ought to do, most of our problems would take care of themselves.”
Following my recent blog regarding contract negotiations and the retention or otherwise of IP, I thought I'd share some further thoughts.
Why is it so hard for people to accept that projects are subject to constant change and that they should adapt to the evolving environment rather than trying to predict everything and then fighting to defend their position despite reality?
I'm regularly involved in contract negotiations on behalf of my clients and invariably find myself facing the same issue. Why is it that suppliers who are being handsomely paid for bespoke development think it reasonable that they retain the IP?
This can range from the outrageous, "all title and IP will vest with Supplier" to the more benign, "IP will pass to the Client on payment for the full system". The latter may appear reasonable, but the word "full" is the crux. Assuming stage payments, the client will have paid a substantial amount before IP is transferred.
I must admit I'm not a prolific tweeter, or twit as a recent customer described people who tweet, and recently I've realised why.
The presentation of the MemberWise survey results at Tuesday's seminar, A Convenient Truth, provided plenty of food for thought. The report has now been sent to MemberWise members and others can download it at Survey Results. Importantly it provides a benchmark against which organisations can measure themselves, and it highlights a number of significant constraining factors that we can hopefully work together to address. More on this will follow in later blog posts.
IndigoBlue were very pleased to host another successful breakfast meeting at the Royal Automobile Club in Pall Mall. Organisations currently using a range of membership systems were represented by senior team members from IT and Finance.
It was striking to note the number of membership organisations actively reviewing the current technology deployed to support membership and CRM, with a range of different approaches including: