Tech Project Conflicts

My 3 Step Formula to avoid them

Akhil Mishra
June 19, 2024

Software projects ending in dispute typically have three major customer complaints:

1) The software is costing too much to implement.

2) The software is taking too long to implement.

3) The software doesn’t work as expected.

Conflicts are common in Software Projects, leading to a downward spiral of speculation and baseless finger-pointing.

Software project failures can be traced to failures of either party in understanding and adhering to their duties.

Everyone is happy to work at the beginning of the project, and they just see the positive side.

While in any business or commercial arrangement, you should always hope for the best scenario but prepare for the worst scenario.

Here are 3 points you must consider before starting your next project:

The most basic point, but still, many tend to rush this part of the project.

a) What the software should do

b) How it should look

c) What features and functionalities it should have

Everything should be detailed.

Changes in requirements are often made during development.

A change management process should, therefore, be agreed upon.

To lay down how changes are going to be handled while considering the impact on previously established schedules.

The respective parties should know how much, when, and how they will pay or get paid for the software development.

If it's a milestone-based project, outlining when the payment is due is important.

Will it be due on delivery or acceptance, and what if the client doesn’t accept after much wait?

Clarity in payment terms helps avoid cash flow issues as a business and keeps the project on track.

A standard software template would just say:

“The software would be transferred to the customer upon full payment to the vendor.”

But, what if the project is to be terminated early?

Does the customer get nothing?

And, what about the third-party components used in software?

How can the vendor transfer the complete software without the right over such components?

To avoid conflicts and lawsuits, these points should be considered while entering into a software development contract.

That's it.

Those are the 3 important points that I would always consider before drafting a Contract.

Because if other agencies are dealing with the same issues, chances are you would too.

And it's always good to be prepared for such conflicts, by staying clear from Day 1.

If you need my help to draft a Contract that's made for you. Something that protects You, Your Business, Your Time, and Your Money.

Then reach out to me on LinkedIn.

Or pick a time here.

We can talk about how we can work together.

Talk to you soon.

-- Akhil Mishra

or to participate.