We’ve previously set old documents to have an emerging scope of building elements, because we don’t know how many documents we can find to add to the new document management system.
Let’s say PRJ01, PRJ02, PRJ03, and PRJ04 are done. Use the tracking section to update their status, or do so using the status diagram above the pages of those deliverables.
Go back to the project level and check the chart:
Did you notice the progress of old documents? It’s still 0%. Why do you think this is so?
If its building elements had a fully defined scope, like new server that we saw before, its progress could be calculated based on its building elements. However, old documents has en emerging scope, meaning that more items may be added underneath it in the future. As a result, its progress can’t be calculated based on the progress of its building elements. You can even mark all its children complete, and the progress of old documents remains 0%.
If you open old documents, you’ll see this type of heading:
This is similar to the status diagram of the low-level items, but it has squares instead of circles. The idea is that such items remain at 0% progress until we realize that everything is done, and we don’t have anything else to add underneath them. At that time, you can come to this page and click on done or approved.
The planned progress of dynamic-scope items has a pattern that matches the actual progress (otherwise, we will have an unjust deviation in the system). The planned progress of these items remains at 0% until their planned finish date, and at that time, it suddenly changes to 100%.