Requirements gathering is tough. Clients are often unskilled in technology and will be unable to articulate their problems and symptoms in technical terms. To create a sufficiently detailed list of requirements, the software engineer or systems analyst must be a skilled interviewer.

Discuss different techniques you can adopt to overcome the "scope creep" situation. Your answer should align with the IEEE 830-1998 standards.

Notes:

A phenomenon known as "scope creep" can derail a project when new features keep getting added, which eventually fall outside the scope of the original project. Give an example of how this might happen if your team was designing a payroll application.

IEEE830 defines how system requirements should be documented to ensure that all parties are on the same page regarding what the new system is expected to do or the problems it is expected to resolve. Where might some breakdowns occur?