Dev / Stage environment, db: Server=VMFF77140;Database=penningtonsLawStage;User Id=penningtonsLawStaging;Password=Thb66$rfmp5$$rf!h;encrypt=false;TrustServerCertificate=true;
Posted: 20/03/2012
An IT dispute can be disastrous for businesses. The disruption caused when systems are down can be immense and costs can spiral quickly as resources are diverted to handling the issue. In this article, which is also published in the latest issue of The Business Magazine, Nicole da Silva looks at areas where problems commonly arise:
Urgency - for good business reasons, the client needs to launch a new system as quickly as possible. This can result in the parties implementing the project without fully agreeing its scope, timetable or price.
Scope - although the scope of the project is generally defined in the contract, often it evolves as the project progresses ('scope creep'). Scope creep can be exacerbated if the client does not properly explain its requirements or fully understand the supplier's proposal.
Milestones - often IT contracts have 'milestones' which trigger payments. Disagreement over whether milestones have been reached can lead to disputes over payment.
Termination - many IT disputes arise from a party's attempt to terminate the contract. Usually, the contract will allow termination for 'material breach'. What constitutes a material breach is a frequent area of contention. Other disputes arise over obligations after termination or whether a party's actions are tantamount to a rejection of the contract.
How to avoid the most common pitfalls
The simple answer is clarity: