CrowdExchange - Developer Community Wireframe Challenge 2

Welcome to "CrowdExchange - Developer Community Wireframe Challenge 2". We just completed our first wireframe challenge and are now looking to simplify, clean-up and  expand the features of the CrowdExchange developer portal. We already have an initial wireframe that should be used as the base for your solution. At the end of this challenge we are looking for clean and easy-to-understand wireframes that continue to help us plan and build CrowdExchange. 

Round 1

Checkpoint - Initial submission for client review
- Submit as much of a completed wireframe as possible
- We must see the Submission and Scoring process
 

Round 2

All requirements as stated in challenge details with any checkpoint feedback applied.

Challenge Details
We are looking for your wireframe concepts to help us plan this new community portal. The key things here are how our internal project teams can use the crowdsourcing model (access this community portal of developers) and drive project deliverables and results. This challenge focuses on integrating new features for submission and scoring mechanism along with merging several ideas from our previous wireframe challenge into one solid solution.

About CrowdExchange
CrowdExchange is an internal developer community portal. We are looking to change how we tackle development activities and create an crowdsource model that allows our employees to tackle the type of development activities they are interested in.

Wireframe Expectations
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- You must create traditional wireframe call-outs and notes (be aware of screen size)
- Provide us with your interaction and click-path thoughts and suggestions
- The application must be very easy to use and intuitive. Keep that in mind when creating your solution for the layout and flow information.
- Use the note pane in your design to explain your design
- Note: We review the submissions from the "index.html" page/view. 

Challenge Requirements
- We are looking for the following pages - feel free to adjust/modify based on your user experience planning of the application.
- As part of this challenge we would like to integrate concepts from the previous wireframe challenge.

Home
- Be aware of the page fold - show content above the page fold and content below the page fold. Important content should be above. 
- Reduce the size of the carousel
- Check spelling (make sure phrases/text make sense)

Dashboard
- Summary Data: We would like to have the dashboard mean more than just the Stories or Activities - we think the user will want to see summary data/stats and important information they can react to. The dashboard page that would show things like total members, total stories, total activities, registrations, submissions, etc. (see 02-206537)
- Layout: Stories and Activities are the major items - you can adjust the layout and navigation as Profile/Notifications tend to be at the top right. The dashboard can then use the full screen
- See 02-206537 for how they handle notifications
- The navigation is not very intuitive for new users - we had to bounce around clicking the "Activities" and "Stories" buttons and tabs to figure out where everything was. There is no sense of flow - think about and plan this
- Feature: "Developers who I have worked with/Publisher who I've been worked with" - (review 03-206490) - we like this feature for both Publisher and Developer (how do you incorporate this)

Search (with results)
- Search: Search is currently not very intuitive, we are not sure if the activity type and process type are search arguments or filter for the stories on the dashboard
- See 02-206537 for how they handle Activity and Member content results
- We prefer that search can be accessed from anywhere:
-- User can find Story and Activities
-- User can find Community Members
-- Users can find Activities or Members based on technologies/skills
- User should be able to "take action" on search results
-- Example: Publisher can email/send invitations to Members)
-- Example: Member can register for an Activity)
- Customization: The application should provide a list of qualified Members to the Publisher first and also on the Activity
- Customization: The application should provide a list of qualified Stories/Activities to a Member first

Stories/Activities
Review 02-206537 and 03-206490 for the wizard approach
- It is not clear how the publisher would assign an activity to a member - we need to complete this flow (think about it)
- Member will get a notification when the are assigned an Activity
- A Publisher can email/contact Members (think a message to everyone or only a few)
- We want to populate the wireframe with real names (different names) and realistic numbers (8 registrations should show 8 names)
- Check spelling - make sure "Registration" is correct

Create Activity
- Make sure to implement the wizard approach
- Activity Type: change this label to "Service Offering"
- Activity Requirements will need "numbers" (1.0, 1.1, 1.2) that the user can assign
- User shoudl be able to designate the importance of a Requirement: (Critical, High, Medium, Low)
- Publisher can copy an existing Activity
- Budget: Change this label to "Prize"
- Budget: Activities need to have multiple prizes/awards (and the ability to create more)
- Budget: No need to show the Budget graphic on the Activity
- Code Tags: How does a user add tags to an Activity? (interaction)

Timeline
- Publish
- Start
- Registration 
- Registration End
- Submit
- Review
- End

Activity Member View
- The member needs to be able to see the prize(s)
- Timeline: Start Date, Registration Date, Submit Date, End Date
- We want to populate the wireframe with real names (different names) and realistic numbers (8 registrations should show 8 names)
- Check spelling - make sure "Registration" is correct
- Registration: Capture this flow
- Submit: Capture this flow

Profile (Publisher and Member view)
Review 03-206490 for how they planned the Profile pages
- We need to update the profile to show more relevant data to the Publisher and Member
- Also easy to manage and Edit (think LinkedIn type of experience)
- Capture the flow for contacting Members
- Capture Edit view

New Wireframe Features: (Submission and Scoring Mechanism)
Review submission 02-206537
- This wireframe has started the initial design for the submission and scoring mechanism. You can use this as a start but we need you to improve and create a simple user experience as this is a key feature to our application. 

Member Scenario
Reference flow 01-Member-Submits-Flow.png & 02-Member-Review-Scores.png
- We need to add how a Member can submit their code for an Activity that they already registered for
- A Member can only able to submit to an Activity that they are registered for 
- A Member will needs to open the Activity details and then submit their code via the associated submission form. 
- They will need to submit before the deadline
- Note: Capture alerts on the profile and on the Activity if the deadline has passed 
- Once the code has been submitted they will be informed that the submission has successfully uploaded and will be sent for review
- Once the review is complete, Members will be able to review their score and feedback for their code submission.
- The Member can also see requirements they did not complete and provide comments when the requirement has been completed/re-upload new code (see 02-206537)
- The Activity list/layout and information needs to indicates that the review phase is complete and show list of the submissions which available for the activity from all the members that submitted.
- Members will be able to see the review scores and Publisher feedback for their code. 

Publisher Scenario
Reference flow 03-Publisher-Reviews.png
- A Publisher needs to be able to download the associated code and provide feedback on the submission
- The Publisher will find their submissions listed on the Activity and download them
- The Publisher will be able to view the submission scorecard and answer questions
- The Publisher will review each submission and provide a score for each requirement
- Focus on this being a smooth process that is easy to understand

There are several judging criteria like
** Meets Requirements
** Somewhat Meets Requirements
** Doesn't Meet Requirements

- The Scorecard should also have a comment field about each requirement so the Publisher can provide additional information about why requirements were exceeded, met or failed to meet expectation (see 02-206537)
- Publisher can designate a minimum acceptable requirements >= 70%
- If a submission is accepted then the publisher will mark the submission as an acceptable solution (Publisher can select multiple winners)
- Publisher can mark the Activity as complete
- Publsher can mark a Story as complete
- If the Publisher cannot get their Activity completed they can perform two actions:
1) Repost the Activity and the application will clone the Activity and Publisher can updates the deadline dates
2) Cancel the Activity and provide a reason

Scorecards
- A lot of this is described during the Publisher flow
- Publisher will need to be able to see and create scorecards associate with thier Activities and Requirements

The critical component for our current scoring mechanism to work is that the Publishers must set a of number requirements. They will also need to designate the importance of the requirements as well -- we think Critical, High, Medium, Low is fine

- Scorecards always total 100 points.  
- There will be a dynamic number of requirements to score against.  
- To score the submission, just add up the potential score based on the weightings of the requirements.  
- Then as the reviews are completed the Publisher can calculate the members actual score vs. the potential score that is possible for a particular submission.   
- We will use a percentage of potential score vs the possible as the primary metric for judging the members.  
- For example, if a Publisher defines 10 requirements and each is worth 3 points the number of possible points will be 30.  
- If a member receives a score of 27 in his review he will receive rating of 90 for this submission meaning that he achieved 90% of the available points.  
- Besides the scoring publisher will need a comments field (for each requirement) to describe how the submission did or didn't meet the requirement outlined.

Target Audience
- Publisher: Project Managers who need work/activity "activities" done
- Members: Developers who are tackling/doing the work offered by Publishers

Learn Axure
- New to Axure? Here are some quick tutorials to help you get started.
- http://www.axure.com/learn

Judging Criteria
- User Experience of the application/community
- Completeness and accuracy of the wireframe as defined in the attached requirements.
- How well your wireframes provide a consistent user flow

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

Submission File
Wireframes should be built in HTML or Axure. The resulting files are not critical in this Challenge. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.