I realize that sometimes requirements and scope are used interchangeably. In many discussions, the picture of the detailed requirements become the overall scope of the project that you then protect with oversight and change orders.
But there is also some work that has to happen up front to create that scope – that overall vision for the project and what will and won’t be included and what the ‘as-is’ will become. That overall scope of the project must be well-defined jointly with the customer so that everyone is working from a common vision before the first detailed requirement is written.
But there is also some work that has to happen up front to create that scope – that overall vision for the project and what will and won’t be included and what the ‘as-is’ will become. That overall scope of the project must be well-defined jointly with the customer so that everyone is working from a common vision before the first detailed requirement is written.
RSS Feed
