What often results in project scope creep when functional requirements are not defined as well as they could be?

What often results in project scope creep when functional requirements are not defined as well as they could be?
A . Inadequate software baselining
B . Insufficient strategic planning
C . Inaccurate resource allocation
D . Project delays

View Answer

Answer: A

Explanation:

Inadequate software baselining often results in project scope creep because functional requirements are not defined as well as they could be.