While executing a software rollout project, the team encounters unexpected server outages and a critical vendor shipment delay. The project manager needs a single document to log each problem, assign an owner, set a due date, and track resolution status throughout the lifecycle. Which project management document should the manager update?
An issue log is the correct artifact for recording problems that have already occurred on a project. It captures details such as description, owner, priority, target resolution date, and status, enabling the team to monitor each issue until closure. A risk register lists potential events that could happen in the future, not problems that already exist. A change log documents approved alterations to the project's scope, schedule, or budget. A project dashboard summarizes high-level performance metrics but is not used to track individual problems.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What specific information is included in an issue log?
Open an interactive chat with Bash
How is an issue log different from a risk register?
Open an interactive chat with Bash
Who is responsible for maintaining and updating the issue log?