Discussion on:
View:
Show:
Those these may be a little more detailed than an overall general outline, I found that regardless of the project size, ya gotta know how to do critical path scheduling and creating a work breakdown structure [part of statement of work].
I'm biased since I work at SmartDraw.com but I'm curious as to what tools people are using to manage their projects. Tom, you don't mention tools at all but do you have a favorite?
Nice post - I feel obligated to mention scope management as an important part of PM. Especially in the software world, scope tends to creep out of control, if not kept in check by a good PM. Tracking actuals against estimates, using measures such as SLOC, requirements, Function Points or other "size" indicators helps a great deal.
When the project's variance wanders too far off course, question the team before flying off the handle. There may be some initial assumptions that were incorrect. Even so, the earlier a variance is detected and corrected, the more time there is to recover.
James Heires
www.ez-metrix.com
When the project's variance wanders too far off course, question the team before flying off the handle. There may be some initial assumptions that were incorrect. Even so, the earlier a variance is detected and corrected, the more time there is to recover.
James Heires
www.ez-metrix.com
PMI advocates, and PMP's will know these 10 core knowledge areas:
1.Project Integration Management
2.Project Scope Management
3.Project Time Management
4.Project Cost Management
5.Project Quality Management
6.Project Human Resource Management
7.Project Communications Management
8.Project Risk Management
9.Project Procurement Management
10.Project Stakeholder Management[5]
as specified in the PMBOK, 5th edition.
PMBOK says there are 47 processes, not 10. But all 47 fall within the above 10 knowledge areas.
1.Project Integration Management
2.Project Scope Management
3.Project Time Management
4.Project Cost Management
5.Project Quality Management
6.Project Human Resource Management
7.Project Communications Management
8.Project Risk Management
9.Project Procurement Management
10.Project Stakeholder Management[5]
as specified in the PMBOK, 5th edition.
PMBOK says there are 47 processes, not 10. But all 47 fall within the above 10 knowledge areas.
This post is a great "PM in a Nutshell" item to share with others who may be wanting to understand what you do as a PM. I noticed the article is from 2005...but these are timeless topics. As far as tools go, I believe they will vary depending on the needs of an organization and/or individual project. Some of what I use ranges from the more traditional PM tools like MS Project to the simple use of a spreadsheet. In the Agile world, we've got tools specifically designed to help facilitate that style of work (Scrum and Kanban) and can be used to manage projects; sometimes with creativity and augmentation from other tools!
Compare with PMBOK, i think this article is more praticle for us to understand. It is very useful other than theory learning
- Keyboard Shortcuts:
- Prev
- Next
- Toggle

































