A software testing plan provides the backbone of the entire software design, development and installation process. Carefully considering all the aspects of a testing plan will help ensure success when starting the software design process, giving a clear direction and path. The testing plan provides information as to how success is defined and how it will be achieved – these are key aspects to making sure the product designed will address the actual needs of the internal or external client.

This is the third post in a series about hidden project changes: things that affect scope but are easily overlooked. The topic for this post is ambiguous requirements.

One of the conditions for a waterfall project to succeed is comprehensive requirement specifications.

You supposedly plan the whole project in the beginning, during the planning phase. Anything that is not clearly stated, without room for interpretation, potentially leads to contract negotiations, which in turn might lead to a damaged relationship with the customer and - in the worst case - the project failing or being canceled altogether.