According to Define Scope, why Project Document Updated includes Stakeholders Register, Requirement Documentation and Requirements tractability matrix?
According to Define Scope, why Project Document Updated includes Stakeholders Register, Requirement Documentation, and Requirements traceability matrix? Saving Changes...
Because all those documents define the limits of the requeriments, the RTM define the priorities User / Acceptance Test Case, and the stakeholders are the people who is going to be involved to aprove every requeriement in the doccuments Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
While you define scope, you often will identify new stakeholders or learn more about known stakeholders. This may lead to new or refined requirements. There is no requirement without a stakeholder assigned to it, so these two are tightly linked. in Scrum this is represented by backlog grooming.
This might be true for more processes in the project, but it is key in Define Scope.
PMBoK Guide calls this progressive elaboration of project documents. Saving Changes...
you need to remember that PMBOK processes can be executed multiple times over the life of a project.
As such, an existing Stakeholder Register, Requirements Document or RTM could be updated based on a scope change or as a result of rolling wave planning/progressive elaboration.
This ensures that at any point in time, these artifacts are in sync with approved requirements and that traceability from high-level requirements down to detailed requirements can be demonstrated accurately.
