Define the scope of the Job in a structured manner, with the Job being iteratively broken down into smaller components, also called Job Requirements.
This helps to ensure that Job clarity can be maximized, and scope- and expectation-related misunderstandings can be avoided during project execution, so that the product is developed first-time-right.
Clearly document the Acceptance criteria for each defined Job requirement.
This would help to ensure that the Customer team & Service Delivery team are on the same page vis-a-vis what is expected from the product, and under what conditions the deliverables would be accepted by the Customer team.
Customers may have different Business contexts, and may want to choose based on a variety of attributes such as Price, historical performance, schedule, etc.
Here, Customers can choose the attributes and relative importance assigned for sorting the the Job Proposals received.
With this feature, Customers can view the auto-sorted list of Job Proposals received, making the Job Award decision much faster and less effort-intensive.
Customers can either choose to publish their Job to all the users on GigsBoard, or select a specific Project Manager to submit their Job Proposal.
If the Job is published as an Open Job, then all Project Managers and Agencies on GigsBoard can submit their Job Proposals to the Customer.
If the Job is specified as an Invite-only Job, then the Customer can select a specific Project Manager or Agency to the Job, and request for a Job Proposal.
