Your management has decided that all orders will be treated as "projects" and that project managers will be used to update orders daily, to resolve issues, and to ensure that the customer formally…

Question

Options

• ABecause each individual order is a "temporary endeavor," each order is a project.
• BThis is program management since there are multiple projects involved.
• CThis is a recurring process.
• DOrders incurring revenue over $100,000 would be considered projects and would involve

• A
  11% (2)
• B
  6% (1)
• C
  78% (14)
• D
  6% (1)

Explanation

Option C is correct because the scenario describes recurring operations masquerading as projects - the work (processing orders, updating status, resolving issues) repeats continuously with standardized steps, which is the definition of a process, not a project. A true project is a temporary endeavor with a unique outcome; here, the orders are routine, repetitive business transactions dressed up with project management language.

Why the distractors fail:

• A is wrong because calling something "temporary" isn't sufficient - projects must also produce a unique deliverable; routine orders follow the same process each time, making them operational work.
• B is wrong because program management groups related projects to achieve strategic benefits; a stream of identical orders is not a program.
• D is wrong (and incomplete as written) because the dollar value of work does not determine whether something is a project - a $150,000 order processed the same way as a $100 order is still a recurring process.

Memory tip: Ask yourself, "Would this work repeat in essentially the same way again next week?" If yes, it's a process (operations). If it ends and won't repeat, it's a project. Management labeling something a project doesn't make it one.

No community discussion yet for this question.