[topcoder] - New Challenge Creation and Launch Wireframe Challenge

Welcome to [topcoder] – New Challenge Creation and Launch Wireframe Challenge. Current methods for creating and launching a [topcoder] challenge can be … well.. Challenging at times. We would like to do something about that! Please help us refine the interface, and the very process, of defining a challenge. We’d like to add all kinds of helpful cues to the experience, so that anyone  — [topcoder] copilots, end-customers or Appirio employees — can quickly, easily and accurately spin up good challenges. (What is a good challenge? One that is clear, complete and succeeds in building adequate interest from the community.) This work will be vital to the ongoing growth and development of [topcoder] -- here’s your chance to make a big impact on the [topcoder] platform!

At the end of this wireframe challenge, we are looking to have a complete solution for the User Experience and flow of the application.

Round 1

For your R1 deliverables please submit the following screens:
0. Pre-flight page
1. Challenge type
2. Challenge Description
3. Requirements Description
5. Technologies Used
9. Final Review & Launch
- Notes.jpg: Any comments about your design for the Client

Round 2

Final Design plus any Checkpoint feedback
0. Pre-flight page
1. Challenge type
2. Challenge Description
3. Requirements Description
4. Challenge Guidance
5. Technologies Used
6. Submission Guidelines
7. Timeline
8. Prize Amounts
9. Final Review & Launch
- Notes.jpg: Any comments about your design for the Client

Challenge Details:
The primary goal of this challenge is to make it possible for primarily an Appirio community customer or other interested party that wants to create and launch [topcoder] challenges to be able to easily complete that process without more than minimal knowledge of the community and/or it’s process.  The challenge creation and launch process should be easy to understand (e.g. be self-service and not require training), should be possible to complete quickly without assistance (in under 15 minutes), should be flexible and allow those with greater expertise to have access to control more settings, and should generate challenges that successfully garner interest from the community including generating many valid submissions.

We are looking for the [topcoder] design Community to help us with planning our new UX "user experience".

Wireframe Expectations:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The website must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all use cases mentioned in challenge details below.
- You MUST use wireframes note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.

Supporting Documents:
- Workflow (Workflow.pdf.zip) 
- Main Features Document (Main Features.docx.zip)
- Challenge Types (challenge types.png)

Design Considerations:
- The challenge creation process should be substantially simpler than the current one.
- The challenge creation process should be more flexible and allow settings like challenge duration, prize count, and prize amounts to be set and edited by the creator.
- Challenge creation is driven from a process wizard interface:
A- The process follows a logical progression from beginning to end
B- The process is re-enterable e.g. while it follows a logical progression from beginning to end, the user can move back and forth as more information becomes available.
C - We will need a “Save Challenge for Later” or “Save as a Draft” button in all wizard pages.

Required Screen Size:
- Desktop page of size 1024px width and height as required.

Required Screens:
Notes:
- Please make sure to read Main Features Document (Main Features.docx.zip).
- A particular step might have two different "modes": 
1- A simple mode (where we, as much as possible, abstract away the complexities of things like our pricing model / timeframes, etc.
2- An advanced mode, where -- for users that need to express more control over a challenge, they may dive into this mode to give greater detail / override default settings, etc.

0) Pre-Flight page:
- We will show some information to the user to expect what’s coming and how much time needed.
- There will be a “Lets get started” button.

1) Challenge Type:
- User will be able to select the challenge type he wants, Design or Build. Note that the main features document and wireframes include a 3rd option e.g. “Fix a Bug” but that should not be included.
- User can only select one type.
- User will be able to enter advanced settings for a more detailed view; design would include all the challenge types for design, and Build would include all the challenge types for Development (refer challenge types.png)

2) Challenge Description:
- User will be able to enter challenge name in editable text field.
- User will be able to write challenge description in editable rich text field.

3) Requirements Description:
- User will be able to list one or more features that he would like to see in the winning entry and specify the review weighting for each.  Review weighting should be a numeric value and the total for all requirements must add up to 100.
- User will be able to add one or more additional requirements than appear on the page by default.

4) Challenge Guidance:
- User will provide the guidance and files needed to start from, which will help the contestants to excel at the challenge.
- The page should include a prompt indicating the types of files that would be helpful to upload and be challenge type-specific e.g. the suggestion for Design challenges might be to upload wireframe examples, and for Build challenges the suggestion might be to upload data model examples, sample JSON, source files, and so on..
- User will be able to upload files to describe his challenge

5) Technologies Used:
- If this is a development challenge the user will be able to enter the technologies used in editable tag-based list control.

6) Submission Guidelines:
- User will be able to provide submission guidelines in editable rich text field.
- User will be able to select templates from a drop down list; Templates may be guidelines for common challenge types e.g. by type of work, type of technology, and so on.  Eventually, in addition to pre-built templates, users may be able to define their own templates.

7) Timeline:
- Data gathered to this point will affect the types and recommendation for allowable timeframes.
- User will be able to select the appropriate timeline.
- User will be able to enter advanced settings to choose start, end dates and select key milestones.

8) Prize Amounts:
- User will be able to enter the amount of prize for each placement.

9) Final Review & Launch:
- All the settings that you've applied throughout the process are now shown to you, in a friendly and understandable format. 
- Users should have the ability to edit the challenge elements from the summary page and ideally not navigate away from the page.

Target Audience:
- Customer technical resource
- Customer non-technical resource
- Appirio consultant
- Appirio management
- Appirio [topcoder] expert services resource
- [topcoder] co-pilot

Judging Criteria:
- User experience
- Completeness and accuracy of the areas of functionality and content
- How well your wireframes provide a consistent user flow and clear information architecture for the application

Submission & Source Files:
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
Generated HTML files with all the requested contest requirements stated above.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.