Lenka PincotChief of Staff to the CEO| Project Management InstituteParis, France
Regardless how much sounds this question obvious, I happened to be in situations where defined scope is considered not necessary. I'm looking for arguments why it is needed. By defined scope I mean high-level description, not WBS or anything even more detailed. Thanks! Saving Changes...
I second Glenn Chundrlek. How can a project team know what success looks like if the project is not defined clearly? It would also be incredibly challenging, if not impossible, to determine risks, stakeholders, and other critical pieces that a project needs without knowing what is in scope for the project. I don't see a successful outcome, or even a mediocre one, without knowing the scope. Best of luck to you Lenka! Saving Changes...
