FIT App: Supply Collector Tool Design Challenge

Front-End Design

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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to "FIT App: Supply Collector Tool Design Challenge". In this challenge, we need your help to move and merge all functionality from our existing Supply Collector tool to our FIT application.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit your initial designs for checkpoint feedback
01) Supply Collector Features
  • 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 the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your final designs with all checkpoint feedback implemented
01) Supply Collector Features
  • As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
  • Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
  • If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2

CHALLENGE OBJECTIVE

  • Create UI screens in our FIT application to accommodate all Supply Collector Tool features
  • Need to STRICTLY follow the FIT application design style elements


BACKGROUND OVERVIEW

  • We are looking to migrate all functionality from our Supply Collector Tool which was created using "PowerApps" to our FIT application natively and enhance that functionality based on the amazing capabilities inherent in the FIT!
  • The existing Supply Collector Tool created using "Power Apps" software and the UI was designed using the best practice of Power Apps
  • All the supply collector tool functionality mentioned in the "Supply Features-gtap v2" needs to be merged into the FIT application. Use Delivery Group screens as the entry point/jumping off point for editing Supply/Capacity from each Delivery Group
  • Moving forward we want to shut down/move away from the Power Apps and build the Supply Collector functionality/features into our FIT application 
  • That means all features from Supply Collector Tool need to be added into our FIT application and needs to follow FIT design branding


FIT APPLICATION

The FIT application is a tool that is used by our business and IT users to identify and assess high-level project scope - starting with customer experience, defining capabilities for delivery, and estimating the size of the impacts and determining the teams ("Delivery Groups") that will do the work.
  • Part of the metadata used to drive the estimation process is Delivery Org data tied to a tiered set of entities: Solutions and Delivery Groups. (There is also an alternate Delivery Group parent, Functional Domains.)
  • Solutions roughly correspond to VP-level orgs and Delivery Groups roughly correspond to Director-level orgs. Functional Domains tend to be higher than DGs, but lower than Solutions.
  • Solutions and Delivery Groups are acquired from Jira Align via integration, but Functional Domains are mastered in the FIT
  • The FIT has a "Delivery Group Admin" function where several people from the VP-level org intake team can update certain metadata associated with the Delivery Groups for which they have configured access. Currently, this includes information like associated Applications, associated LOE providers, and will be expanded to include some additional attributes as well.
  • The current screen used for Model Management by the FIT Admins and the screen used by DG Admins are being consolidated into a single experience with user-targeted filtering. This will provide a single, three-tab screen that presents Solutions, Functional Domains, and Delivery Groups and their configured metadata in one place.


SUPPLY COLLECTOR TOOL APP

The existing Supply Collector tool is designed to collect resource and capacity information associated with the exact same Delivery Org structure described above. Capacity data is associated with each Delivery Group, and then can be rolled up to be viewed at the Functional Domain level, as well.
  • In downstream portfolio planning activity, this resource and capacity information gathered at the Delivery Group and Functional domain level is interpreted as "supply", and FIT estimates (cited above) are interpreted as prospective "demand" against our IT staffing resources. Comparison and roadmapping of these two sets of data is done outside of the FIT, via other tools and reporting mechanisms.
  • Since many of the users serving as DG Admins and providing Capacity information are the same set of users, and both sets of data represent data associated with Functional Domains and Delivery Groups, the desired outcome is to integrate the Supply Collector data gathering into the FIT Delivery Org screens.
  • This will allow associated DG Admins to both manage Delivery Group metadata and Delivery Group Capacity data in one place
  • The existing Supply Collector Power App pulls the Delivery Group data from FIT data that flows into our data lake. So moving this data collection point to the FIT will allow the data to be directly associated to the FIT Delivery Groups, rather than doing it in another tool with a dependency on batch jobs to keep the DG data synced
  • Additional metadata/configuration data needed to support the Supply Collector in the FIT should leverage the current UI pattern for Model Management data where applicable, unless a simpler design is more appropriate.


PROJECT GOALS

  • The goal of this challenge is to merge all functionality from our existing Supply Collector tool to our FIT application


TARGET AUDIENCE

  • FIT Admin - A Business Architecture or JSP FIT Administrator who has full access/editability to all data in the tool
  • DG Admin - Typically a person from a VP-level org intake team who has access to manage metadata associated with the Delivery Group in the FIT
  • Portfolio Admin - Typically a person from the Portfolio team who will be able to review supply entries provided by DG Admins and approve/accept those submissions for use in the next "capacity roadmap". Part of their role is to consider the net effects of those DG Admin-sourced entries to make sure there isn't a significant change month-over-month that will disrupt the IT roadmap


SCREEN REQUIREMENTS

  • Please open our branding folder and use “Delivery_Org_Update.xd” as your design base in this challenge, you also can see the design from this XD Handoff Link
  • IMPORTANT: Delivery org screens should be used as the entry point for users to be able use supply collector tool features in the FIT application.
  • In the "Supply Collection Deck.pptx", you can see several screenshots of the existing power supply tools that are being created in "PowerApps", it should be used as references and to show examples of the type of data that are being collected. 
  • Now, please open and check "Supply Features-gtap v2" google sheet, use this as references for  the requirements to understand the data that needs to be collected for each DG, as well as the underlying configurable data that will drive that data collection
  • Under "Supply Features-gtap v2 -> Supply Features" sheet, please suggest on how the best visual and user experience should appear in the FIT application for the following supply collector tool features: 
    • No# 6,7,8,9,10 - Supply collector-specific configuration data to drive the UI/experience:
      • Ability to define a configurable, periodic unit of time to use for supply collection (e.g. per month, per PI, or per sprint). Initial configuration would be monthly.
      • Supply collector-specific configuration data to drive the UI/experience - Ability to define a configurable set of "Delivery phases" with which to associate supply entry (e.g. AR, Build, and possibly Ops)
      • Supply collector-specific configuration data to drive the UI/experience - Ability to define a configurable set of "resource roles" with which to associate supply entry
      • Supply collector-specific configuration data to drive the UI/experience - Ability to configure a capacity planning "window" according to the number of periodic units configured (i.e. initial configuration of 18 months)
      • Supply collector-specific configuration data to drive the UI/experience - Ability to configure the "current period" to anchor the first period of the "planning window"
    • No# 11: Ability for a DG Admin to use a User Interface to enter and submit periodic (e.g. monthly) supply data (headcount) per ART/Delivery Group for the configured planning window (e.g. 18 months), associated with each Delivery Phase and Resource Role.
    • No# 12: Ability for the DG Admin to choose in the User Interface whether to enter differentiated values for each period of the planning window (i.e."ramp plan"), or to enter a single value to apply across the entire planning window. If choosing a ramp plan, ability to have a shortcut to "fill right" on a range of periods identified by the user.
    • No #13: Ability to provide summary views of periodic supply data for the configured planning window (i.e. by Functional Domain), rolling up ART/Delivery Group data, with drilldown to show the detail per ART/DG, and the ability to easily switch between viewing and editing
    • No# 14: Ability to choose to display in the UI a partial length of the planning window (e.g. 6 periods vs. the full 18), and expand to see the full planning window
    • No# 19: Ability to capture a baseline number of "resource hours per period" for each ART/DG, identified by the user as "fixed" or "differentiated" across the planning window. If choosing differentiated, ability to have a shortcut to "fill right" on a range of periods identified by the user.
    • No# 20: Ability to only show in the UI data for periods in the "planning window" + the previous period. Periods no longer in the "planning window" would no longer be editable by either user or admin.
    • No# 21: Ability to display calculated hours per Role/Period/Delivery Phase using the headcount figure and the ART/DG baseline hours.
    • No# 22: Ability for DG Admin to map a DG to one or more People Managers (for the purpose described in the next item)
    • No# 23: Ability for DG Admins to view actual named resources associated with a DG (using DG-associated People Managers and the OrganizationalHierarchies features of the FIT)
    • No# 24: Ability for DG Admins to (optionally) associate named resources with the intersection of a DG/Role/Delivery Phase. Provide ability to select resources rolling up to the DG or outside the DG, but prevent double-assignment of resources. Enable resources to be assigned by a DG Admin within the current DG or "loaned" to an ART.
    • No# 25: Ability for the DG Admin to view a summary/headcount based on named-resource DG/Role/Delivery Phase assignments, and either accept or override the headcount for the first period of the planning window
    • No# 26: DG could assign resources (by named resource or by count) to another ART/DG as a reduction of capacity for the DG. "Lending" would need to be specific to the phase/role being lent, and would continue to be visible from the source DG.
    • No# 27: Ability for receiving ART/DG to  see the augmented supply on their side, along with the source DG. Baseline hours for destination ART/DG would be used for all calculations.
    • No# 29: Ability for DG Admins to see and set each configured Demand Reservation category per ART/DG (across all roles and Delivery phases) as a percentage, and to see "My Supply" minus "My Demand Reservations"
    • No# 30: Ability for Portfolio and DG Admins to see in the UI where supply is allocated to a deprecated or hidden ART/DG, and make a determination to move or re-allocate the supply
    • No# 31: Ability for DG Admins to enter Notes regarding their supply entry per DG/Delivery Phase
    • No# 33: Ability to systematically populate supply data for a new "last" month as the planning window shifts to the right by duplicating the "old" last month data. Make the "updated by" value for this record something that distinguishes it from an actual user entry, so it could potentially be flagged/reported on.
    • No# 35: Ability to enable Portfolio Admins to have a UI view to "approve" changes provided by DG Admins to the supply records. Provide comparison against previous entry to help understand the magnitude/impact of the change.
  • Under "Supply Features-gtap v2 -> Supply Screen Narrative" sheet, you will find the associated configurable metadata that will drive much of the behavior in the supply collector (e.g. Period, Delivery Phases, Resource Roles, Capacity Planning Window, Current Period, Demand Reserve categories). This Supply Screen Narrative sheet should be helpful in terms of understanding how the data relate to each other on these screens


CHALLENGE FORUM


DEVICE SPECIFICATIONS

  • Web/Desktop: Follow screen size from our XD files


DOCUMENTATION


BRANDING GUIDELINES

  • Follow our existing FIT design style!


JUDGEMENT CRITERIA

  • Creativity: Conservative - barely new ideas, use what is already proven to work
  • Exploration: Restrained - strictly follow the provided screen requirements section and production guidelines.
  • Aesthetics: Hi-fidelity design - provide a top-notch finished looking visual design
  • Branding: Strict - carefully follow the provided guidelines and stick to them


MARVEL PROTOTYPE

  • We need you to upload your screens to MarvelApp
  • Please request your MarvelApp prototype in the respective thread in the challenge forum
  • You MUST include your Marvelapp URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment this link while you upload)


FINAL DELIVERABLES

Submission File
  • Submit JPG/PNG image files based on Challenge submission requirements stated above
  • Declaration files document contains the following information:
    • Stock Photos Name and Links from allowed sources
    • Stock Art/Icons Name and Links from allowed sources
    • Fonts Name and Links source from allowed sources
    • Full Details of the Topcoder Policy can be found in this LINK

Source Files
  • All source files of all graphics created in Adobe XD, Sketch, or Figma and saved as an editable layer


FINAL FIXES

  • As part of the final fixes phase, you may be asked to modify your files, add or remove screens or combine details to create a final presentation

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.

Challenge links

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? ‌

CHALLENGE DISCUSSION

Source files

  • Sketch
  • Adobe XD
  • Figma

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30280127