In this post we take a look at ‘Planning’ + Time & Budget’
Planning, part 2.
Having defined what is required from the project the next stage often rushed is planning. Software builds tend to have a number of interlinked dependencies, so a robust, sufficiently detailed plan is a necessity. As with anything in life, the more planning put in place the better the potential outcome. There is often a tendency for all parties to want to push on and progress the project as quickly as possible, however time spent at this stage will certainly be saved further down the line as the project proceeds and will benefit everyone involved.
Correct project planning will ensure that everyone involved knows their role and responsibilities and there will be a toolkit of systems, milestones and processes put in place to ensure that the project runs smoothly and that everyone has the capability to collaborate in ensuring a successful outcome.
Not Enough Time and Insufficient Budget, part 3.
Be realistic, consider what you need and its value to the business. Timescales and budget are major factors in any project and both tend to get squeezed to the point where they both impact on the successful outcome. For most customer’s projects of this nature are infrequent and therefore it is often difficult to gauge the time and cost required. However, for the company delivering the solution this is something they are doing on a daily basis and as such should be in a position to provide the requisite guidance and justification as to how long projects are likely to take to deliver and at what cost.
Quite often someone not directly involved in the project will dictate the deadline for delivery and the budget; this can put pressure on all aspects of the project and everyone involved. In this instance, effective planning becomes even more critical.
Avoid rushing a project just because you have the go-ahead and a partner who you believe can provide a solution. It is critical to make sure that time is taken to accurately assess the level of investment required both financially and in terms of the resources required from the business as this will equate to time and lost opportunity cost. Not having an accurate understanding of the internal resources required to successfully deploy a project can lead to delays and overruns which ultimately will result in additional spend.
While controlling costs is clearly very important, putting pressure on a supplier to adhere to a reduced budget will ultimately cost the company in a less satisfactorily delivered project and a supplier that will be focusing on the management of their own costs rather than the delivery of a successful project. Inevitably this will likely incur a greater cost for your internal project management team.