Challenge Summary
In this Challenge, we are looking for your design concept for a client that is working in agile and as part of the Agile process, team members rate their mood on a daily basis to start the daily SCRUM meeting.
This is a exploratory challenge! Through this mobile application - we are looking for the topcoder design community to come up with innovative ways to capture the team mood and also looking for innovative ways to visualise the same as dashboard, reports, etc.
Capturing the mood of team will help understand overall mood of the team, and managers or people at the top levels of hierarchy will be able to take measures/follow up that need to be taken in-order to improve the mood of the team(s). We are looking for your ideas / thoughts on how do we take action/ show alerts or help find root cause also!
This should be a FUN challenge, take a look and lets discuss in forums on any questions you have!
We are very excited to see your designs for this challenge.
Round 1
Submit your initial design for a Checkpoint FeedbackAs 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 the comments while uploading your submission
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
Round 2
Submit your Final Design plus Checkpoint UpdatesAs 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 the comments while uploading your submission
- Make sure all pages have correct flow. Use the proper file numbers, (1, 2, 3, etc.)
What is Agile and SCRUM Process?
In a Agile is a methodology and SCRUM is a process in agile development.
For example, you have to develop an app with 100 features, so we develop in iterations...each month we do one code release, with 10 features and on the 10th month we will deliver 100 things.
Each cycle is called a Sprint. This includes a daily standup call in person mostly, this standup call is called Daily Scrum meeting/ stand up meeting which should be timeboxed to 15-20 mins max. Main essence of this meeting is to answer 3 questions from all the team members:
1. What have you worked yesterday
2. What you will work today
3. Any impediments/ blocker
Mostly we shouldn't have more than 12 people, the SCRUM meeting is attended by dev team and SCRUM Master. Scrum master is a facilitator mostly and not a manager.
Please fine more details in below links:
Standup Meeting: https://en.wikipedia.org/wiki/Stand-up_meeting
SCRUM: https://en.wikipedia.org/wiki/Scrum_(software_development)
~
User Definition and their Hierarchy:
(Please find the png here: https://drive.google.com/open?id=138W1GLyoNDP2hFnSmvwZ-LZvMdEBC6BM that shows an example hierarchy)
- There are an undefined number of teams.
- Each team is made up to 12 team members (TM).
- A team has only one Team leader (TL).
- Each team is attached to one Domain Leader (DL).
- A domain leader (DL) has one or many teams attached to him.
- An entitymanager (EM) has several domain leaders (DLs) attached to him.
Team Member (TM):
- A TM can belong to one or many teams.
- A TM must be able to vote and can see the team mood reports of the teams he belongs to.
- TM might not vote all the time because of absences.
Team Leader (TL):
- A TL must be able to vote in the Teams he belongs to and can see the team mood reports of the teams he belongs to.
- A TL can see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- TL might not vote all the time because of absences.
Domain Leader (DL):
- A DL must be able to vote in the Teams he belongs to and can see the team mood reports of the teams he belongs to.
- A DL can see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- DL might not vote all the time because of absences.
Entity Manager (EM):
- An EM must be able to vote in the Teams he belongs to and can see the team mood reports of the teams he belongs to.
- An EM can see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- EM might not vote all the time because of absences.
~
User Personas:
A) John: Entity Manager
John is a Entity Manager, had 2 domain leaders under him.
- He is able to quickly take a look at the teams he is part of
- For the teams in which he is a team member, he is able to see a screen where he can vote on a daily basis with 5 moods (very sad, sad, neutral, happy, very happy) and also sees a way to provide comments (optional) with voice recognition.
- He is also able to see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- He is able to view the consolidated reports of the teams he is part of and change the period as required (a year, with weekly and monthly consolidation)
- The comments made by the team members were anonymous.
- All votes were anonymous
B) Carl: Domain Leader
Carl is a Domain Leader, had 3 Team leaders under him
- He is able to quickly take a look at the teams he is part of
- For the teams in which he is a team member, he is able to see a screen where he can vote on a daily basis with 5 moods (very sad, sad, neutral, happy, very happy) and also sees a way to provide comments (optional) with voice recognition.
- He is also able to see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- He is able to view the consolidated reports of the teams he is part of and change the period as required (a year, with weekly and monthly consolidation)
- The comments made by the team members were anonymous.
- All votes were anonymous
C) Mark: Team Leader
Mark is a Team Leader, had 5 team members under him.
- He is able to quickly take a look at the teams he is part of
- For the teams in which he is a team member, he is able to see a screen where he can vote on a daily basis with 5 moods (very sad, sad, neutral, happy, very happy) and also sees a way to provide comments
(optional) with voice recognition.
- He is also able to see the team mood reports of the teams who report to him (he might not necessarily vote himself in those teams).
- He is able to view the consolidated reports of the teams he is part of and change the period as required (a year, with weekly and monthly consolidation)
- The comments made by the team members were anonymous.
- All votes were anonymous
D) Elizabeth: Team Member
Elizabeth is a Team Member and is part of 3 teams
- She is able to quickly take a look at the teams she is part of
- For the teams in which she is a team member, she is able to see a screen where she can vote on a daily basis with 5 moods (very sad, sad, neutral, happy, very happy) and also sees a way to provide comments (optional) with voice recognition.
- She is also able to see the team mood reports of the teams she is part of
- The comments made by the team members were anonymous.
- All votes were anonymous
~
Screen Thoughts:
We wanted to give you rough idea on the screens, feel free to add any other screens that will help you explain the flow.
- Think through the user personas mentioned above and please show flow for each of the users.
Some of the priorities features where we are looking for EXPLORATION and INNOVATION is marked in green
00 Navigation:
- How will the navigation look like
- What should be the navigation items, looking forward to your thoughts
01 Teams:
- Show list of teams the user is part of.
- How will the user view the team mood reports of the teams they are part of
- Do you think we need to show / indicate a user need to vote?
- How will the user view the team mood reports of the teams who report to him
- Do we need any filters and would a search be good for this page?
02 Vote Screen / Mood Capture:
- How should this screen be shown?
- User votes on a daily basis with 5 moods “very sad, sad, neutral, happy, very happy”
- Show us best ways to capture the mood
- We want to avoid form filling as much as possible and explore other methods of capturing (voice, anything else, etc) the mood!
- Also provide a way for the user to provide comment
- Looking forward to your thoughts on how you can come up with this page
03 Mood Reports / Visualizations:
- We are looking for Innovative ways to show the data that's captured (something that helps explain and at the same time help people at the top level identify which team is lagging (bad mood), etc)
- These visuals will need to showcase the captured mood under proper hierarchy (please make sure reports are shown for all the user personas in the hierachy as this is where we need innovative ways for finding / alerting managers, top levels in hierarchy etc about the teams that are not in a bad mood, etc - open to your thoughts) and thus reporting upto higher management
- As all of the information captured across the hierarchy is anonymous, we need your exploration here as how does the person at the top level (manager level) use this data and help for the betterment of the team (s) that are not performing well or not having a good mood?
- Team members will also see their own team reports, this basically will help them understand how their team is performing.
- We are looking for your ideas / thoughts on how do we take action/ show alerts or help find root cause, etc!
- User should be able to view consolidated reports.
- Should be able to view these reports by year, with weekly and monthly.
- Anything else do you think is necessary to be shown in this page, feel free to show them.
04 Dashboard:
- We are thinking of a dashboard with alert/notifications to top management like managers, leads, etc will be helpful.
- Any other features thats helpful!
05 Anything else?
- Please think through the concept and come up with ideas on what other pages will be required or will be useful for this application
- We are open to your thoughts, think out of box!
MarvelApp Prototype
- We need you to upload your screens to Marvel App.
- Please send your Marvel app request to csystic@gmail.com or in Challenge Forum
- You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it within your notes while you upload).
Design Considerations:
- Come up with clean and modern design
- Think about the user experience
- For this challenge we are focussing on Phone (ios and android), please have your screens of size 750 x 1334px
- We don't have any branding guidelines, open to designers.
Target Audience:
- Entity Manager (EM), Domain Leaders (DL), Team Leader (TL), Team Member (TM)
Judging Criteria
Your submission will be judged on the following criteria:
- Overall idea and execution of concepts
- How well does your design align with the objectives of the challenge
- Execution and thoughtfulness in designing this mobile application
- 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
- Submit Marvelapp as part of your submission.
Source Files:
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file or Sketch!
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.