A Guide to the Project Management Body of Knowledge (PMBOK Guide) was first published by the Project Management Institute (PMI) as a white paper in 1983 in an attempt to document and standardize generally accepted project management information and practices. The first edition was published in 1996 followed by the second edition in 2000. In 2004, the PMBOK Guide — Third Edition was published with major changes from the previous editions. The latest English-language PMBOK Guide — Fourth Edition was released on December 31, 2008.
Work on the Fifth Edition is in development.
The Project Management Body of Knowledge is the sum of knowledge within the profession of project management. As with other professions such as law, medicine, and accounting, the body of knowledge rests with the practitioners and academics who apply and advance it. The complete Project Management Body of Knowledge includes proven traditional practices that are widely applied, as well as innovative practices that are emerging in the profession, including published and unpublished material. As a result, the Project Management Body of Knowledge is constantly....
A Guide to the Project Management Body of Knowledge (PMBOK Guide) is a book which presents a set of standard terminology and guidelines for project management. The Fourth Edition (2008) was recognized by the American National Standards Institute (ANSI) as an American National Standard (ANSI/PMI 99-001-2008) and by the Institute of Electrical and Electronics Engineers — IEEE 1490-2011.[
One of the goals of project management is to meet the expectations of the stakeholders of the project. Managing the quality of the project is the function that will allow this to happen. Quality management will include all the work that is necessary to ensure that each of the objectives of the project is met. In the latest edition of the Guide to the Project Management Body of Knowledge, PMI emphasizes that the purpose of the project is to meet the requirements of the stakeholders. In the past, the project goal was to meet or exceed the customer’s...
This book has been written to help those preparing for the Project Management
Professional Examination. It is intended to cover all of the
material that the Project Management Institute (PMI) considers important
enough to be included in the exam. This book has been revised to
reflect the changes in the Project Management Professional Examination put
into effect as of March 2002 and reflects the Guide to the Project Management
Body of Knowledge, 2000 edition.
The Guide to the Project Management Body of Knowledge describes project time management as the process used to ensure the timely completion of the project. The guide goes on to say that there are ﬁve major processes that are required to do proper project time management: Activity deﬁnition. Deﬁning the speciﬁc activities that are necessary to complete the project and produce all of the project deliverables. Activity sequencing. Identifying the sequence in which the activities must be done.
This paper provides a review of the steps and stages associated with project management according to the
Project Management Institute® (PMI). It is a primer for anyone new to the Project Management Body of
Knowledge® (PMBOK®) and who is preparing to take the PMP exam.
In order to understand how the Project Management Institute (PMI) recommends that projects be run it is nec-
essary to understand the project management life cycle. The project management life cycle is the framework
around which project management activities are structured.
Project management is the application of knowledge, skills, tools and techniques to project activities to meet project requirements. Project management is accomplished through the application and integration of the project management processes of initiating, planning, executing, monitoring and controlling, and closing.
Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. Project management is accomplished through processes, using project management knowledge, skills, tools, and techniques that receive inputs and generate outputs.
Describe the software crisis and how the often dismal track record for information technology (IT) projects provides a motivation for changing how we view and manage IT projects.Explain the sociotechnical, project management and knowledge management approaches that support ITPM. Define what an IT project is and describe its attributes. Define the discipline called project management. Describe the role and impact IT projects have on an organization. Identify the different roles and interests of project stakeholders.
With sales of more than 160,000 copies, "Fundamentals of Project Management" has helped generations of project managers navigate the ins and outs of every aspect of this complex discipline. Using a simple step-by-step approach, the book is the perfect introduction to project management tools, techniques, and concepts. Readers will learn how to: develop a mission statement, vision, goals, and objectives; plan the project; create the work breakdown structure; produce a workable schedule; understand earned value analysis; manage a project team; and control and evaluate progress at every stage.
Being a project manager is similar to the decathlete and in the business of projects,
the field is very competitive. Similar to a decathlon there are events (nine
knowledge areas) in the Project Management Body of Knowledge. The decathletes
in project management are the companies that are controlling costs, schedule and
quality on a project level. The project-driven companies must find ways to learn
“best practices” in a competitive world and apply these lessons to their processes,
systems, and tools.
Fully understanding the Project Management Institute’s (PMI ) approach to project management can be diffi-
cult. This is not because of the complexity of the material. The difficulty arises from having a body of knowl-
edge that is structured for referencing, not learning.
PMI divides the tasks associated with project management into 44 processes. There are also 44 different man-
agement activities that must be completed, in a specific order .
Project Time Management includes the processes required to accomplish timely completion of the project. Figure 6-1 provides an overview of the Project Time Management processes and Figure 6-2 provides a process flow diagram of those processes and their inputs, outputs, and other related Knowledge Area processes.
Project Risk Management includes the processes concerned with conducting risk management planning, identification, analysis, responses, and monitoring and control on a project; most of these processes are updated throughout the project.
Project Quality Management processes include all the activities of the performing organization that determine quality policies, objectives, and responsibilities so that the project will satisfy the needs for which it was undertaken.
The Project Management Institute, Inc. (PMI) standards and guideline publications, of which the document
contained herein is one, are developed through a voluntary consensus standards development process. This
process brings together volunteers and/or seeks out the views of persons who have an interest in the topic
covered by this publication.
Overview of the Project Management Maturity Model.
2.1 The Software Engineering Institute Capability Maturity Model
Beginning as early as 1986 the Software Engineering Institute (SEI), which is affiliated with Carnegie Mellon University, began developing a process maturity framework for software development . With financial support from the Department of Defense this early effort resulted in the publication of the Capability Maturity Model® (CMM®)  in 1991.