9 Knowledge Areas in PMBOK

Project Analysis
Floyd-Sayles, Management Consultant, United States
Mwaita, not clear on the question. Analyze what knowledge area of the project (scope, time, cost, quality, HR, communications, risk, procurement) and / or which process group or stage in the life cycle (at concept, planning, executing, monitoring & controlling, or closing)?
One could advocate project analysis occurs in every area and every stage.
Do you have further details available?

Project Analysis in PMBOK
T. Stahl, Canada
Analysis is often done by using "expert knowledge", metrics or tools.
- For example, you would perform analysis on cost estimates by getting input from experts who have done similar work before, by accessing company data on previous projects, or using estimating software tools.
- On time, you would perform "critical path" analysis or similar analysis, again using "expert knowledge" or available metrics. Hope this helps.

Analysis of Knowledge Areas: Distinguish Before and During Project Execution
Vaibhav Behere, India
As a baseline activity, we analyze everything before we proceed towards execution to enhance the chances of project success. With respect to 9 knowledge areas of PMBOK, the degree of analysis varies as per the nature of project.

Nine Knowledge Areas in PMBOK
Edie, South Africa
All the nine knowledge areas are analysed. This is done is ensure the project success and this exercise should be carried at the early stages of the project and should be reviewed throughout all the stages of the project.

Additional Knowledge Areas in PMBOK
Khalil Shahriari PMP, Management Consultant, Iran
3 knowledge area should be added to above 9 knowledge areas in the Construction Standard issued by PMI:
- Claim management
- Safety management
- Environment management.

Project Analysis and the Business Analyst
Jacqueline E. Dennis, United States
@T. Stahl: As part of managing programs and projects, I have engaged a lead business analyst (BA) who had the responsibility of:
- Ensuring the business/customer requirements were gathered. Well documented and analyzed for clarity;
- Developing Use Cases for traceability back to customer requirements;
- "Walking through" the Use Cases with the customer to solicit buy-in;
- Establishing User Acceptance Criteria, after the Use Cases were base-lined.
These responsibilities were invaluable to the success of the project.