A key takeaway from this article is that "the purpose of operations is to keep the organization functioning while the purpose of a project is to meet its goals and conclude. Therefore, operations are ongoing while projects are unique and temporary". Why is this such an important distinction? Projects have a beginning and an end. Operations always hum along in the background while everyone else works on projects. Which category does BI fit into? What does the BI analyst do? List up to 10 activities. Which of these consists of persistent monitoring? Maybe there is an aspect the business decision-makers want to observe daily, weekly, or monthly. This could be production levels, hiring rates, training costs, or anything else. These would be considered operational activities. These are normally almost fully automated via dashboards with little input from the analyst once the program is set to run. There may be some analytic process you add before you submit the regular report, but you are not creating something unique and new. If this is all a firm uses its BI capacity for, it wastes a valuable resource that should be constantly put to work on long- and short-term projects to answer strategic-level questions.
Project Attributes
Definition of a Project
There are many written definitions of a project. All of them contain the key elements described above. For those looking for a formal definition of a project, the Project Management Institute (PMI) defines a project as a temporary endeavor undertaken to create a unique product, service, or result. The temporary nature of projects indicates a definite beginning and end. The end is reached when the project's objectives have been achieved or when the project is terminated because its objectives will not or cannot be met, or when the need for the project no longer exists.