Agile Methodology
Though Agile was first utilized in IT projects, the bottom line on Agile methodology according to a simplified method I wrote is, “using the best process through empowered teams, customer involvement, and the ability to analyze and quickly control changes to the project scope at inception and throughout the lifecycle of the project.”
Whew, what does that even mean? Basically, using Agile management in a project helps you define the project clearly with stakeholders and team input, sprints or iterations assigned to a small groups, effective project monitoring, immediate change instead of constant review, along with constant communication throughout the project. Essentially, in my article Agile for Dummies: Making Sense of It All, a process at a auto service center that took 12 steps to complete was re-evaluated using Agile, cutting the process down to only 4 steps. Simply put, Agile cuts project bottlenecks.
PRINCE2®
According to the official PRINCE2 website, this management methodology developed in the UK includes six variables, “costs, timescales, quality, scope, risk, and benefits.” The article PRINCE2 Project Management Methodology goes a step further in identifying the method; “PRINCE2 is an acronym for PRojects IN Ccontrolled Environments.” It could be argued that this method combines all practices offered through PMBOK including a consistent approach, focus on business justification, control through review, stakeholder involvement from beginning to end, and continuous improvement.
PRINCE2 roles are very specific in design including the project management, users, customers, and suppliers. With PRINCE2, however, teams report to the project manager who in turn, before risks, problems, or changes occur is required to report to a compilation of users, customers, and suppliers for effective decision-making outcomes.
Six Sigma / Lean Six Sigma Methodologies
Perhaps Agile management developed through Six Sigma and Lean Six Sigma and those who believe so adamantly in the Agile method will tell you they are never going back. In the article Key Concepts of Six Sigma, the process is defined as a “statistical concept that measures a process in terms of defects. Achieving Six Sigma means your processes are delivering only 3.4 defects per million opportunities or DMPO.” Six Sigma started with two phases, the DMAIC phase and the DMADV phase. The DMAIC phase or defining, measuring, analyzing, improving, and controlling are first used to keep projects within specification guidelines. Next comes the DMADV phase or defining, measuring, analyzing, designing, and verifying. In this phase project elements have completed the DMAIC phase and are perfected.
With Lean Six Sigma, the process is shorter by combining the two phases to realize results quicker. While quick doesn’t mean getting to the project deadline faster, it does mean by utilizing Lean Six Sigma, your processes within your phases are streamlined for quality.
Is there a "best" project management methodology? Read on to the next page for a discussion of this question.
If we look at every project management methodology is one better than another? Can you use any project management methodology on any project or must you choose the correct methodology? How to choose the right project management methodology for your project.
No comments:
Post a Comment