BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to the “Wipro Mentorship thru Networking Responsive App Design Challenge. Wipro Learning Network is an internal employee mentorship programme managed by the company employees. In this challenge, we are looking for you to provide design concepts for an engaging and informative app that targets 2 different user roles:
1. Mentee - employee who is trained by Mentor (one of the employee)
2. Mentor - employee who trains Mentee (one of the employee)

Read the challenge specification carefully and let us know if you have any questions.

Round 1

Submit your initial design for a Checkpoint Feedback
1. Employee Mentee:
1A. Dashboard (Desktop & Mobile)
1B. Initiate Mentoring (Desktop & Mobile)

2. Employee Mentor:
2A. Volunteer connection (Desktop)
2B. Active connection (Desktop)

- As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your Final Design plus Checkpoint Updates
1. Employee Mentee:
1A. Dashboard (Desktop & Mobile)
1B. Initiate Mentoring (Desktop & Mobile)
1C.Creating Meeting Request (Desktop)
1D. View and Close Connections  (Desktop)
1E: Mentee / Mentor Profile  (Desktop)

2. Employee Mentor:
2A. Volunteer connection (Desktop)
2B. Active connection (Desktop)
2C. Setting up meeting (Desktop)
2D. Mentor Scoreboard (Desktop & Mobile)

- As part of your final submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt.
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)


Background Overview
This challenge is about conceptualizing and designing an engaging Learning Network programme. There are two category of employee roles for this programme - Mentee and Mentor. Through this interface the employees should be able to register and execute the roles assigned to them.

Challenge Goals
Design the UI/UX for requested different user roles. This site will be Responsive. We are currently focused on Desktop views with a couple of Phone views to understand how your design will breakdown/render responsively. It is important to follow the Wipro Branding Guidelines.

Design Considerations
- We want you to focus on specific user experiences, roles and interactions
- We want the Interface to be engaging and intuitive (think if you were an employee using this site)
- Clean, Intuitive and Innovative interface design

Mentee User Persona:
Nidhi Sinha is a 27 year old employee working for Wipro as a Software Engineer. She is self-motivated and is committed to her professional growth. Nidhi decides to look for a mentor who can help her in her learning and development needs. So, Nidhi logs in to Learning Networks app and registers herself as a Mentee. Once she becomes a Mentee, she can Initiate Mentoring by selecting the mentor from the list of available Learning Areas. From the available Mentor list she then sends requests to a maximum of 3 mentors at the same area. Once she selects her mentor, she sends him a meeting request. Mentor accepts the request and it becomes an active connection. In the connection, along with the learning, she can even share updates on her learning progress or challenges if any, as notes or feedback. Once the learning has finished, she provides the rating to the mentor and closes the connection. On her dashboard, along with registering as mentee, she can even update her profile, can see list of her mentors, see summary of all her connections, status of her requests, notifications etc. Once she’s an active mentee, she can also volunteer to become a mentor by sending request to admin.

Mentor User Persona:
Varun Katiyar is a General Manager working for Wipro. Varun has specific expertise and he likes to help develop the career of mentees. So Varun logs in to Learning Networks app and volunteers as mentor by updating his profile online. Once admin approves his profile, he becomes a mentor. As a mentor, Varun gets to see list of mentees and he can reject or approve their connection. If he approves a connection, he gets a meeting request from mentee. The approved meeting request then gets stored in his outlook calendar to remind him of the upcoming meetings. In every connection, he not only teaches mentee, he also has an option to take notes or share feedbacks. Once the learning finishes, he closes the connection.

Required Pages/Features
For this challenge, we are looking for below mentioned pages. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of your design.

1. Employee Mentee:
1A. Dashboard
Employee logs in the learning networks page and comes to dashboard. It needs to have following elements:

- Update Profile: Employee shall update their profile and can also link / update profiles from LinkedIn / marketspace / SAP.
- Employee should be allowed to register as Mentee successfully by selecting " Register as Mentee"
- Should be able to see: View All Connections, My Mentors, My Mentees, Awaiting Approval, View my requests
- Initiate Mentoring
- Reading list : list of articles that interests them
- Add link: Why should I become a Mentee? and Why should I become a Mentor? (link/ button - will take them to those respective pages)
- Discussion Forum: see own and other forum discussions
- Notifications: alert for notifications that will appear in case of any action with respect to request of mentor or mentee happens

1B. Initiate Mentoring
- Learning Area:
Once registered as mentee, Employee should be able to Initiate Mentoring by selecting the mentor from the list of available Learning Area. Each Learning Area will have common/individual mentors.
Learning Area form can show:
Mentoring Category , Learning Areas, Mentoring Objective, Search Mentor button.

- Search Mentor: Mentee can use Search Mentor to search for any specific mentor. And mentee can also invite mentor to join learning networks if he/she is not available in the portal
- Mentee can have one active mentor for each learning category. Can send requests to a maximum of 3 mentors at the same area. Once Mentor accepts the request it will become an active connection
Recommended Mentor Matches:
Should be able to choose from displayed list of mentor profiles (with photo, name and designation). Can choose only 3 mentors.

1C. Creating Meeting Request
- Mentee shall send meeting request with 3 different time for meeting:
Select preferred Date & Time, Mentor Comments, Display photo, Submit and Cancel button.

- Mentor can approve/reject request in UWL. Approved/rejected meeting request should trigger a Auto-mailer to mentee and mentor. Approved meeting request should be stored in outlook calendar to remind upcoming meetings for user.

- Mentee should be allowed to take notes anytime in the connection. Mentee can also share notes with mentor and it can be a common note for both mentor and mentee.
Notes will contain: Mentoring Category (eg. Speed Mentoring), Learning Area ( Eg. GIS TSG Speed Mentoring), Mentoring Notes (some placeholder text), Notes (place to add notes) , Submit and Close button.

1D. View and Close Connections
Employee should be able to see summary of all connections, list of his Mentors and Mentees, connection status (active / inactive), learning area, start date, notes, feedback.
They can have upto 3 active connections.

- Once learning is completed connection can be closed by mentee/mentor. Mentee should be allowed to close the connection any time. Mentee can close a connection by giving feedback to his mentor.
- On closing the connection an auto-mail trigger will sent for both mentee & mentor.
- Separate feedback claim will be pushed through UML for mentee and mentor. Where mentor/Mentee shall provide feedback about the Connection/meeting
- Notes are provided to record discussion points. These are visible only as reference

1E: Mentee / Mentor Profile
Employee shall update their profile and can also link / update profiles from LinkedIn / marketspace / SAP.
- Design for one error case for mandatory fields. For eg. Name is mandatory in the profile creation, if the user doesn't enter name, how do you show that mandatory field has to be entered.

- Employee should be able to see following details:
His personal details - Name, Display name, Email, Phone, Stream, Domain (Business unit/service line/function), Designation, Location, Wipro Experience (years, months), Total Experience (years, months), Display photo
Work Detail - Prior roles in Wipro and other organizations, Significant Achievements
About me - Interested Areas, Strength Areas
Volunteer as a mentor - What is your objective/reason to volunteer as mentor? , What are the key strengths you possess which will make you good mentor?
Select your expertise domain -
Domain (For eg. Financial Services Domain, Communications Domain, Consumer Domain, Healthcare & Life Sciences Domain),
General (For eg. Career Development, Effective Execution, Interpersonal Skills),
GIS Catapult (For eg. WINTEL 1& 2, UNIX 1& 2, Network, Storage),
GIS Rookie Program (For eg. GIS Rookie Program)

2. Employee Mentor:
2A. Volunteer a connection

- Employee will login to learning networks page, and he/she should be a active mentee to nominate as mentor.
- Employee can volunteer as mentor, Mentor either shall update profile online or update from SAP/LinkedIn/marketspace.
- Once mentor submits the profile an auto mailer will be triggered for admin and mentor saying "profile is under scan and will be approved shortly by the admin." auto mailer is sent again once profile is approved.

2B. Active connections
- Mentor should be able to see the list of mentee on different areas.
- Mentor will get notification in UWL from mentee for connection. Mentor can approve or reject the connection. Mentors to get a reminder mail after 2nd and 4th days respectively to either accept/reject the connection request. Post that request can be auto-deleted and mentee can be informed on the same
- Once connection is created mentor will get meeting request from mentee in UWL. Mentor will select the preferred time and approve the meeting. Mentors to get a reminder mail after 2 and 4 days respectively to either accept/reject the meeting request. Post that request can be auto-deleted and mentee can be informed on the same.
- Approved timing should be sent to outlook calendar. And it should remind about the upcoming meetings
- Mentor shall have option to take notes for each connection specific, and also option to share the notes.
- Mentor can close the connection any time. Once closed Mentor/mentee should get feedback form in UML separately

2C. Setting up meeting
- Mentor shall also set up a meeting in an active connection.
- Mentor shall create Meeting request with 3 time options. Request will be sent to mentee in UML. Once request is accepted by mentee it should trigger confirmation mail and same data should be moved to outlook calendar.
- Mentors can invite multiple mentees for the same meeting as well. Once mentees approves a particular timing, it should go and sit in his/her & mentors Outlook calendar
- Mentees to get a reminder mail after 2 and 4 days respectively to either accept/reject the meeting request. Post that, request can be auto-deleted and mentee can be informed on the same.
- Monthly reminder should go to mentors and mentee asking to schedule meetings through the portal. In case they have already had meetings, they can select a link on the mail body to mention about the meeting they had. It will be stored in database.

2D. Mentor Scoreboard
- Employee should be able to get the feedbacks in UWL instead of logging in the application.
- Based on the feedback provided by mentee, mentor should able to see his score/points in  dashboard. You can create a dashboard similar to Mentee Dashboard and add these extra information
- Talent Management team / performance appraisal - application will be using this data of mentor points and stars to display in the annual appraisal of the mentor.
- Auto mailer/task should be created for both mentee and mentor on each Relationship closure, one week after meeting schedule time, and once a month.
- Based on the feedback by mentee points/score will get updated and mentor shall able to view that in his connections page

Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance

Branding Guidelines
The design should follow the attached Wipro branding guidelines
-  Wipro-Branding-guidelines.zip

Target Devices
- Desktop Standard Screen Size: 1366px(w) × 768px(h)
- Phone Retina Screen Size (iPhone): 750px(w) × 1334px(h) (@2x)

Stock Artwork (Icons, Photography)
- Stock artwork and icons are allowed for this challenge.
- Make sure to declare all your assets properly or you might fail screening.
- Check the branding guidelines!

MarvelApp Prototype
- You need to upload your screens to Marvel App.
- You can request for your Marvel App link by posting on forum or by sending a mail to Challenge Copilot
- Remember to include your Marvel app URL in your Notes or Declaration document while uploading your submission.

Target Audience
Wipro Employees

Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of your concepts
- How well you capture the features for the 2 user flows
- Overall design and user experience
- Cleanliness of screen design and 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
Submit JPG/PNG for your submission files.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop or Illustrator or Sketch. Layers should be named and well organized.

Final Fixes
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2018 Topcoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar
  • Sketch

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30062539