I believe these practices largely apply to traditional, agile, and hybrid projects, Paul. How they are performed will vary, as you will do things in smaller increments on an agile project. But agile projects still need to record estimates and track them (e.g., for velocity assessment), identify and control risks, define success criteria, define release criteria (definition of done), negotiate commitments (for each iteration), plan for rework, perform retrospectives and improve their processes, and so on.

The assumption people often make when I write articles like this is that I'm saying "do all this stuff once at the beginning of the project." I'm not saying that at all. I'm saying, "This is stuff you ought to do, appropriately sliced and diced, on every project or development cycle."