When I think of hybrid PM approaches, I initially think of the popular contrast today between waterfall and agile. However, these are the two generalized approaches, and there are many nuances in between depending on the structure of the project or program you are working on.
There’s a lot of controversy—sometimes quite passionate and emotional—over which method is better, but I think that virtually every project is hybrid. You don’t need to pick a specific methodology! I’d like to show you how you can leverage the best from each—that is, use thoughtfully chosen bits and pieces from various methodologies cobbled together into a whole. It all depends on things like the experience of the stakeholders, the environment, and the knowledge of each member of the project management team in your situation.
First, a Little Background
The origins of the waterfall method date back to Winston W. Royce (and some before him) in the 1960s. Royce started working as an aerospace engineer in the early 1960s, but soon after found himself working on large and complex software systems and started developing new methodologies for improving the management of software projects. In 1970, he published his influential article “Managing the development of large software systems,” which is generally considered to be the paper that defined the “
Please log in or sign up below to read the rest of the article.