Agile can be effective in a business as usual environment similar to what the article is concerned with. It may not meet the technical definition of a Project

Agile can be effective in a business as usual environment similar to what the article is concerned with. It may not meet the technical definition of a Project but it uses and benefits from many of the same processes. Is that mission creep for PMI ? Cooking dinner can be managed as a project. If PMBOK starts to get merged with ITIL then we have a problem but sharing best practice is healthy everywhere. As for the Iron Triangle, there is a reason it consistently results in cost overruns and blown schedules -- the plan stage suffers from low visibility of future conditions and the polotics of getting funded. At the other end of the spectrum is this Agile like approach of the article where your plan floats in a two week scheduling window without a baseline and you draw targets around wherever you land. There needs to be room in the middle.