The project's change control approach states that PRINCE2's recommended issue and change control procedure will be used. The senior user has requested that a new set of marketing materials and marketing channels be introduced to support the launch of the training course. The senior user has suggested that this should be managed informally.
Where should the project manager record the issue, and why?
The project manager should record the issue in the issue register because this request involves a change to a baseline product. PRINCE2's issue and change control procedures require that any request for change (RFC) that affects a baselined product should be managed formally and documented in the issue register. This ensures that the change is properly evaluated, authorized, and controlled, maintaining the integrity of the project's baselines.
Any change on a baselined document needs to go through change control, hence this needs to be managed formally and so this needs to be logged in the issue register.
B is correct, "Issues being managed formally should be entered in the issue register and given a unique identifier. The daily log can be used to record issues being managed informally."
Wrong : Correct Answer is C
Believe B is correct - 'The senior user has requested that a NEW set of marketing materials and marketing channels be introduced to support the launch of the training course'. This is a new request not a change to an existing baseline therefore entered and monitored in the daily log - https://prince2.wiki/management-products/issue-register/#:~:text=Informal%20issues%20are%20normally%20placed,project%20printer%20needs%20new%20ink.
Yes its a change to baselined Project product Description.
D. In PRINCE2, issues should be recorded in the issue register regardless of whether they are going to be managed formally or informally. The issue register is the central repository for capturing and tracking all project issues, which includes requests for change. It provides a systematic way to document, assess, and manage issues throughout the project.
Option B is not the best choice because the fact that the senior user suggests managing the issue informally does not determine where it should be recorded. Recording in the issue register allows for a more comprehensive and structured approach to issue management. Option C is also incorrect because the issue register is the appropriate place to record all issues, including requests for change, even if they require a change to a baseline. Recording in the issue register initiates the process of managing the issue, which may involve baseline changes or other actions.
That is not correct statement. Issues that can be managed informally can be recorded in the daily log.