A new question is Tweeted every day: Follow @PMPQuestions
Your project has just had a new sponsor appointed and she is trying to understand the purpose of the project charter, and the project scope statement. You tell her their functions can be described as:
A. The scope statement is a more detailed version of the project charter created by progressive elaboration.
B. The project charter contains high level information about the whole project, while the scope statement contains a detailed description of the scope components.
C. The scope statement and the project charter contain a lot of duplicate information, she only really needs to read one.
D. The project scope statement provides a high level overview of the project's objectives, the project charter contains the detailed work done in developing the business case.
Tip of the week: Minor scheduling mistakes to avoid
The ‘minor mistake’ of ignoring these simple factors will put your project behind schedule before you get started!
1. Load your team leaders less than 100% because they
need time to “lead” their teams.
2. Allow time in the initial tasks for ramp‐up and learning curve - no one hit the ground ‘running’ at 100%.
3. Schedule walkthroughs several days after the completion of the draft documents because reviewers need time to review before they can provide feedback.
4. Incorporate holidays, vacations and other non working days into your project calendar before you communicate the dates to your project stakeholders.
5. Schedule the sending requests for access, permission, etc. early because they often require unreasonably long lead times.
We are all familiar with these common problems, but with time pressure to get started, they’re easy to forget! For more on good scheduling practice see: http://www.mosaicprojects.com.au/PDF/Good_Scheduling_Practice.pdf