Public works wants to issue a project charter for weekly street sweeping that has run the same route for years. What should the associate project team recommend?
Select an answer to reveal the explanation.
Short Explanation
Weekly sweeping on the same routes is the lawn you keep mowing—operations—not a one-and-done project. Chartering BAU as a “project” just creates paperwork without a unique temporary outcome.
Full Explanation
Projects are temporary and unique; weekly street sweeping that has run the same route for years is continuous operational work and should not receive a project charter. The associate team correctly recommends treating recurring sweeping as ongoing operations. Chartering it as a project because any city work that uses a calendar needs a charter fails by concept: calendars schedule both projects and operations; a calendar alone does not create a temporary unique endeavor. Chartering it as a program so every sweep becomes a related project fails because a program coordinates related projects for combined benefits—it is not a device for converting routine maintenance cycles into projects. Moving sweeping into the capital portfolio so it competes with bridge replacements fails because portfolio capital prioritization is for strategic initiatives and investments, not for reclassifying BAU street cleaning as capital project competition. Exam caveat: CAPM fundamentals repeatedly test that charters authorize projects; issuing a charter does not change the nature of recurring operations, and forcing BAU into project or portfolio structures creates governance noise. Operational check: leave sweeping on the public-works operations plan and SLA calendar, and reserve project charters for temporary unique efforts such as route redesigns, fleet replacements, or one-time corridor rebuilds.