Cycle Time Optimisation
Cycle time optimisation is an operating philosophy of maximising the efficiency of the sub optimal value-added activities while reducing the non- value activities and time for the best quality, the cost and the responsiveness to the customer needs.
If after guessing the total elapsed time for the project, if it is found that the project will take much longer time than the planned completion then the project should be redefined. This can probably be done by breaking the project into phases or defining multiple projects.
There are some compelling reasons why very large systems projects shouldn't be undertaken. First, the organisation loses the attention span at some point. Also, the other priorities may intervene. The resources may tend to disappear, through attrition or through reassignment.
Second, the business conditions may change. If the project cannot be completed within the one calendar year of its commencement then the project will risk the delivery of the obsolete system from the business standpoint. The competition will be moving more rapidly all the time. The governmental regulatory climate might change which applies to the any industry. The reduced cycle time is the concept which is being preached for all the products and the services. This has always been true for the effective information systems.
Third, if the project is larger, then the risk of failure will be greater. While attempting to control the projects which are too large the best project managers and the best project management methodologies and tools will become strained. The errors in planning or estimating the degrees which may be easily correctable on the small projects could be overwhelming on the large ones. The management should have the visibility and the ability to control the overruns and also cut the losses. This is much more likely on the smaller projects.
Many organisations would have undertaken very big projects. Chances of the success are importantly enhanced when the project is carved up so that the major implementation occurs at least once in a year. This will give the ongoing visibility and the organisational commitment to the project.