Training for PM certification: The good, the bad, and the highly questionable
By Mark E. Mullaly, PMP
This article was originally published on gantthead on October 16, 2002.
Long regarded as the crucial hurdle in attaining the Project Management Professional certification, the PMP examination inspires as much fear and loathing as finals did in high school and college. It also has inspired as many strategies today as we developed then for packing study into the least amount of time possible.
Never before have so many PMP exam preparation courses, guides, tools, techniques, and tactics been available. Exam preparation has become an entire sub-genre of training, and a profitable one at that. Candidates can choose from books, sample exams, flash cards, online sites, and training courses that all bill themselves as the ideal way to prepare for the examination. Almost every project management training course suggests that it also readies participants to pass the examination. Some go so far as to guarantee examination success.
Beyond the offerings of the consultants and training companies, PMI also presents its own study guide. Many PMI chapters provide PMP preparatory courses, as well as study circles and mentoring opportunities, as a service to their members. Some community colleges and technical training courses even offer comparable programs.
The flurry of advertising clearly demonstrates that there is a demand for help in preparing for the exam, but how much of it actually works? Does the hype meet the expectations? What does it really take to pass the exam successfully? In answering this question, it is important to recognize that we all have different approaches to studying and learning, and no one way will work perfectly for everyone. Based upon my own experience, and that of the dozens of others I have discussed the process with, there are a few key conclusions that are essential.
For starters, studying for the PMP exam really is a great deal like studying for an exam in high school. The focus is on the terminology, processes, and process boundaries within the Guide to the Project Management Body of Knowledge (PMBOK Guide). How you practically refer to concepts and practices in your professional role as a project manager is entirely irrelevant here; you are being tested on the terminology as PMI defines it. This means that the process of preparation is in large part an exercise in rote learning, and we need to acknowledge it as such. Think of the study approaches that worked well for you in high school (I know it's a while ago, but work with me here) and chances are that they will serve you well again preparing for your PMP.
I recognize that at this point many will argue that the value of the PMBOK—and what the PMP principally demonstrates—is the understanding that comes of a common terminology, and it shouldn't be dismissed as being generic or rote. And they are right, to an extent. The PMBOK, however, is not a process—and to practically apply the principles, we need to give meaning to terms that go well beyond how PMI has defined them. It is also important to recognize that many companies have long since defined their standards of project management, and the terms that we practically reference on the job may not fully or even closely align with the definitions of the PMBOK. That said, the principles of the PMBOK are a sound base for building our processes, and sustained knowledge of the PMBOK will serve us well as project managers.
This brings me to my greatest criticism of many of the preparation approaches and training offerings that are being commercially promoted today. They encourage cramming, not the development of long-term knowledge and comprehension. When we were in high school, our learning choices often reflected one of two avenues: learn the fundamentals of the principles being taught and, through a relatively deep understanding, be able to apply them to different situations and problems; or cram at the last minute, relying on short-term memory and triggers to recall the essentials, never to be recollected or used again. We face the same choice preparing for our PMP, but a significant number of development offerings are predicated on the assumption that it is the short-term "binge and purge" studying habits that most of us are looking for.
The worst offenders in PMP preparatory training are the boot camps that promise an intense, focused week of cramming and guarantee success in passing the exam. This is all well and good so far as getting a passing grade goes, but how well do we hold onto this information over time? If we were to write the exam again 12 months after the boot camp—or even two months later—would we remember sufficient information to pass with a comparable mark? Will we be able to demonstrate our ongoing understanding of the PMBOK? And if we can't, just what was the point in taking the exam in the first place?
When people pursue the PMP just to have a set of initials after their names, without taking the time to truly comprehend the underlying principles, they are doing both themselves and the certification a huge disservice. If, as we discussed previously, the value of the exam is that it demonstrates a consistent understanding of terminology, then what is the point of going to the effort if we don't retain that working knowledge? While studying for the PMP is indeed a whole lot like high school, we need to move beyond just using the tricks we once employed to get by. We need to start focusing on true scholarship and being able to apply the principles and concepts. While our means of learning may well be different, it is the understanding and retention of what we are taught that is essential--not our ability to regurgitate it in a brief four-hour window in an exam.
Mark Mullaly is subject matter expert for the Project & Program Management department on gantthead.com and the author of gantthead's Project Management in Practice column.
Training for PM certification
PMP Certification - PROJECT INTEGRATION MANAGEMENT
MODULE – 4.0
PROJECT INTEGRATION MANAGEMENT
- Project Integration Management includes the process required to ensure that the various elements of the Project are properly coordinated and integrated throughout the project life cycle.
- Include the process required to identify, define, combine, unify and coordinate the process and project management activities within the project management Process groups.
- Involves in making trade off among the competing objectives and alternatives in order to meet or exceed the customer expectation.
- Integration includes the characteristics like unification , consolidation, articulation an integrative action that are important and crucial for project completion , managing the expectation and successfully meeting customer and stakeholder requirement .
- Project work and deliverables need to be integrated with the on going
operation of the delivery /performing organization or the customer organization or with the long term strategic planning that takes future problems and opportunities into consideration . - Product scope and project scope are integrated.
- Integration primarily concern with the effective integrating the process among the project management process groups that are required to accomplish the project objectives within organization’s defined procedure.
Process Includes :
- Develop project charter
- develop preliminary scope statement
- Develop project management plan.
- Direct and Manage Project execution.
- Monitor and control project work
- Integrated Change control
- Close project
Project Initiation phase:
- The purpose of this phase is to ensure that all the project requirement are identified,
communicated and negotiated. - All the preparation are completed for planning and executing the project.
- It should recognize that project should begin and committed to do so.
- Some time PM may involve in the beginning of the initiation process. A PM is identified and assigned as early in the project as feasible.
- PM should be assigned prior to the start of planning and preferable while the project chartered is being developed.
- The stakeholder has the greatest ability to influence project outcome and risk is highest during initiation.
- The project has the lowest probability of success during initiation phase.
- Project is initiated internally within the organization – generally a steering committee is responsible for project initiation who are external to the project. A steering committee is responsible group of senior managers and sometime mid level managers who represents the functional areas of organization .The steering committee is responsible for project review, selection and prioritization
.
PMP Certification - Project Management Process
MODULE – 3.0
PROJECT MANAGEMENT PROCESS
PROJECT PROCESS :
· Process : A series of interrelated actions and activities that bringing about a result/product/service.
· Project Management Process :
o Concern with describing and organizing the work of a project
o Are applicable in most of the project, most of the time
o Contain nine knowledge area and five process groups
· Product oriented process :
o Concern with specifying and creating the project product or services.
o Typically vary with project application area
o Defined by the project lifecycle.
PROJECT MANAGEMENT PROCESS GROUPS:
· Initiating process :
o The project and the project manager come into existence
o Defines the project or phases
o Authorized the project or phases
o It creates the approval to commit the organization resources to work on the project or phase.
· Planning Processes;
o Define and refine the objectives
o It involves determining the alternatives and selecting from the best of those to produce the project
goal.
o Amount of planning should commensurate with project scope and product scope
o Planning is an iterative process which progressively elaborated and detailing of project plan is called ‘ Rolling wave planning’
· Executing Processes :
o Actually performing project work to generate project results
o Putting project plan to work
o Coordinating project team members, support staff and other resources to carry out project
plan.
· Monitoring and controlling processes:
o Monitoring project progress regularly to identify variance from the plan.
o Carry out the project performance measurement .
o Take corrective actions
o Take preventive action in anticipation of possible problems
o Ensure project objectives are met.
· Closing processes :
o Bringing the project or phase to an orderly end and formalizing the acceptance.
o Contract closeout- completion and settlement of the contract including any open items.
o Administrative closeout – generating , gathering , disseminating information to formalize phase or project completion.
INTERACTION AMONG THE PROCESS GROUP
·Process groups are interactive in nature
· Actions or failure to take actions in one process group impact other process Groups
· Result or outcome of one become input to other.
· In core process, the process linkage is strongly defined and change in one will impact other.
· Process groups are integrated and iterative.
· Overlap one another and occur at varying levels of intensity throughout each phases of the project.
· Not same as project phase, process groups are normally repeated for each phase.
· Within a process group , the linkages between the components process are established by input- output relationship.
o Input – items which are to be acted upon
o Tools/techniques- mechanisms used to convert inputs to outputs.
o Outputs- Items which are produced by the process.
PMP Examination - PROJECT MANAGEMENT CONTEXT
Read First MODULE – 2.0 PROJECT MANAGEMENT CONTEXT What is project context ? PROJECT LIFECYCLE : Serves to define the beginning and end of a project via specific project phases. Project phases : · Activities grouped together to complete one or more deliverables with defined exit and entry criteria · Each phase exits is associated with · Phase exits are also called stage gates and kill points Project lifecycle : · Typical project lifecycle · Feasibility/initial/concept · Project lifecycle is the subset of product lifecycle Product lifecycle : Project lifecycle characteristics : · The ability of the stakeholder to influence the project is highest at the start of the project and become progressively lower as the project continue PROJECT STAKEHOLDERS · Individual and organizations that are actively involved in the project or whose interests may be positively or negatively affected as a result of project execution or completion. o Executive sponsor o Senior/ Functional manager o Project team ORGANIZATIONAL INFLUENCE: · Projects are influenced by the organization that set it up. · Project are also influenced by the maturity of organization Organizational cultural style: Most organization have developed unique and describable culture which are reflected in their share value, norms belief, expectation, policies and procedure, work ethics and work hours and view of authority relationship. Project organizational structure : ( See PMTI’s blue book table ) · Functional Organization · Projectized organization o Disadvantages – There is not enough work to justify the all dedicated · Matrix Organization o Functional and project organization co exists o Challenges of matrix organization : § Authority and responsibility of the PM Vs Functional manager o Some tips for matrix organization to be successful § A project charter that assigned the responsibility and authority to the PM · Composite organization – SEE PMBOK Program Management office · Program – Group of interrelated project managed in a coordinated way to obtain the benefit and control not available if managed separately. · Some time program involves aspect of ongoing operation · Program management is the centralized and coordinated management of a series of project to achieve organization objectives. · Strategic Mode: · Tactical mode: o Guidance for effective project management · Portfolio Management o Is a collection of projects or programs and other work that are grouped together to meet strategic business objectives. General management skills of PM · Leading – Physical environment Understand the local ecology and physical geography that could affect the International and political environment
1. How to get PMP Cretification
2. PMP Framework and standard
o Assessment of costs and deliverables
o Review of risks and allocation of further resources
o Go or No Go decision – review for accuracy and completeness
· Project phases may overlap – example of schedule compression called fast tracking
· Usually phases are sequential and usually involved transfer of technical information
· Phases can be further sub divided into sub-phases and may also have distinct project life cycle.
· Planning and designing /development
· Construction/Execution/implementation
· Handover/closeout /termination/final
· Varies based on the industry, organization and application area
· The project lifecycle phase usually define
o The technical work to be done in each phase
o The skill level of staff involved
o The completed deliverable that will mark the end of each phase
o How the each phase will controlled and approved
· Introduction: Launch , heavy advertisement
· Growth : Product is new, discount continue, sales increases, few competitors
· Maturity and saturation : decline in sale increase, more competition, other product
· Decline : Sales decline, product out of date or out or fashion.
· Lifecycle closure : During this phase the product is withdrawn from the market.
· Cost and staffing level are low at the start, peak during intermediate phase and drop rapidly as the project is near completion
· The probability of successful completion of project is lowest at the start of the project, hence risk and uncertainty is highest at the start of project. The probability of successful completion increases as project continue
· Cost to change is lowest at the initial stage of project and progressively higher at the end.
· Who may exert influence on the project and its results
· Have varying level of responsibilities and authorities and these may change over the course of project lifecycle.
· They could be invisible yet powerful – It is the PMs responsibility to map all the stakeholders and their relative influencing power.
· May have vested interest.- PM need to reconcile them and when in conflict, decide in the interests of the customer/sponsor.
· Different stakeholders and their responsibility( See Rita P 267 to 274 –VVI)
§ Set broad objectives
§ Fund the project
§ Set intermediate direction
§ Track progress
§ Approve deliverables and changes
§ Release resources.
§ Execute the project
§ Identify and mange risks
§ Communicate progress
o Project management system
o Cultural style
o Organizational structure
o Project management office
o Clear reporting hierarchy – each person ahs one reporting manager
o Each department is specialized in a specific function or skill set
o Project are local to the department
o People with similar skill and expertise is easier to manage
o Work assignment are easy to distribute
o Usually supervisor or manager are the functional eapert
o PM has little or no authority in the functional area
o PM required good communication, interpersonal , influencing and negotiation skill to make project success. o Team member are loyal to the functional manager
o Cross functional decision are taken by the functional manager
o All Activities including functions carried out as projects
o Department provide support to the projects
o PM ha ultimate authority to the project
o Other departments supports the project
o Resources are focused on project
o Loyality is to the project not to the functional manager
o Project team dissolve at the conclusion of the project
o PM responsible for making decision regarding the project and assigning resources.
resources except for a very large project
o Projectized organization are very expensive to operate.
o There can be week balanced and strong matrix
o In strong matrix organization there will be separate authority for project manager from top management
o Functional manager is the provide of resources and PM is the customer of resources
o Functional manager are responsible for administrative activities and assigning resources
o PM is responsible for work allocation
o PM and FM share the responsibility of performance review, assigning priority , planning and tracking.
o Team members reports to both Fm and PM
o Less anxiety exists about project completion the resources back to functional organization.
o Existence of horizontal and vertical communication chaannel
§ Communication flow within the team as well as to and from other group.
§ A good working relationship between PM and FM
§ PM’s Job is accomplished primarily thro the process of negotiation and leadership
§ Team members must overcome the confusion and split loyalty and adapt to a two boss situation
§ Negotiation , communication and leadership skills are key for PM to success.
§ Need to anticipate the channel of conflict
§ Need to promote team work
§ Document the every approval
§ Plan globally and act locally.
· When Projects managed collectively as a program , then the PM capitalized on the benefit that would not be achievable if the project were managed separately.
· PMO are vested with the responsibilities of managing the program
· PMO usually operate in strategic and tactical mode
· Centralized office for operation and management of project tools, such as enterprise wide project management software.
· Central coordination of communication management across projects
· Central monitoring of all PMO project timelines and budgets, usually at the enterprise level
· Coordination of overall project quality standards between the project and any internal and external quality personnel or standards organization.
o Project qualification – selection method/criteria
o Centralized repository and management for both shared and unique risks for all projects
o Project portfolio management
o Define Project management process
o Set reporting standards
o Train people , select use of tools and template.
o Allocate common resources and funds.
o Clearing house and management for project policies, procedures, template and other standard documentation .
o Centralized configuration management for all projects administered by PMO
o The projects or programs may or may not be related or interdependent.
o Portfolios are managed according to the organization goal
o Maximize the value of the portfolio through careful selection and examination of projects and programs for inclusion in portfolio
o Balanced the portfolio among incremental and radical investment
o Balance the portfolio for efficient use of resources.
o Portfolio management is utilized to achieve strategic objectives
o Portfolio management is generally the responsibility of senior managers.
o Establishing the direction/aligning people/motivation.
o Managing – Consistently producing key results expected by the stakeholders.
· Communicating
· Negotiating
· Problem solving- Conflict management
· Influencing the organization – required understanding of formal and informal structure of the organization
· Budgeting ,organizational and team building skills.
Socio – economic influences on project
· Understand how the project affect the people and how people affect the project
· Understand the demographic , economic, educational, ethical, ethnic, religion and other characteristic of people affected by the project or who have interest in the project.
· Standards and regulation
· Cross cultural issues.
· PM should examine the organizational culture to understand his/her recognized accountability and authority in managing the project.
project or affected by the project
· Consider the time zone difference, national and religion holidays.
· Travel requirement for physical meeting and logistics
· Be familiar with international, national, regional and local laws, customs and political climate that could affect the project.
PMP - Framework and Standard
Read First
How to get PMP Cretification
PROJECTS
What are project :
Projects bring about the new product, services or process into existence
Normally are means by which strategy is implemented in an organization.A project is a temporary endeavor undertaken to create a unique product or service.
Organization resort to project to achieve their strategic needs , which can not otherwise be attained through normal operation.
Project Characteristics:
Temporary : Project has definite beginning and definite end.
Unique : The product or service delivered is different from others.
Progressive elaboration : The project is developed by steps and continued by increments. It integrate the concepts of temporary and uniqueness.
Project Vs Operation
Project and operations have fundamentally different objectives. The purpose of the project is to attain its specific objectives and then terminate. The purpose of operation is to sustain business.
Projects :
· Temporary and unique
· Finite life cycle
· Deploy cross functional skills
· Progressively elaborated
Operations·
Ongoing and repetitive
· Produce pre- defined product or services
· Scope is well defined
· Organized by functional skills
Why project ?
Better focus, Deployment, channelization and conservation of resources and Address diverse interest of all stakeholders and manage their expectation.
What is management?:
- Is the art of getting things done through people
- Is the process of planning, leading, and controlling the efforts of organizational resources to achieve stated goals.
What is project management??
- Application of knowledge, skills, tools and technique to project activities to meet the project requirement.
- Accomplished through the use of processes such as initiating , planning, executing, controlling and closing.
Includes :
Identifying requirements
- Established clear and achievable objectives
- Balancing the competing demands for quality, scope , time and cost
- Adapting to the approach to the different concerns and expectation of the various stakeholders.
To be effective , requires that project management team understand and use the knowledge and skills of :
- PMBOK
- Application area knowledge, standards and regulation
- Project environment and project context
- General management knowledge and skills
- Interpersonal skills.
- Understand and decide which element are applicable and they are to be applied for a specific project.
When the project is deemed to be successful ?:
- Achieve the scope for which it was undertaken
- Comply with quality , cost and time parameter
- Delight the end customer
How to ensure project success ?:
- Mapping the customers expectation to well defined scope
- Deploy right resources in right time in right quantity
- Keep looking for risks
How project evolves ?
- A market demand
- · An organizational need – to improve internal process
- · A customer request
- · A technological advancement
- · A legal requirement
- · Social needs.
Managed By Projects : An approach that treats many aspect of ongoing operations as projects to apply project management techniques to the operation.
Project Objectives:
Project objectives are defined in the Preliminary project scope statement and project scope statement ( obtained from SOW and sponsor /client meeting)
- There are different objectives – Project, Product, cost, time, scope and stake holder’s objectives.
- Project is completed when objectives are met
- The reason for quality activities to make sure that project objectives are met
- Project often require trade off between project requirement and project objectives
- Project objective are determined in the initiation process group and refined in the planning process group
Further Reading
Managed by Objectives ( MBO) : Seerita mulchahi
OPM3 – PMI org maturity model for project management