Traditional IT project managers have struggled to use the PMI methodology when it comes to software development for decades. Using the traditional project management methodology for software development is similar to trying to put a square peg into a round hole; you can force it, but it just does not fit as well as it should PMP certification .
Over the past several years, the Agile methodology has really started to gain momentum. This is in large part due to the popularity of Scrum, even though Agile has been around for nearly two decades. Scrum is one of several frameworks that fall under the Agile umbrella. Some of the others include Extreme Programming (XP), Rational Unified Process (RUP), and Design for Six Sigma.
There are generally two different types of control theory. The first is the defined (or theoretical) process. This is what traditional project management follows; it’s all about command and control. There are lots and lots of planning. You plan what you expect to happen, then enforce the plan; sometimes regardless of the conditions. Finally, this process makes use of change control. You will often find a change control board that oversees any change requests.
Scrum, on the other hand, employs what is known as the empirical process. In this process, you learn as you proceed. Instead of planning everything up front and planning on how to handle change, the empirical process states to “plan for change.” As a matter of fact, the empirical process embraces change through inspection and adaption; two of the three pillars that uphold every implementation of empirical process control.