You never finish a software project, you stop working on it.

In 2019, 16.2% of projects were successful by all measures, 70% were not successful,+52% were partial failures and 31% were complete failures, while project management was set to be a $6.6 trillion industry in 2020 according to teamstage.io.

I worked on solutions that served +13 millions mobile network subscribers on 2 continents, and I learnt that it'sokay to live with an unfinished when:

1. The bedrock of the project is done

The foundation is key and allows me to work on the project in the future.

Project time might be extended due to unforeseen situations or priority changes. When it happens, the project's foundation has already been laid. It's okay to live with it as-it-is. 

It's fine to keep it, and revisit it later. Don't throw it away.

2. The intended purpose can be served

When what is essential and basic for the software to be operational is ready.

There are essential elements in each project. Often these are business rules that manipulate data(create, read, update and delete). As long as they are implemented and the project can be used, you should not cast it aside. 

The minimum usable project can be deployed when software can serve the intended purpose.

3. The remaining parts are for continuous improvements

Don't cast a project aside due to open items that require continuous improvements.

Since 1985 until now, The Windows operating system has been in development. As long as a version can be used, they ship it. Microsoft understands that there is room for improvement, but they are not afraid to release it for use.

It’s OK to ship the solution as long as it can be used without causing damage.