Like all things, a project has a start and an end.
Project start
Usually, a project starts when one of its steps and all associated tasks are assigned and/or executed. This puts things in motion.
Тhe system applies - but also redefines- this concept. It allows PMs to create a project before it is even officially ready for execution. What do we mean?
Use Case
Imagine the following scenario. You’ve negotiated with a client a potential collaboration for the production of, say, a pair of pants. You must contact the client in a month to confirm whether they would like to proceed with the order. To not forget, you immediately create a project in the system (regardless that it cannot officially start), load the proper project template, and set a reminder for the first activity. In doing so, the system would remind the PM to pay attention to the activity and project at the earliest date it would make sense. Theoretically, you start/create a project, but not its execution.
This approach has proven valuable in scenarios where PMs manage many projects and tend to miss the earliest possible date they could start work.
Project end
Conversely, as project end is considered the date on which final product delivery happens (date defined internally or by the client).
Bear in mind, though, that a project may have several phases. The end of one phase marks the beginning of another and the creation of a new project. For example, delivering a certain solution can be one project, while its “service and maintenance” can be another project.