project charter review

 Ed is asked to audit a relatively new project that creates a web interface for warranty claims processing at a manufacturing company. The project is already in trouble with a lot of new changes, and business partners are becoming frustrated. During interviews with the project team, Ed realizes that each individual has a different view of what the project is supposed to accomplish. After reviewing the project charter, he notices that individual assignments are listed, but no objectives or high-level deliverables. What should Ed recommend the project manager do to help save this project?

A)Have the project manager publish a description or explanation of the business need the project is going to address.

B)Change the project charter to include objectives and high-level deliverables with individuals assigned and time frames

C)Develop a scope statement with the project stakeholders.

D)Hold a kickoff meeting to get everyone on the same page

 

 

 

 

A ?

It's always good to have high level socpe in project charter but in absence of that. C is the best answer it seems

jvleminc's picture

Agree with C. Without clear scope definition anything else won't help much.