Gartner Research

Determining When a Project Is Really a Project

Published: 30 June 2010

ID: G00173325

Analyst(s): Donna Fitzgerald, Matthew Hotle


Many organizations struggle with how to categorize their work and, therefore, govern and manage it. Not everything is or should be a project. Here, we provide a framework for determining what should be managed as a project and what should be managed in a day-to-day workflow.

Table Of Contents
  • Overview
  • What Is a "Project," and Why Do We Care?
  • What Are the Minimum Number of Hours in a Project?
  • Managing the Service Request
  • Did We Give the Right Answer to the Wrong Question?
  • Blending Cost and Effort

©2021 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. and its affiliates. This publication may not be reproduced or distributed in any form without Gartner’s prior written permission. It consists of the opinions of Gartner’s research organization, which should not be construed as statements of fact. While the information contained in this publication has been obtained from sources believed to be reliable, Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such information. Although Gartner research may address legal and financial issues, Gartner does not provide legal or investment advice and its research should not be construed or used as such. Your access and use of this publication are governed by Gartner’s Usage Policy. Gartner prides itself on its reputation for independence and objectivity. Its research is produced independently by its research organization without input or influence from any third party. For further information, see Guiding Principles on Independence and Objectivity.

Already have a Gartner Account?

Purchase this Document

To purchase this document, you will need to register or sign in above

Become a client

Learn how to access this content as a Gartner client.