You can create logs for any tracking. Such logs are part of Project Document updates.
Project logs, as it sounds are at higher level i.e. at project. Project logs can have issue logs, assumptions logs, resource logs, defect logs etc.
The purpose of logs is tracking, its just a table (like excel sheet) where every row represent an item to be tracked. E.g.
Project logs – rows can have list of project approval, whether baselines (cost, time, scope) have been created/reviewed/approved/rejected etc
Issue logs – rows can have issues/constraints identified during execution and M&C cycle. You can put a resource name against each issues/constraints and have a status for each like In-Progress/On-Hold/Resolved/Closed etc.
saket_pmp
Sun, 06/03/2012 - 14:29
Permalink
You can create logs for any tracking
You can create logs for any tracking. Such logs are part of Project Document updates.
Project logs, as it sounds are at higher level i.e. at project. Project logs can have issue logs, assumptions logs, resource logs, defect logs etc.
The purpose of logs is tracking, its just a table (like excel sheet) where every row represent an item to be tracked. E.g.
Project logs – rows can have list of project approval, whether baselines (cost, time, scope) have been created/reviewed/approved/rejected etc
Issue logs – rows can have issues/constraints identified during execution and M&C cycle. You can put a resource name against each issues/constraints and have a status for each like In-Progress/On-Hold/Resolved/Closed etc.
Saket, PMP