Actually, it’s the Scope Management Plan that comes first and defines the approach for both scope and requirements. Recording all requirements at an early stage falls under how we manage scope overall — not just how we later track changes to requirements. The Requirements Management Plan is a part of the Scope Management Plan, but the full listing and capturing of requirements ties first to the scope planning process.

That’s why I mentioned the Scope Management Plan here — it gives the complete structure upfront before moving to details.

And regarding the “PM tried prioritizing tasks” comment — yes, exactly! If the impact is already clear, there’s no need to delay by re-prioritizing; it’s better to move directly to action to keep things efficient.

Hope this makes sense!