PMBOK 6th, 5.5.3.2 Work performance information includes information about "project progress such as ...deliverables have not been accepted and the reasons why". Isn't the Issue log the document that records this kind of information? Saving Changes...
It could be in the issue log or other documents. The issue log rolls up all issues in one place, but you could also have separate documents focused on certain activities like a requirements verification matrix that contain information on deliverable acceptance itself.
It's very common to have various information duplicated in multiple documents due to having different views of a project.
...
1 reply by Lilian Seow
Feb 04, 2021 7:15 PM
Lilian Seow
...
Thanks Keith. I have seen duplication of information in many different documents that is not properly updated or/and referenced the source.
It could be in the issue log or other documents. The issue log rolls up all issues in one place, but you could also have separate documents focused on certain activities like a requirements verification matrix that contain information on deliverable acceptance itself.
It's very common to have various information duplicated in multiple documents due to having different views of a project.
Thanks Keith. I have seen duplication of information in many different documents that is not properly updated or/and referenced the source.
...
1 reply by Keith Novak
Feb 05, 2021 12:30 PM
Keith Novak
...
By their very nature, document based information systems include a lot of duplication and the opportunities for error that comes with it. Depending on your perspective of a project, such as procurement, design, construction, verification, support, etc. different documents contain different combinations of data to support the user needs.
One aspect of digital transformation is integrated rather than federated data. Data types are stored in a database as a single authoritative source, and the various views pull data from the source and combine them on a dashboard type view.
When there are many types of data and views required, that is a lot more complicated than it sounds, even if it sounds very difficult.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
@Lilian. If you are preparing for taking the certification exam please let me say something that I think could help. When you answer exam questions you have to write what the PMI expect as an answer in the context or framework of the PMBOK no matter that could not work in our real life working like project manager. Saving Changes...
WPI is a fairly generic term which covers a variety of content which may be found in existing artifacts or information systems.
The analogy I always use to help folks understand the difference between the three WPs is:
- WPD: Raw eggs - not too tasty, and might make you sick.
- WPI: Boiled eggs - safe to eat, filling, but not that exciting
- WPR: A Cobb salad - a complete meal with lots of variety
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Lilian,
work performance information is not one document, but rather an abstract concept. It might include the issue log.
I have seen issues as being related to the work in a project. One other definition I saw and liked was 'an issue is a gap in understanding between stakeholders'.
Deliverables are often tracked in a configuration management system and reflect the product of the project instead. Saving Changes...
Thanks Keith. I have seen duplication of information in many different documents that is not properly updated or/and referenced the source.
By their very nature, document based information systems include a lot of duplication and the opportunities for error that comes with it. Depending on your perspective of a project, such as procurement, design, construction, verification, support, etc. different documents contain different combinations of data to support the user needs.
One aspect of digital transformation is integrated rather than federated data. Data types are stored in a database as a single authoritative source, and the various views pull data from the source and combine them on a dashboard type view.
When there are many types of data and views required, that is a lot more complicated than it sounds, even if it sounds very difficult. Saving Changes...