A project team is working on a software development project and needs to track changes to requirements, design documents, and source code. They want to ensure that all team members can access the latest versions and that changes are logged with the author and timestamp. Which type of tool should the project manager implement to meet these needs?
Version control systems track changes, log author/timestamp, and enable team access to latest versions.
Why this answer
A version control system (VCS) is specifically designed to track changes to files—such as requirements, design documents, and source code—by recording every modification with the author and timestamp. It ensures all team members can access the latest versions through branching, merging, and centralized or distributed repositories (e.g., Git, SVN). This directly meets the need for change logging and access control.
Exam trap
The trap here is that candidates may confuse a collaboration platform (Option C) with version control because both allow file sharing, but only a VCS provides structured, auditable change tracking with author and timestamp metadata for every revision.
How to eliminate wrong answers
Option A is wrong because a quality management tool focuses on defect tracking, test case management, and quality metrics, not on versioning or change logging of documents and code. Option B is wrong because a project scheduling tool (e.g., Microsoft Project) manages timelines, dependencies, and resource allocation, not file version history or author tracking. Option C is wrong because a collaboration platform (e.g., Slack, Microsoft Teams) provides communication and file sharing but lacks granular version control with author and timestamp logging for individual file changes.