When a project is started and Requirements are not specified in great detail, the exact project Budget can not be calculated without mistakes. Concrete numbers in this stage will lead to an ineffective situation in which the customer or developer may experience loss.

To avoid the possibility of an ineffective situation, we provide a Rough Order-of-Magnitude (ROM) Estimate of costs and time when Requirements are not specified in the early stages of the project. The ROM Estimate is based on Vision document that includes a list of Features.

The ROM Estimate includes the following project parameters which are the foundation for estimation:

Project may be completed within this range if all Requirements will be within the scope specified by Vision document.

Minimum and maximum duration of the project in weeks.

List of Features from Vision document that were used by estimators. Best Case (BC), Worst Case (WC), and Most Likely (ML) are the output numbers of three-point estimate method.

Each customer has their own understanding of task definition. Customers also use their own format for documentation. Sometimes, such documentation is properly formatted and presented, and sometimes it is not. We use a uniform and standard format for the preliminary scope definition. It is short, simple, and very clear - we call it the Vision.

The Vision document is a two page file that includes a description of the project, list of Features, key risks, assumptions, and architectural concepts. It is possible to present any work scope in this simple format, even if the project is very large.

The Vision document is not a fully-dressed Specification and cannot be used as the final Scope Of Work to be completed. The Vision is used by the Handyman, customer, and other stakeholders for the following reasons:

• To define the boundaries of the work.
• To gain an understanding of project goals.
• To identify key stakeholders and their needs.

A Handyman usually spends up to five hours developing the Vision.