I have this struggle in my mind, on how to define projects, and how much can I (we) stretch the definition of a project.
A rough, simplistic definition of a project would be "an endeavor taken in order to achieve a certain goal". And this kind of definition (somehow) implies the idea that a project always has an end (date).
However, running a business is done with "the same" knowledge of management, but at another scale. And all the activities of the business can then be seen as sub-projects (especially including the activities which are projects undoubtedly).
So, the bottom line question is, is it OK to consider that some projects have no end (date)? Or, with different words (or different point of view), is it OK to consider that some special projects have a (forever) sliding end (date) intentionally?
I am especially interested the "why not" explanations. My attempt is to mentally "unify" project management and business management in a way that makes sense. They are both based on the same science of management after all.
Note: to give a sense of time-framing, the farthest milestone can be considered the "end of the project". A company without clear milestones will end quite soon, I guess, anyway - so they are out the scope of the question. As long as new milestones and targets are added, the project's end moves ahead in time.