Waterfall

What do Agile, Waterfall, and the former energy corporation Enron have in common? A strange shared history that may shed light on one of the most well-known conflicts in software development.

Agile project management strives for adaptability, while Waterfall strives for predictability. A hybrid approach that marries the two can be challenging to implement but beneficial for some projects.

The various documents, artifacts, and the processes that generate documentation are some of the main symbols of the Waterfall model. Borrowing from Lean, Agile considers a lot of documentation as “waste” that needs to be eradicated in order to streamline the development lifecycle.

Project management software comparison websites list about 600 different project management tools and choosing the right one can be head-spinning. We provide a list of 6 essential PM tools and insights on which types of projects they are most suited for.

Agile has become the mainstream approach to software delivery recently due to the popularity of Scrum and Kanban. However, many problems arise when project managers try to scale traditional agile frameworks to larger groups of people. A lot of companies revert to waterfall framework while others use hybrid methodologies like DAD, SAFe, LeSS, or Scrum@Scale.

As project managers, we are sometimes tasked with taking over a project in progress. In this guide, we will outline how to plan a project takeover and execute it flawlessly. Use the included project manager checklist for your upcoming projects.