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

The Agile life cycle

This section is probably the most tested because some specific events and artifacts occur during an Agile project. The life cycle is so much more different from a predictive environment, so it should be easier to identify in the exam.

There are five main Scrum events:

  • Sprint planning
  • The Sprint
  • The Daily Scrum/stand-up
  • Sprint review
  • Sprint retrospective

When I think of the word Sprint and how it applies to the framework, I think of running very quickly but not getting very far. It's the same concept in Scrum and most Agile frameworks. The Sprint is typically 1 month or 2 weeks in duration. That allows for a consistent duration to be in place for all development efforts.

That does not mean that the project is over and done with. In fact, a new Sprint starts immediately after the previous Sprint is over until such a time when the customer or organization determines that the project is complete.

Sprint planning

Agile...