Remove 2004 Remove PMI Remove Prince2 Remove Technical Review
article thumbnail

PRINCE2 and PMBOK: How They Compare

Rebel’s Guide to PM

We were talking about PRINCE2®, what it means to get qualified and how it compares to the PMBOK Guide. She first took her PRINCE2 Practitioner exam in 2004. Elizabeth, what’s the story behind the PRINCE2 methodology? PRINCE2 stands for Projects IN Controlled Environments and is a widely used project management method.

Prince2 415
article thumbnail

From Technical To Exceptional Review [Training Course]

Rebel’s Guide to PM

The move from technical expert to leader is a big jump for many people. Many people get promoted – or think they get promoted – because they’re technically very good in a role. From Technical to Exceptional is a course designed to help you safely and successfully make the transition. From Technical to Exceptional.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

What is Taylorism, and why Waterfall is just the tip of the iceberg!

Scrum.org

For many people, the traditional project management methodologies (see PMI / PRINCE2) are the root of the problems that birthed Waterfall. Reviewer(s): Russell Miller PST. However the technology of the time was unable to automate at that scale, so the only available “machines” were people. Subscribe to A Wee Dram!

2001 212
article thumbnail

Risk Management Resources

Herding Cats

Information about key project cost, (technical) performance, and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.

article thumbnail

A Compendium of Risk Management Resources

Herding Cats

Information about key project cost, (technical) performance and schedule attributes is often uncertain or unknown until late in the program. Taxonomy-Based Risk Identification,” Marvin Carr, Suresh Konda, Ira Monarch, Carlo Ulrich, and Clay Walker, Technical Report, CMU/SEI-93-TR-6, Software Engineering Institute, June 1993.