In supervising work, which statement correctly distinguishes a task from a project?

In supervising work, which statement correctly distinguishes a task from a project?

• A. A project does not have a defined objective.
• B. A project is always smaller than a task.
• C. A task is a single unit of work; a project is a coordinated set of tasks with a defined objective and timeline.
• D. A task requires multiple objectives and a timeline.

Answer: (C)

Understanding the distinction between a task and a project helps you plan and supervise work effectively. A task is a single unit of work with a specific output, typically scoped and bounded in time. A project, in contrast, is a coordinated set of tasks that work together to achieve a defined objective within a timeline, with dependencies and resource considerations you need to manage. This is why the correct statement is that a task is a single unit of work, while a project is a coordinated collection of tasks with a defined objective and timeline. It captures how projects bring multiple tasks together to reach a bigger goal on a schedule, whereas a task stands alone with its own immediate deliverable and duration. Think of an example: a task might be “update the user FAQ page,” a single piece of work with a clear output. A project might be “launch a new product feature,” which requires several tasks—design, development, testing, documentation, and marketing—each linked and assigned a timeline to deliver the feature as a whole.

Understanding the distinction between a task and a project helps you plan and supervise work effectively. A task is a single unit of work with a specific output, typically scoped and bounded in time. A project, in contrast, is a coordinated set of tasks that work together to achieve a defined objective within a timeline, with dependencies and resource considerations you need to manage.

This is why the correct statement is that a task is a single unit of work, while a project is a coordinated collection of tasks with a defined objective and timeline. It captures how projects bring multiple tasks together to reach a bigger goal on a schedule, whereas a task stands alone with its own immediate deliverable and duration.

Think of an example: a task might be “update the user FAQ page,” a single piece of work with a clear output. A project might be “launch a new product feature,” which requires several tasks—design, development, testing, documentation, and marketing—each linked and assigned a timeline to deliver the feature as a whole.