In Topcoder, a Conceptualization contest is where we start to understand the needs and ideas of the customer. Members of the TopCoder community work directly with the customer to help identify, organize and document the needs and ideas. After the contest, the high-level business requirements, overall scope, user stories and context is documented in an organized and presentable manner.
The output of the contest, the Business Requirements Document, identifies and describes the workflows that the client knows, or intends to follow, to accomplish one or more business goals.
The questionnaire will cover current process and your new application. At the same time, it will cover the sort of technical environment the new application should expect, and what features the new application should include.
The specification must cover the expected results and the inputs (the Questionnaire, existing documents, etc.) The copilot (if any), together with PM, will also ensure the inputs of the contest(s) are correctly entered into the Cockpit and the contest is activated in time.
The members who register the contest may have many questions. Good communication makes good results. Maybe there are some updates in the specification. Maybe there are requirement unclear or vague in meaning. Maybe there are members who are almost done but the timeline have to be extended to 24hr.
In this step, reviewers will review the submissions against the review scorecard specified in the contest detail page. After that the submitters who do not agree with the low score obtained will appeal. Reviewers have the right to accept or decline the appeal. During the final fix process the reviewers will list items that need to be improved. The winner will have to fix them before the submission is approved by PM.
Client can download the approved final fix in Cockpit.