Requirements capture the need of the client,
Scope defines your understanding of the clients requirements and sets battery limits which allows scope and change management. Saving Changes...
Requirements are the expectations which the product need to fulfill (are the things your project needs built). Requirements are collected from the customer, stakeholders and Sponsor. Saving Changes...
I concur with Morne and Andre
1. Projects begin with objectives, which is the purpose/aim of the project.
2. Then follows what needs to be done to meet the objectives. This is the scope and deliverables.
3. Then follows criteria of executing the project and the criteria of the deliverables, which are basically the requirements Saving Changes...
To be more precise:
1. Requirements management plan is more about clients requirement and expectation. It is general document comparatively.
2. Project scope statement is the view from a project manager indicating what is to be achieved, what is included and what is not. It is a detailed document comparatively. Saving Changes...
The key word in both documents is management. The documents explain how you will manage the scope and how you will manage the requirements.
Given the definitions generously provided by our colleagues, you should write out how you will manage each one. Don't be surprised if there is a lot of common activities and steps. Saving Changes...
