You are a project manager for a software development project. The team uses a cloud-based project management tool that includes features like task assignment, Gantt charts, and document storage. During a status meeting, a team member reports that they cannot find the latest version of the project schedule. Several team members have been updating the schedule file directly on the shared drive without version control. As a result, the file has multiple conflicting copies. You need to resolve this issue and prevent it from recurring. Which course of action should you take?
Check-in/check-out version control enforces a single authoritative copy, preventing concurrent edits that create conflicting schedule files. This directly addresses the stem's constraint of uncontrolled shared-drive updates, giving an auditable history and locking files during editing.
Why this answer
Implementing a version control system with check-in/check-out functionality directly addresses the root cause: multiple users editing the same file without coordination. This approach enforces exclusive locking or merge tracking, ensuring that only one person can modify the schedule at a time while preserving a complete history of changes. It aligns with the PMBOK's recommendation for configuration management and is a standard practice in cloud-based project management tools like Jira or Microsoft Project Online.
Exam trap
The trap here is that candidates may choose Option A (sole updater) because it seems like a simple control, but the exam tests the understanding that version control systems are the standard, scalable solution for collaborative document management, not restrictive assignment of editing rights.
How to eliminate wrong answers
Option A is wrong because assigning one person as the sole updater creates a single point of failure and a bottleneck, which is inefficient for a collaborative team and does not leverage the tool's multi-user capabilities. Option B is wrong because creating a baseline and only updating at milestones ignores the need for continuous updates in an agile or iterative development environment, leading to outdated schedules and missed dependencies. Option C is wrong because manually merging conflicting copies is error-prone, time-consuming, and does not prevent the same problem from recurring; it is a reactive fix, not a preventive control.