Dec 8, 2010
Print this post
Understanding the PMBOK Guide on Time Periods
There’s an interesting phrase in the PMBOK Guide (Guide to the Project Management Body of Knowledge, 4th Edition) when it comes to the amount of time activities take to get done. It uses the term “work periods” instead of hours, days, weeks or months. This intentionally broad term is there for a reason. (Though the PMBOK Guide does seem intentionally obtuse sometime.)
The reason it’s so broad is that every project and every general type of activity has its own time period that makes sense for it. Some activities get done in hours, some in days, some in weeks.
By keeping the term broad, the PMBOK Guide gives us discretion in choosing the time period that makes the most sense for our project. It recognizes the difference between the units of effort required for different activities, and in doing so, emphasizes that no matter what type of activity, project management processes can help. That is, the body of knowledge of project management has something to say about every type of activity, regardless of the length of time it takes to do it.
This is also a heads up that picking the right unit for the time periods on our projects is an important part of the planning and scheduling process.
[...] Understanding the PMBOK Guide on Time Periods | Vertabase Blog vertabase.com/blog/understanding-the-pmbok-guide-on-time-periods/ – view page – cached There’s an interesting phrase in the PMBOK Guide (Guide to the Project Management Book of Knowledge, 4th Edition) when it comes to the amount of time Tweets about this link [...]
[...] days, weeks or months. This intentionally broad term is there for a reason. (Though the [...] Vertabase Blog You can also visit Onebudget.com for Budgeting Posted in Business | Tags: Guide, Periods, [...]