Most likely the answer is No except few exceptional cases. What are the factors that causes the delay? It could be a sum factor of many.
1. Scope Change/Change in the requirement
Changes are inevitable and need to be accepted and accommodated in the schedule. However not all the changes are triggered by the customer and some cases changes are triggered by Developers/Testers. That means requirements are not understood fully by development team during development or testing phase which becomes the reason for the delay in schedule. Hence understanding of the scope is so critical for the success of the delivery without any delay. All the assumptions to be clarified with allowed timeline and if any delay in the assumption, clarifications also may trigger the change in the scope thereby the schedule.
2. Productivity of the Delivery Team (Any internal resource issue/attrition etc)
Another common anomaly is the reason assumed in most cases as compared to the actual reason could be something else with the existing team. Conversely in case the project gets started with the new team this case could be possible however again that should be factored in the planning.
3. Technical Dependency (with other components/delivery)
An additional area of concern behind the reason for the delay in schedule is dependency with other dependent components. However early identification of the dependent components with right stakeholder management, we should be able to handle the situation better
4. Delay in customer Readiness for UAT/Validation (Or feedback to be received from customer)
There are times customers are not ready to do the UAT on time as planned or they become the cause for the final delay for production live. In nutshell with proper planning and project management we can overcome the issues faced in terms of schedule delay. So do we deliver the project on time? we wish to hear your comments.
Write a Comment
Your email address will not be published. Required fields are marked (*)