Book Image

Becoming a PMP® Certified Professional

By : J. Ashley Hunt
Book Image

Becoming a PMP® Certified Professional

By: J. Ashley Hunt

Overview of this book

One of the five most prestigious certifications in the world, the PMP® exam is said to be the most difficult non-technical certification exam. With this exam guide, you'll be able to address the challenges in learning advanced project management concepts. This PMP study guide covers all of the 10 project management knowledge areas, 5 process groups, 49 processes, and aspects of the Agile Practice Guide that you need to tailor your projects. With this book, you will understand the best practices found in the sixth edition of the PMBOK® Guide and the newly updated exam content outline. Throughout the book, you'll learn exam objectives in the form of a project for better understanding and effective implementation of real-world project management tasks, helping you to not only prepare for the exam but also implement project management best practices. Finally, you'll get to grips with the entire application and testing processes in PMP® and discover numerous tips and techniques for passing the exam on your first attempt. By the end of this PMP® exam prep book, you'll have a solid understanding of everything you need to pass the PMP® certification exam, and be able to use this handy, on-the-job desktop reference guide to overcome challenges in project management.
Table of Contents (22 chapters)
1
Section 1: Introduction to Project Management and People
8
Section 2: Project Management Processes
17
Section 3: Revision
19
Chapter 16: Final Exam

Agile project charters

You will review Agile in a bit more depth in Chapter 5, Introduction to Agile Considerations, but it's important to note that even though Agile isn't considered predictive and is instead an adaptive life cycle, a charter is still created. The chosen life cycle doesn't change the best practices.

Traditional project charters are not as flexible as Agile charters because traditional charters document a lot of set information. High-level requirements are included, but it's clear that the organization knows what it is trying to achieve. Agile projects are more open to changes and need a bit more flexibility in the chartering process.

A large part of Agile project management is transparent communication, and then determining what kind of project to charter will be determined by engaging stakeholders in the process prior to chartering. Many topics will revolve around features and functions, rather than a set deliverable. Another difference...