<\/span><\/h2>\nThe answer, of course, depends on the project and your own internal processes. When deciding what method to use within your PMO, evaluate your projects using these guiding questions:<\/p>\n
Is the outcome defined?<\/strong><\/p>\nIt might help to think of this in terms of iteration as well. Have you done this before, and what are you expecting from this project? If you expect it to be \u201cjust like last time,\u201d then a Waterfall approach could be a fitting choice. However, if you\u2019re managing a new product development that has vague goals or is exploratory in nature, Agile could be helpful in accounting for changes, trying out new processes, discovery of technology limitations, or incorporating new ideas along the way.<\/p>\n
Is the process well defined?<\/strong><\/p>\nWhen deciding between Agile and Waterfall, it\u2019s also important to think about whether the method for executing the project is well known and well defined, or if it is relatively unknown territory. The Waterfall method is most well suited to projects with a well defined scope and sequence of events for execution. For example, in the case of an infrastructure upgrade, the process to decommission an existing server and install a new server is very well known and has been completed successfully many times. The process to accomplish this is well known and defined this way for a reason: It works!<\/p>\n
Alternatively, when the process for delivering the project is not well known, often an Agile approach is best. For example, software development projects are often difficult to scope, and several of the features that will be a part of the end product will be discovered during the iterative delivery process.<\/p>\n
How high is the cost of failure?<\/strong><\/p>\nWhen the costs of project failure are high, having a well thought out plan and a detailed scope is best. This lends itself well to a Waterfall project management method. For example, if there are very limited resources and no room for error, or the business is depending on the outcome, it is generally best to know what to expect and when to expect it up front.<\/p>\n
Agile project management and iterative development often encourage failure- \u201cIf you fail, fail fast\u201d is a mantra for some Agile teams. The thought process with Agile project management is to continue to iterate until the finished product is successful. If the cost of failure is small, failing and getting feedback about what doesn\u2019t work can be helpful to identify what works, then continue the project with that feedback in mind.<\/p>\n