Project Management Quiz

A Work Breakdown Structure (WBS) decomposes the total project scope into smaller, manageable components. By systematically breaking down all work packages, the WBS ensures no project work is overlooked or omitted. A scope statement defines boundaries but doesn't guarantee completeness of all work items.

In dependency relationships, SF means Start-to-Finish: the successor cannot finish until the predecessor starts. This is the reverse of the common FS (Finish-to-Start) relationship. The question specifically asks about successor completion depending on predecessor initiation, which matches the SF relationship.

A scope statement clearly defines what is in scope and out of scope for the project, establishing explicit boundaries for completion. Scope verification is about acceptance, while scope definition is the process. The scope statement is the documented boundary that guides all scope decisions.

Individual development is the foundation because teams are composed of individuals. When individual team members develop their skills, competencies, and capabilities, the collective team benefits. While motivation, conflict management, and organizational development are important, they build upon individual competence.

Inputs to project plan execution include the project plan, corrective action, and preventive action. The work authorization system is a tool or technique used during execution - it's the mechanism that authorizes work to begin, not an input itself. This makes A the correct answer as the item that is NOT an input.

In a Weak Matrix organization, the project manager has minimal authority and often little direct control over team members who report to functional managers. This makes team development challenging because the PM cannot fully direct, reward, or develop the team. Projectized organizations give PMs the most authority.

Project archives are the designated repository for all project records, documentation, and historical information upon completion. Archives ensure records are preserved, organized, and retrievable for future reference. A database or storage room might be used physically, but 'project archives' is the formal PMBOK term.

Bar charts (Gantt charts) are widely used for performance reporting because they clearly show progress, status, and timelines in an easily understood visual format. Pareto diagrams, control charts, and RAMs are tools for quality management or planning, not standard performance reporting formats.

To answer this question, the user needs to have an understanding of the project management process and the steps involved in project closing.

Option A: Client appreciates your product. This statement is not necessarily a step in project closing. While it is important to have client satisfaction, it is not a defined step in the project closing process.

Option B: Client has accepted the product. This statement is a possible step in project closing. When the client accepts the final product, it signals the end of the project and the satisfaction of the client.

Option C: Lessons learned are documented. This statement is a possible step in project closing. It is important to document any lessons learned during a project to improve future projects and avoid making the same mistakes.

Option D: Archives are complete. This statement is a possible step in project closing. It is important to archive all project documents and deliverables to ensure that they are available for future reference.

Therefore, the correct answer is:

The Answer is: D (Archives are complete).

Lessons learned should involve all stakeholders who participated in or were affected by the project - this includes the project team, but also customers, sponsors, and other key stakeholders. The project office and performing organization management may have oversight roles, but stakeholders (including the team) are the proper participants.