Project Management Professional (PMP)

Project Management Institute (PMI) is an international organization that fosters the discipline of project management across all types of industries. It keeps track of current trends and recommended methods for project management, acts as a central repository for resources, and provides networking opportunities with other project managers. It offer three types of certifications, the most common one being the PMP.

PMI has designated a specific set of requirements that you need to fulfill in order to obtain a PMP. The requirements are fairly rigorous and include having up to 7,500 hours of project management experience, 35 hours of specific project management education, and a passing grade on the PMP certification test. After obtaining a PMP, a person must maintain active status by earning at least 60 professional development units (PDUs) over a 3-year period.

PMI also maintains A Guide to the Project Management Body of Knowledge (PMBOK® Guide) 2013, which is the main reference of the PMI standards for the project management process. It also lists relevant books, journals, and conferences that are related to the discipline of project management. It is updated every 3 to 4years. The PMBOK is a general guide to the processes and methods endorsed by PMI, and it does not necessarily contain the details of all the project management knowledge that is available to PMPs.

Their website,, has information on project management best practices and provides information on how to become a certified PMP. If you want to learn more about the basics of project management, this is a good place to start.



Project Management Methods

Lots of them can be effective, but I would caution anyone against placing too much priority on a single method. Knowing Scrum, Kanban, Lean, etc. is fantastic as you can do a quick best-fit analysis and have options for discussion about what's going to be valuable. That said, I see a lot of people latch onto a method and become zealots around it. Methods are all made up; someone just like you worked out a method and wrote it down...that doesn't mean it's any more useful for your team than what you can create. Learn from what others have tried, borrow the best of them, but don't dogmatically stick to any of it. The best person to develop the method for your team is you.

In my experience, the most effective teams have methods that:

  • • Have thoughtful iteration baked in; testing and adjusting is paramount.
  • • Are developed with the team, for the team, not just by the leads or producer.
  • • Are hyper-defmed. You can have a flexible method while still defining your process fully. You should know every aspect of how your process should work, so you can understand how to change it when it breaks down.
  • • Are transparent and simple to use. Methods that reduce the reliance on custom software or rigid tools allow your process to be more flexible and less dictated by the tool.
< Prev   CONTENTS   Source   Next >