Hi @tim jerome, In my projects, we have always defined scope, before we start collecting requirements. When I was reading through the 'Scope Management' KA, I saw that the Collect requirements precedes Define Scope. I was surprised initially.. but then I read this... "Since all requirements identified in Collect Requirements may not be included in the project, The Define Scope selects the final requirements" (PMBOK ed 6 - Pg 151) Which makes my point even more stronger! Why collect requirements for something that not be included in my final scope??