There’s a major difference between old documents, as described in the previous parts, and other deliverables. Take software, for example. It’s broken down into OS, Firewall, and Backup. These three are the building elements we need for the software deliverable, and they define EVERYTHING we need to have in that deliverable.
Normally, when we break something down, we expect the underlying elements to cover 100% of the scope of the parent element, not more, and not less. However, it’s sometimes too difficult, or not even possible, such as in the case of old documents. We simply don’t know how many elements there should be. What we have underneath old documents at the moment is just what we’ve identified so far, and we may always add or remove items.
P3pper supports this type of items too. Open old documents, go to the settings
section, and change the Building elements' scope
property from its default mode, fully defined
, to emerging
.
You won’t see any impact on the schedule. The scope
property only impacts progress calculation, which we’ll get into very soon.