How does the Air Force distinguish between tasks and projects in a work context?

• A. A project is a single ongoing obligation.
• B. A task is a single, ongoing obligation; a project is a deliberate set of tasks with a defined end state and objective.
• C. A task is not defined.
• D. A project has no defined end.

Answer: (B)

In work contexts, the distinction centers on temporality and deliverables. A task is a single duty or activity that may be ongoing, while a project is a planned set of tasks aimed at a specific end state and objective.

This aligns with the Air Force approach: everyday duties and routine work are tasks, whereas initiatives with a scope, milestones, and a target date are projects. For example, updating a weekly readiness checklist is a task, while implementing a new maintenance scheduling system with defined milestones and a go-live date is a project.

The correct choice captures that a task is an ongoing obligation and a project is a deliberate, end-dated effort with a defined objective. The other options imply that projects never end or that tasks aren’t defined, which doesn’t fit how work is organized.