In the quality management approach, it has been specified that the quality register will be part of an integrated project register for risks, issues and lessons. It will be stored in an electronic spreadsheet on a shared drive so that it can be accessed by any project team member. Each team member will update the quality register with their own quality activities, when they believe that progress has been made.
Is this an appropriate application of the quality register, and why?
A quality register must be maintained as a separate entity as a minimum requirement for the 'quality' theme in project management. Integrating the quality register with other project registers for risks, issues, and lessons could compromise the specific focus needed for managing quality activities. Each type of register serves a distinct purpose and should be kept separate to ensure clarity and effectiveness in recording and monitoring quality-related progress and issues.
However, it’s important to note that while option A emphasizes the usefulness of integration, it doesn’t negate the importance of controlled access mentioned in option D. Both aspects are crucial for effective quality management. Therefore, while I understand the reasoning behind option A, I maintain that controlled access to the quality register (option D) is equally important to prevent unauthorized changes and ensure data integrity. So, D