Nit's Cookbook

My post on achieving multi-tenancy to leverage economies of scale @ Linkedin  Webinar of the same was presented by me on Liferay Symposium and the slides are available @ Slideshare 

Over runs are very common in software projects. In a recent experience in executing one such project, I decided to do introspection. Not for finger pointing but for making sure we do not set ourselves for failure in another future project. A typical project lifer cycle in software industry starts with a "Statement of work" a contract binding the customer with software development company. Commonly known as "SOW", this contract has very high level goal/requirements for implementation of the system based on analysis done by a sales engineer. However the first thing that can go wrong in a project is that the statement of work though signed by both parties may not have been really reviewed by both parties and customer may have little faith in the SOW considering it implementing parties document rather than considering it a project bible! Mistake #1 SOW not really reviewed by customer. What ever relation you may have with your customer, make sure the SOW is und...