Requirements Management Process
Requirements Management Process
- How can a project manager plan for effective stakeholder engagement while planning the project’s scope?
- Please outline 2 requirements elicitation tools you (as PM) would use to gather stakeholders’ requirements.
- Please describe the MoSCoW technique used for requirements/deliverables categorization in the project scope process.
- Please also give an example of a categorized requirement/deliverable
Words between 200 to 250, APA format , 2 ro 3 Citations
Answer preview
After all the stakeholder’s requirements are collected, they must be prioritized to avoid compromising the project’s scope. The MoSCoW technique is a popular model for categorizing these requirements based on priority. Mo stands for those requirements that must be completed and delivered. For example, a login page is a must-have requirement when developing a web application. S stands for the should-have requirement that should be completed though not very vital. An example of this requirement is the forgotten password button. Co stands for the project requirements that could cause no loss if not achieved, for example, the requirement that needs the user to contact admin to change the web interface. Lastly, W stands for a project requirement that is not necessary for a particular project (Ahmad, Ahmad, Tahir, & Khan, 2017). For example, there is no need to include a video on a login page.
[317 Words]