topcoder-platform / design-pool

Design pool repo for Topcoder-X design task management

Design-Pool

This is the official GitHub repository for Topcoder Design Pool. The issues are used to communicate and track available design work. Please read carefully the rules bellow and reach out to @Dara_K or @vic-topcoder if you have further questions.

How to work with git tickets

The basic flow for handling a ticket is as follows:

1. Assign the ticket to yourself, change the label to "tcx_Assigned", remove the "tcx_OpenForPickup" label. Please only assign tickets to yourself when you are ready to work on it. I don't want tickets assigned to someone and then not have them work on a ticket for 24 hours. The goal here is a quick turnaround for the client. If you can't work on a ticket immediately, leave it for someone else.

2. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically and that it's against the latest commit in Git when you create it.

3. Change the label on the ticket to "tcx_ReadyForReview"

After seeing a ticket marked as "tcx_ReadyForReview", the copilot will review that ticket, usually within 24 hours.

Note that you are expected to keep your changes in-sync with Git - make sure to do a pull before you push changes to make sure there aren't any merge issues.

Accepted fix

If a fix is accepted, a payment ticket will be created on the Topcoder platform within 5-10 minutes of the issue being closed. You should see the payment in your PACTs within 24 hours.

Rejected fix

If a fix is rejected, a comment, and possibly a screenshot, will be added to the ticket explaining why the fix was rejected. The status will be changed to "tcx_Feedback".

If a fix is rejected, that ticket is your priority. You should not assign yourself any more tickets until you complete the required additional fixes!

Payment amounts

Each ticket in GitHub has a dollar value. That is the amount you will be paid when the ticket is completed, merged, and verified by the copilot. Note that there is still a 30 day waiting period as the payment will be treated as a regular Topcoder challenge payment.

Task Size Matrix

Size	Duration
Small	≤ 2h
Medium	2~5h
Large	6~10h

Important Rules:

• You can assign any unassigned issue to yourself with an "Open for pick up" label (first come first serve)

• You can only assign ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.

• You will fix the ticket by committing changes to the master branch.

• After marking a ticket "tcx_ReadyForReview" you are eligible to accept another. You do NOT need to wait for the copilot to validate your fix.

• You can do as many tickets as you want, as long as you follow the rules above.

• If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment on the ticket.

• You can ask questions directly on the GitLab ticket.

ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR GITHUB ACCESS!

design-pool's Issues

[$250] Prototype Customer delivery with defined scope

Prototype Scenario 1 from the attached document (https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit#heading=h.d7nmue4dyw96)

This document outlines screen by screen what is desired to see on each screen for all four scenarios:

https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit?usp=sharing

Note: Several screens can be reused throughout the four scenarios. The primary goal is to illustrate a sample end to end workflow for the future work intake, work planning and execution process within Connect against the four scenarios described above.

Use https://share.goabstract.com/0c23b803-75dd-49e4-91c0-228d2e0d345b and https://share.goabstract.com/77cf58df-b5c9-4be6-b5f9-e0e2b742670e to build the screens. Create the prototype in a single sketch file. Create each prototype on its own page. Design for 1280px width. Use the TC Brand Library 2019 for buttons, forms, and fills. Do not redesign the form elements at this point.

Build the prototype as a series of screens in MarvelApp

[$150] Connect-0819-010: Scope Change Workflow Design - Iteration #2

Format

• Size: Medium.
• Payment: $150.
• Deadline: Aug 17 | 06:00 AM UTC-4.

Summary

Follow up of #43.

Major turnout: Scope is based on the intake form the user initially goes to enter data about the project - see https://share.goabstract.com/fa0d5fcd-19fe-4ee0-9720-45b645e416a7?sha=3dca91ccfa1003b2a3874c1b10530b85f8610f47

A user (Topcoder, or customer) could initiate a scope change on a project. The reason for a scope change is multifold - it could be changing a previously set parameter (Ex. going from 2-4 screens to 5-8), it could be including additional add-ons (Ex. Admin tool development) into the project, or it could be including new deliverables into a project (Ex. the customer originally only purchased 'designs' for an app, but now they want to do development with us).

Both customers and Topcoder users could initiate this change. The only difference is that if a Topcoder user was the originator of the change, I want there to be one additional step where the customer approves the change.

On the backend, once the change is approved, the details of the change will be sent to Salesforce, where our account executives manage the customer's account from a billing perspective. While the change is being processed by the account executive, we want to reflect the change as "Pending Scope Change" inside Connect until we receive a trigger back from Salesforce that the customer's billing account has been updated to reflect the revisions to the project's scope.

Screen/Features Details

1. Dashboard - https://marvelapp.com/5661h4e/screen/59926107

• For the upper right hand corner, prior to any scope changes being initiated, can the button say "Review/Modify Scope".

2. Scope Change - https://marvelapp.com/5661h4e/screen/59926109

• Replace “Upgrade Project” button with “Update Scope”.
• It would be useful to include some subtext underneath the "Project Scope" header to say something like "Modify project scope by updating your selections below, then click the "Update Scope" button when complete. Open to ideas.
• If modifying the scope, the user should be able to see the initial intake form somehow in order to change the scope of the project.
• If the user is reviewing/approving scope changes, she should see a visible highlight of what changed compared to the previous state.
• Screen not needed - https://marvelapp.com/5661h4e/screen/59926111

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Abstract branch: https://share.goabstract.com/3bb5f957-5627-457e-bd46-5638fa9a86a3
  • Project Dashboard: https://share.goabstract.com/2132ddda-cbf1-4e9c-a60c-5109f1829d43

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4273036/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

Design project progress report page

Design a new page on Connect where the customers can view different reports for the project. We will start with progress report on the page, which will sum up all the work progress in the project.

The page should allow specific project details to be clearly visible; think of it as a dashboard for all reports, similar to the starting page of Google Analytics. Upon clicking on the widgets a detailed report would be loaded in a panel - follow the interaction pattern from https://marvelapp.com/3h6bdfd/screen/56035770 (click on a work card to open the details).

[$150] Connect-0719-002: Scope Change Workflow Design

Format

• Size: Medium.
• Payment: $150.
• Deadline: July 29 | 06:00 AM UTC-4.

Summary

Here is the background on outlined processes for scope change workflows in Connect:

• Scope cards will be displayed at the top of every project in Connect. The closed version of the scope card should reflect the project's high-level deliverables and cost, level-setting this for users as well as serving a progress/financial reporting purpose (reference screen 30 in this marvel design: https://marvelapp.com/54cf844/screen/59214136).
• When the scope card is opened by the user, they should see a summary version of their project's scope intake form and should be able to modify the parameters of the project (refer to https://marvelapp.com/54cf844/screen/59213988).
• If a customer is the user doing the scope modification, they should be able to immediately save and submit their changes once complete; in the backend, this data will be sent to Salesforce to adjust the customer's billing for the project, and as a result we need a view of "pending scope changes" until things are finalized in SFDC. If it was not a customer who was modifying the scope, an additional step of "request customer approval" will be required prior to data being saved/submitted to Salesforce. We will need designs to show the interactions mentioned above.

Screen/Features Details

1. Pending Scope Changes

• Client user should be able to see a notice of “Pending Scope Changes” after modifying requirements.
• Client user should be able to see what the changes were (comparison?), considering files, text requirements, etc.
• We need to see suggestions on where to allocate a proper space where to display the pending scope changes.

2. Request Customer Approval

• We need to see suggestions on where to allocate a proper space where to display the scope approval actions and workflow.
• User should be able to see what the new changes are (see 1. Pending Scope Changes).

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Abstract branch: https://share.goabstract.com/3bb5f957-5627-457e-bd46-5638fa9a86a3
  • Project Dashboard: https://share.goabstract.com/2132ddda-cbf1-4e9c-a60c-5109f1829d43

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4229497/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

Concept challenge: Checklist

Launch a new concept challenge that will increase engagement through interactive task list for users. The goal is to design a platform solution that displays a list of tasks to be completed to the users. The tasks might be sequential or non-sequential, required and optional, and they should be visible at particular centralized UI interfaces. Explore all flows (complete profile, select interests, read an article, sign a document, create work requirement, etc.) and placements (dashboard, sidebar, challenge card, work card, etc.).

[$250] Prototype Topcoder delivery with defined scope

Prototype Scenario 2 from attached document (https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit#heading=h.oox0fij3or77)

This document outlines screen by screen what is desired to see on each screen for all four scenarios:

https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit?usp=sharing

Note: Several screens can be reused throughout the four scenarios. The primary goal is to illustrate a sample end to end workflow for the future work intake, work planning and execution process within Connect against the four scenarios described above.

Use https://share.goabstract.com/0c23b803-75dd-49e4-91c0-228d2e0d345b and https://share.goabstract.com/77cf58df-b5c9-4be6-b5f9-e0e2b742670e to build the screens. Create the prototype in a single sketch file. Create each prototype on its own page. Design for 1280px width. Use the TC Brand Library 2019 for buttons, forms, and fills. Do not redesign the form elements at this point.

Build the prototype as a series of screens in MarvelApp

Connect: Milestone Update user flows

Overview
Currently, Architects/Copilots need to choose a phase template with their desired number of milestones. In the work card iteration of phase templates, we will give the Architects/Copilots enhanced control over managing milestones while also creating increased automation of milestone creation.

Requirements
All work card scenarios should begin with a minimum of two milestones (Start/Complete). The scenarios below indicate how milestone management capabilities will change based upon how the work card is used.

Scenario 1: Work Card is kept generic.

• Will have two required milestones: Start and Complete.
• Architects/Copilots will have the capability to add-in an additional two milestones, if needed, for a total of four milestones in the work card.
• Architect/Copilot milestone controls:
  • Add-in an optional two milestones and select the type of milestone they required from the list below:
    • Reporting Milestone: Generic functionality where the milestone is simply represented on the timeline.
    • Design Review/Final Design Selection Milestone: Enhanced functionality for conducting a design review/final design selection.
  • Update the title of the milestone
  • Set the date for the milestone while work card is in Draft and Planned status.
  • Mark the milestone complete.

Scenario 2: Challenge(s)/Task(s) are linked to the work card.
By default, a complete "reporting" milestone should be added to the timeline for each challenge/task associated to the workcard, signifying the completion of the challenge or task.

• The CP/Architect should be able to delete automatically created reporting milestones representing the end of a challenge or task
• The CP/Architect should be able to update the description of the milestone for each automatically created reporting milestone
• If a challenge/task is still in progress past beyond the planned end date, the milestone should shift to the new end date. The timeline should reflect the original and revised date, as well as update the total timeline duration.
• Once a challenge/task is completed, it should automatically mark the associated reporting milestone as complete.
• Architect/Copilot controls
  • Change the platform-generated milestone type (switch a reporting milestone to a design review milestone, vice versa)
  • Change the platform-generated milestone default date (move the milestone to another date before/after the completion of the challenge)
  • Delete platform-generated default reporting milestones representing the end of a challenge (cannot delete the start and complete milestones for the timeline)
  • Add-in a new milestone and choose milestone type
  • Update the milestone titles/descriptions
  • Manually mark a milestone complete

Connect: Display Scope Card in Project Plan

Finalize the display of scope card accordingly. Make sure we enable scope change request from customer. In connection with #10

Requirements:

• When the scope card is opened, users should be able to see the following information:
• Requested deliverables indicated during project intake
• Requested add-ons associated to delivery phases indicated during project intake
• Unselected add-ons available for requested delivery phases
• Unselected delivery phases available
• When the scope card is opened, users should be able to modify certain parameters. The requirements for these scope change activities are indicated in subsequent features.

[$250] Platform: Sidebar

Explore visually and build the final UI specification for the sidebar component.

To Design:

• Connect sidebar explorations
• Community sidebar exploration
• Final polishes to the menu
• Block layout system
• Explore sidebar on mobile
• Project status manual control in sidebar (pause or cancel a project)

Overview
Streamline experience for TC users we will adopt a standard sidebar navigation experience that is consistent between Connect and the Community.

Requirements

• We will remove the top-level tabs of Dashboard, Scope, and Project Plans
• We will still display the project status in the left sidebar, but controls over modifying project status will be updated (re: Feature in Project Plan - Integrate/Automate Project Status)
• Beneath the project status we will be creating the following tabs:
• Dashboard: This will be the default page/tab that is opened when a user accesses a project. It will show both the full project plan and the scope card.
• Discussions: This tab will reflect all project discussions in a single repository, including the discussions occurring on individual project plan work cards as well as stand-alone discussion threads.
• Library: This tab will reflect a single repository of all files and links shared in the project, including those shared in project plan discussions as well as stand-alone discussion threads.
• Reports: This tab will eventually reflect reports created on the project, including financial burndown, progress burndown, and delivery-specific reports, such as QA results.
• Team Management: This tab will support the current team management capabilities, including inviting and removing users from a project.
• Underneath the primary navigation tabs in the left sidebar, the current project Topcoder and customer members will be displayed. Architects should be called out separately from Topcoder project members, as this is a professional service that customers are paying for and it would be good to highlight who is their Architect.

Display Scope Card in Project Plan

Overview

For all project delivery, the scope form completed during project intake should be displayed at the top of the project plan. Users will use this scope card during delivery to manage any scope change.

Design Requirements

• Closed scope card (intake form) should be displayed at the top of Connect project plan:

  • Closed card should display summary of project deliverables (will vary based upon project type)

  • Closed card should display the following dashboard reports, by user:

    • Project Progress (Customers; All Topcoder viewable): Summarized view of % of work in each work card status (planned/in progress/complete)

    • Project Financials (Customers; All Topcoder viewable): Summarized display of total project spend (Topcoder margin + community work budget) vs. what has not been billed yet.

    • Project Work Budget (All Topcoder viewable only): Sum of all workstream budget(s) measured against what has been spent vs. what is available to spend.

• Closed scope card should display a "Modify" button, which will open the work card and enable the user to modify scope, if necessary

• When the user clicks on the card, or clicks the button saying "Modify," the scope card should open. The details presented on the open card will vary based upon the nature of the project. In addition, the opened card should display the information presented on the closed card as well.

Functionality Requirements

• Remove separate scope tab from Connect projects

• The closed scope card should reflect the deliverables required by the customer that they indicated during project intake in the form of the deliverables bar outline.

• The scope card should be able to be opened by clicking on it.

• When the scope card is opened, users should be able to see the full version of the scope form they originally completed during intake.

• When the scope card is opened, users should be able to modify certain parameters. The requirements for these scope change activities are indicated in subsequent features under Projects Delivery Only, Solution Block Delivery Only, and TaaS Delivery Only.

[$350] Redesign Veterans.topcoder.com home page

Redesign of the Veterans home page (https://veterans.topcoder.com/) .

We want to clean up the UX of the page and redesign and change the way we present the content.

Visual direction:

• Use the new color palette from TC Brand Library 19

• Use some of the visual elements/typography from "Website 3.0 Production" (https://share.goabstract.com/cf82b47a-7929-4cc6-89f9-039ac7aaddec )

• Replace the posed images of soldiers with a civil life people working on computers. Search in Unsplash or other sources.

• Keep the soldiers programming in "Learn & Explore" section.

• Use the monochrome TC logo - we're deprecating the multi color version

Content organization:

• Replace the slider with a hero banner section. Design 2 versions of the hero slider with different call to action (CTA):

  • Join the veterans community - for not logged in - use some of the content from the join the community slider

  • Learn about crouwdsourcing and Topcoder for joined members

• Replace the navigation with the black navigation we have at https://share.goabstract.com/57bf20de-6085-4a49-9f5b-8acee0c262d8. You have to adapt it to match the content. Keep the current navigation structure from veterans, but add About Us section

• Transfer the content of the other 2 sliders as part of the page.

• Move the latest challenges closer to the top

• Move the news and updates closer to the top

Explore 2 layout options for the page and try to make it easy to read through, and on-brand.

[$350] Challenge Management

For this task, we are looking at a couple of updates for the management of a challenge in Connect.

All the files needed for this project are in: Abstract > Business App (Connect) > Connect App. Sketch > Proto – Experience – TC page: https://app.goabstract.com/projects/f5ad5620-9d7d-11e7-afe2-2b4ecfac8af8/branches/master/files/0D3DED93-CB84-4E3E-A692-FD152A752177/pages/3BF274EB-C524-4652-A15D-F46830440C9D

All the requirements detailed below can be seen here: https://marvelapp.com/4acgiai/screen/58136218 with notes from Ariel.

1.Design Review:
https://marvelapp.com/4acgiai/screen/58407761
This design reflects the activities the customer/Topcoder should be able to see during a design review milestone. What is missing from this design in my perspective are the clear edit controls for customers on how they would interact with the design review milestone, including:

1. Ranking their preferred designs
2. Providing feedback on the designs in free text fields next to each design submission

2. Requirements Editor
https://marvelapp.com/4acgiai/screen/58441907
In this design I need to have the content updated to show a text field input under the "Requirements" tab. This tab is meant as a requirements collaboration space between customers/delivery to align on any requirements for the piece of work being completed. Basic editing tools should be utilized in the free text fields, so users can change font size, font color, created numbered or bulleted lists, etc.

DaraK notes: we should probably see a WYSIWYG editor.

3. Challenges Updates: add a challenge/task, work card with editable milestone and workstream budget
https://marvelapp.com/4acgiai/screen/58441908
On this "Challenges" tab of the work card, I need the design pool to expand on what has already been started in other designs (I will share those as well). First, please rename the "Challenges" tab to "Delivery Management." Essentially on this tab of the work card, which should only be visible to Topcoder users at this time, Architects/Copilots should be able to do the following:

1. They should see a button stating "Add Challenge/Task" 2) When the button is clicked, the user should have the following options: A) Input Challenge/Task ID into a field (this field will be used if the Copilot already created a challenge/task separately, and now wants to add it to the work card) OR B.1) Create new challenge/task button B.
2. When the user clicks this button, they should see a dropdown list of available challenge/task types (Ex. Select F2F) and can select their challenge format.
3. When a user adds challenges/tasks to a work card, we need a design showing the added items.
   On the work card itself, Topcoder users should be able to see the following for each added challenge/task:
   A) Challenge/Task Type
   B) Challenge/Task Title
   C) Challenge/Task Start/End Date
   D) Challenge/Task Cost
   E) A 'Manage Details' button next to each added challenge/task.
   Note: This button will launch the new Challenge/Task Manager app (long-term Direct replacement), which will open a new tab in the web browser where the Copilot can finish setting up the challenge/task details and launch the challenge

Note DaraK: check the screenshot attached to the task – “Delivery Management.png” to see the how this looks now, or go into Abstract > Business App (Connect) > Prototype Scenario 4 – Desktop > 03_4 – Screen-3.

Additionally, on this 'Delivery Management' tab in the work card, the Topcoder users need to see/do the following:

1. They need to see the work card timeline with editable milestones. Note: This work card timeline is built automatically by the platform as users add challenges/tasks to the work card by pulling in data on the start/end dates of the of each challenge/task and creating one timeline for the work card, which is viewable for customers, that is built by using the earliest start date and last end date for all challenges/tasks. Additionally, milestones signifying the end of each challenge in the middle of the timeline will be added automatically by the platform. Topcoder users will also need the capability to manually manage milestones (which are customer viewable) on the work card timeline - more details are provided below.

2. Topcoder users need to see a "Workstream Budget" reflect on the work card. In future project plans, we are building in a component for Topcoder delivery leaders to see the available community work budget (i.e. the amount we have to spend with the community to accomplish the work). This budget will be viewable at both a project-level and a workstream-level. Workstreams, built by the platform, reflect groups of deliverables.
   For example, if a project has both Design and Development on a project, the platform would build two workstreams: Design Workstream, Dev Workstream. Inside the work card on the 'Delivery Management' tab, the Architect/Copilot should be able see the recommended community work budget for their workstream (Ex. Design Work Budget: $5000) and then be able to track their spend within their workstream as they add challenges/tasks to the work card.
   Here is an example: We have a Design workstream budget of $5000. The Copilot adds a challenge to the work card which will cost $1000 to run. When they add this in, they should see the available budget on the work card changed to $4000 left to spend.

3. How editing milestones works:
   Topcoder users should be able to manage milestones on the work card timeline that is viewable to customers. Milestone management capabilities should include:
   A) Editing the date of all milestones
   B) Editing the description of the milestone
   C) Deleting a milestone that was automatically added to the work card timeline by adding a challenge/task, if they do not want to report to the customer on that milestone.
   D) Adding a milestone to the work card timeline. Topcoder users should be able to select the milestone type (reporting milestone, or design review milestone), update the description, and update the date of the milestone.

4. Final Deliverables
https://marvelapp.com/4acgiai/screen/58441909
Remove the "Final Deliverables" tab from the design.

5. Assets
https://marvelapp.com/4acgiai/screen/58441911
Update this tab to reflect a view of all files and links shared on this work card. Ideally, the view of assets shared on the work card should mirror the view of the total projects "Assets Library" that Vic designed (Assets Library.png), just in a consolidated view limited to files/links shared on the specific work card.

[$250] Content panel: Connect work card

Interaction animation in XD
Revise navigation (tabs as icons)
Discussion per milestone - revisions
How to enable the milestone navigation so users can view past milestones?

Fixed Delivery: [$250] Scope Change Workflow

Objective: Once a project is started, scope change can occur at several points of delivery, including:

• Customer/team wants to repurchase a solution (Ex. 1 RUX was performed, another RUX on the same app is desired)

• Customer wants to add a new phase (i.e. a new workstream) of work (Ex. We sold them design, but now they also want us to do the development)

• Customer wants to add an additional add-on(s) to an already planned workstream

• Customer wants to modify the "size" (# of screens, # of devices) of the existing scope of work

High-Level Requirements: A change in scope should result in three changes to the project.

• Scope Card: The rendered summary scope document needs to be updated to reflect the changes to deliverables, cost and timeline to the customer.

• Community Work Budget: The available project total community work budget, as well as the associated workstream budget estimate, needs to update for Topcoder to accurately track the new available budget they have.

• Workstreams: Based upon the selection either a new workstream will need to be added if a new deliverable is included, OR an existing workstream needs to have its summary duration updated if an add-on or change in size modifies the existing workstream(s)

• Send to SFDC/Retrieve data from SFDC: We need to send the change to SFDC and align it to the customer's billing account for this project, so that the Account Executive can complete the sale.

Workflow:

• Increasing Project Scope

  • Both customer and Topcoder should be able to increase the scope of the project, by:

    • Repurchasing an already completed solution (Ex. 1 RUX was completed on a project, but customer wants another RUX for the same app)

    • Adding an additional phase of work (Ex. Going from just design, to design + dev & QA)

    • Including additional add-ons within the scope of an existing phase

    • Increasing the "size" of the existing project (Ex. Increasing number of screens or devices required)

  • If a Topcoder user has modified the scope of the project, the a customer user on the project must approve this change. If the customer user initiated the scope change, this step is not required.

  • Once the scope change is "approved" from the customer-end, the change in project scope should be sent to SFDC in association with the customer’s billing account and project ID. If there is an Account Executive assigned to the customer billing account in SFDC, they should also receive an email alert that the scope of the project has increased so that they can follow-up with the customers immediately and close the sale.

  • Once the sale is completed in SFDC (opportunity marked ‘won’), the changes to the project scope (cost for customer, community work budget, workstream durations) should be reflected.

• Decreasing Project Scope

  • Both customer and Topcoder should be able to increase the scope of the project, with restrictions to the following scenarios only:

    • If no work has been initiated (no challenges/tasks have started), the scope of the project can be decreased with no restrictions.

    • If the project has only one workstream and work has already begun (i.e. challenges/tasks have started), scope cannot be decreased.

    • If the project has multiple workstreams, the scope can be decreased only for workstreams that has had no work start yet.

  • If a Topcoder user has modified the scope of the project, the a customer user on the project must approve this change. If the customer user initiated the scope change, this step is not required.

  • Once the scope change is "approved" from the customer-end, the change in project scope should be sent to SFDC in association with the customer’s billing account and project ID. If there is an Account Executive assigned to the customer billing account in SFDC, they should also receive an email alert that the scope of the project has increased so that they can follow-up with the customers immediately and modify the project’s billing information.

  • Once the sale is completed in SFDC (opportunity marked ‘won’), the changes to the project scope (cost for customer, community work budget, workstream durations) should be reflected.

[$150] Run UX analysis of the existing Veterans Community website.

Go to https://veterans.topcoder.com/ and create analysis report for any problems and possible solutions that you observe.

What are the UX problems a first-time user will face?

Is it clear what the user can do?

Does the page help you understand why you should join?

What can be done to better up the pages and bring the visual styles closer to what Topcoder brand is?

Viki Pere created the UX report on the big problems, see the attached .pdf

[$400] Connect-0819:003: Alternate Work Card Creation Workflow

Format

• Size: Large.
• Payment: $250.
• Deadline: Aug 17 | 06:00 AM UTC-4.

Summary

As a part of the 'Work Management' features we are developing in Connect, we want to explore an alternate concept for how 'work cards' (which represents a unit of work, with challenges associated with it on the backend) are created. We need an alternate prototype workflow designed.

In this scenario, the customer has bought a pre-packaged application solution, combining catalog offerings for design, development, QA, and deployment. The UI from this Marvel design can be repurposed significantly, with several updates - https://marvelapp.com/54cf844/screen/59213988.

Screen/Features Details

Screen 1

• User: Topcoder User
• Context: This is the initial view of a project plan in Connect once the project has been initiated, but no delivery work has begun.
• Screen Contents:
  • Top of Screen: The project’s scope card should be displayed, with information including:
    • Summarized view of required project deliverables - Design, Development, QA, Deployment (Update UI to show all deliverables as included in project scope + the progress report on this scope card should not show any progress at this time)
    • A budget utilization report showing the amount of “Community Work Budget” available for the project. On this first screen, the budget amount can be set to $50K and the report should show that no community work budget has been utilized yet.

Sample image for scope card:

• Header: Build your delivery plan.
• Header subtext: Build your delivery pl`an here so that progress can be reflected to the client and you can manage your community work budget efficiently.
• Beneath the header information, the Topcoder user should see:
  • A sectioned breakout of workstreams, as follows:
    • Design - Available Work Budget: $10,000.00
    • Development - Available Work Budget: $30,000.00
    • QA - Available Work Budget: $5,000.00
    • Deployment - Available Work Budget: $5,000.00
  • A button in each workstream, stating: ‘Create a challenge/task’

Sample image for workstream layout (please do not include the completed work cards until later screens):

Screen 2

• User: Topcoder User
• Context: This screen will show what happens when a Topcoder user clicks the ‘Create a challenge/task’ button underneath a workstream, where they select their desired challenge type.
• Screen Contents:
• Reuse this screen - no changes are required.

Screen 3

• User: Topcoder User
• Context: This screen will show the new challenge/task manager app, where challenge set-up will occur and will be maintained.
• Screen Contents:
  • Input this screen (Ariel to provide sample screen) into the flow - Update to include a few details, such as:
    • Challenge description: ‘Wireframes’
    • Challenge start/end dates
    • Challenge cost ($2,000.00)
  • The prototype should enable a user to click on the ‘Save’ button.

Screen 4

• User: Topcoder User
• Context: This screen will return to Connect’s view of the project’s plan, now with two challenges added in (The challenge the user created in Screen 3, and another challenge that they created for this project while working in the challenge/task manager.
• Screen Contents:
  • Scope card should still be displayed at the top of the project plan, with the community work budget utilization updated to reflect to planned budget use for the two challenges - Available amount: $47,000.00; Utilized amount: $3,000.00
  • The header and header subtext that was originally displayed on Screen 1 should no longer be visible.
  • Workstreams content:
    • Design Workstream - Available Work Budget: $8,000.00
      • The first challenge that was created by the Topcoder user inside the design workstream should be displayed here as a line item, similar to this design:
      • Next to the challenge item on the right-hand side should be a free text field labeled - Title Work Card - where the user can create a name for the work card that will be created to reflect this item to the work card. This field should also have a drop-down option to select any previously created work card labels.
      • Underneath the listed challenge, the button ‘Create a challenge/task’ should still be displayed.
    • Development Workstream - Available Work Budget: $30,000.00
      • Note: the ‘Create challenge/task’ button should be displayed here.
    • QA Workstream - Available Work Budget: $5,000.00
      • Note: the ‘Create challenge/task’ button should be displayed here.
    • Deployment Workstream - Available Work Budget: $5,000.00
      • Note: the ‘Create challenge/task’ button should be displayed here.
    • Uncategorized - Available Work Budget: N/A
      • Since another challenge, titled ‘UI Prototype’ was created in association to this project, but not in association to a workstream, this challenge should be listed here. The challenge data (description, start/end date, cost) should be displayed the same as the challenge above.
      • However, on the right-hand side of the listed challenge, there should now be two editable fields:
        • Designate Workstream: This will be a dropdown selection of Design, Development, QA, and Deploy.
        • Title Work Card: This field should work the same as the field described above.

Screen 5

• User: Topcoder User
• Context: This screen will show the user interaction with the ‘Title Work Card’ under the Design Workstream.
• Screen Contents:
  • Same design as Screen 4, except showing a user typing a title (Ex. Customer UI Cool New App) into the field and clicking ‘Save.’

Screen 6

• User: Topcoder User
• Context: This screen will show a work card created after the user title the work card in Screen 5. The challenge item should now be displayed on a generated work card.
• Screen Contents:
  • Same design as Screen 4, except with the following changes:
    • Under the Design Workstream, a work card should now be displayed. Reuse this UI for the work card (Screen 8 in this Marvel App link). The only updates to the UI for the work card will be:
      • Remove the work budget from being displayed on the card.
      • Update the challenge details displayed to match what you used on earlier screens
        The work card timeline on the Details and Delivery Management tab should now reflect the start and end dates indicated for the challenge, and a Design Review milestone should be included as well.
      • The “Status” options in the upper right corner to a single button, stating “Publish.”

Screen 7

• User: Topcoder User
• Context: This screen will show the completed work card from Screen 6, and will highlight the user’s interaction with the uncategorized challenge.
• Screen Contents:
  • Same design as Screen 6, except with the following changes:
    • Show the user selecting the Design workstream from the “Designate Workstream” dropdown menu for the ‘UI Prototype’ challenge.
    • Show the user selecting the previously created work card title of “Customer UI Cool New App” for the ‘UI Prototype’ challenge.
    • Show the user clicking ‘Save.’

Screen 8

• User: Topcoder User
• Context: This screen will show an updated work card under the Design Workstream, with the second challenge, ‘UI Prototype’ now included on it. The ‘Uncategorized’ workstream should no longer be visible, as there is no longer any uncategorized challenges.
• Screen Contents:
  • Same as Screen 6, except with the following changes:
    • The work card under the Design Workstream now has two challenges, ‘Wireframes’ and ‘UI Prototype,’ listed on it.
    • The work card’s timeline should now reflect the earliest start date of the challenge and the last end date. Additionally, there should now be the following milestones included:
      • A ‘Final Design Selection’ milestone for the Wireframes challenge
      • An additional design review milestone for the ‘UI Prototype’ challenge
      • The ‘Uncategorized’ workstream should no longer be visible
      • The Design Workstream’s available work budget should be adjusted to reflect $7,000.00

Screen 9

• User: Topcoder User
• Context: This screen will the user’s interaction with the ‘Publish’ button on the work card.
• Screen Contents:
  • Same as Screen 8, except with the following change:
    • Show the user clicking ‘Publish’ on the work card

Screen 10

• User: Customer
• Context: This screen will show the customer’s view of Connect’s project plan once a work card has been published.
• Screen Contents:
  • The customer should see the scope card at the top of the project plan, with the following changes:
    • The ‘Community Work Budget’ report should be replaced with a report showing the project’s total cost, $65,000.00 and should reflect the amount they have been invoiced to date ($10,000.00)
    • The customer should see all workstreams listed, with the following changes:
      • Design Workstream:
      • The customer should not see the available work budget for this workstream.
      • The customer should not see the ‘Create challenge/task’ button.
      • The customer should see the published work card. They should be able to see all tabs on the work card except for the ‘delivery management’ tab.
    • Development Workstream:
      • The customer should not see the available work budget for this workstream.
      • The customer should not see the ‘Create challenge/task’ button.
      • The customer should see a message stating, ‘Your Development delivery plan is under construction’
    • QA Workstream:
      • The customer should not see the available work budget for this workstream.
      • The customer should not see the ‘Create challenge/task’ button.
      • The customer should see a message stating, ‘Your QA delivery plan is under construction’
    • Deployment Workstream:
      • The customer should not see the available work budget for this workstream.
      • The customer should not see the ‘Create challenge/task’ button.
      • The customer should see a message stating, ‘Your Deployment delivery plan is under construction’

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Abstract branch: https://share.goabstract.com/3bb5f957-5627-457e-bd46-5638fa9a86a3
  • Proto - Experience - TC Artboard: https://share.goabstract.com/2132ddda-cbf1-4e9c-a60c-5109f1829d43?sha=3dca91ccfa1003b2a3874c1b10530b85f8610f47

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4273081/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

P2: Assets Tab [$150]

Overview

Currently, when a link or file is shared in a phase template it is not reflected in the left sidebar. In the new work card iteration of phase templates, we want to ensure that files/links shared are captured in the total project Library (re: Navigation alignment w/ Community feature in the left sidebar) as well as in an in-work card file and link library.

Requirements

• When a file or link is shared in a work card discussion post it should be added to a work card specific Library, which is accessible on the work card.

• Additionally, this shared file or link should be added to the total project Library, located in the left sidebar of the project, where all shared files or links on the project are accessible.

• The closed work card should display a count of files/links shared on that work card.

• The opened work card should have a Library section where users can view all files/links shared on that work card.

[$75] Launch App Overlay in Connect

Objective: When a CP/Architect clicks "Manage Details" next to a challenge or task linked to a work card in Connect, the Challenge & Task Manager app should open as an overlay in Connect. This is where the CP/Architect will manage the remaining set-up activities for a challenge/task and where the challenge/task can be launched to the community.

Requirements:

• When a CP/Architect clicks "Manage Details" next to a challenge/task linked to a work card, the Challenge & Task Manager app is opened as an overlay in Connect.

• To exit the Challenge & Task Manager app, the CP/Architect can click "X" in the upper right of the modal window overlay. They should then be returned to the view of the open work card they were working on.

Create Open Card Modal Window

Overview

When a user opens a work card, a modal window should pop-out from the right-hand side that reflects total work card details.

Requirements

• Create modal window pop-out

Concept challenge: Design review experience.

Redesign the design review experience for connect and community to be within a singular interface that is overlaid/loaded on top of connect or community.

P0: Update Draft to In Review Project Status Logic

Overview: Remove the additional step of users needing to move project from 'Draft' to 'In Review' to send lead data to SFDC by converting projects to be in 'Draft' status only when the intake form is incomplete and 'In Review' status immediately after intake submission/project creation and leveraging the objective flag to route leads to SFDC appropriately.

Requirements

• Draft: Projects are only considered 'draft' when the intake form is incomplete and not submitted.

• In Review: All projects with a completed intake form should automatically be changed into 'In Review' status upon intake form submission/project creation. However, only projects with the intake form objective flag answer of: "I need work done," "I am exploring my options," or "Submitting Client Request" should have the intake information routed immediately to SFDC. Projects created with the objective flag with 'Internal Project' or 'Demo/Test/Other' should not have lead data sent to SFDC.

[$75] Connect-0719-001: Defect Count Log Report Design

Format

• Size: Small.
• Payment: $75.
• Deadline: July 29 | 06:00 AM UTC-4.

Summary

The edit view of this defect log will only be viewable to certain users. Copilots/Architects need the capability to edit the defect count log on a reoccurring basis. They should be able to enter in numbers only, edit, save and/or cancel changes. The Copilot/Architect should be able to access this report/edit this metric from the "Reports" tab in the left sidebar (this tab/page will be new). Once the Copilot/Architect enters a number into the defect log, this metric should appear as a part of the Crowdsourcing Highlights report.

Screen/Features Details

1. Add/Edit Defect Log

• Add a link/button to create a new defect log from the reports page.
• This view should allow the user to enter the defect data.
• User should able to enter in numbers only.
• There should be the ability to save or cancel this action.

2. Defect Log Details View

• The new metric should appear as a part of the Crowdsourcing Highlights report (see example below)

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Abstract branch: https://share.goabstract.com/3bb5f957-5627-457e-bd46-5638fa9a86a3
  • Report page: https://share.goabstract.com/2132ddda-cbf1-4e9c-a60c-5109f1829d43

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4229474/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

[$250] Prototype Topcoder delivery with budget

Prototype Scenario 4 from attached document (https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit#heading=h.k9fl7f5ne3ut)

This document outlines screen by screen what is desired to see on each screen for all four scenarios:

https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit?usp=sharing

Note: Several screens can be reused throughout the four scenarios. The primary goal is to illustrate a sample end to end workflow for the future work intake, work planning and execution process within Connect against the four scenarios described above.

Use https://share.goabstract.com/0c23b803-75dd-49e4-91c0-228d2e0d345b and https://share.goabstract.com/77cf58df-b5c9-4be6-b5f9-e0e2b742670e to build the screens. Create the prototype in a single sketch file. Create each prototype on its own page. Design for 1280px width. Use the TC Brand Library 2019 for buttons, forms, and fills. Do not redesign the form elements at this point.

Build the prototype as a series of screens in MarvelApp

Connect: Update Work Card Mechanism

General Requirement:
Architects/Copilots should always have the capability to manually update the status of a work card, even if automations are in-place.

• Draft: A work card will be in this status as an Architect/Copilot is creating the work card. This status will be automatically set as the first status of a work card.

• Planned: A work card will be manually moved into this status by an Architect/Copilot once they have completed the set-up of the work card. At this time, the work card will become visible to customer users. Additionally, moving a work card into Planned status will automatically trigger the project status to move into Active status.

• In Progress:

  • If a work card is kept generic (meaning that no challenges/tasks are linked to it), the Architect/Copilot will have to manually update the work card status to In Progress.
  • Architects/Copilots should have the capability to revert the work card status back to Planned.

• Complete: If a work card is kept generic (meaning that no challenges/tasks are linked to it), the Architect/Copilot will have to manually update the work card status to Complete.

  • Architects/Copilots should have the capability to move a work card back to In Progress from Complete in the event an additional challenge or task needs to be added to the work card.

[$75] Connect-0819:008: Pre-Paid Budget/TaaS Financial Report

Format

• Size: Small.
• Payment: $75.
• Deadline: August 22 | 06:00 AM UTC-4.

Summary

For customers who have purchased a pre-paid budget (capacity) or a talent pool, they will receive a report showing the budget utilization of their ‘project.’ The report should indicate the amount of budget they have utilized to-date and the amount left to be utilized.

Screen/Features Details

• Update this report (the Project Budget) to reflect how customers will see and understand their pre-packaged solution’s financials (remove the breakout of budget by work/fees/revenue/remaining) and instead follow the guidelines below - https://monosnap.com/file/Rjo8jj4CnMMCkqUsE5bgzIpTY7rDlf
• The report should be shown on the scope card (in Connect’s primary dashboard), as well as in the “Reports” tab of Connect, where all reports will be shown.
• The report on the dashboard’s scope card should show:
  • Retitle the report to Budget Utilization
  • The total available budget: Ex. $60,000
  • The $ amount the customer has utilized to-date
  • The $ amount the customer has not utilized to-date
  • The most recent date of data refresh of the report
• The report on the “Reports” tab should show the same information as above, except with the following details included:
  • For the utilized budget amount, an indication of which tracks the budget was utilized. See example below:
    • Total Budget: $60,000
    • Total Budget Utilized to-date: $20,000
    • $5,000 spent in design
    • $15,000 spent in QA

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Reports and Project Dashboard pages https://share.goabstract.com/52298a36-e886-4024-9f99-51d87a7ff694?sha=635a497184013b106b3d3a8d22f2656b8dd9c83d

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4279069/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

Connect work card - Milestone interaction stage

Redesign the user experience for all user roles on the following milestone types

Report
Approval
Requirements
Design review
Design delivery
QA report
Development delivery
QA delivery
Data Science (not sure for now)

Navigation: Sidebar alignment w/ Community

Overview

Streamline experience for TC users we will adopt a standard sidebar navigation experience that is consistent between Connect and the Community.

Requirements

• We will remove the top-level tabs of Dashboard, Scope, and Project Plans

• We will still display the project status in the left sidebar, but controls over modifying project status will be updated (re: Feature in Project Plan - Integrate/Automate Project Status)

• Beneath the project status we will be creating the following tabs:

  • Dashboard: This will be the default page/tab that is opened when a user accesses a project. It will show both the full project plan and the scope card.

  • Discussions: This tab will reflect all project discussions in a single repository, including the discussions occurring on individual project plan work cards as well as stand-alone discussion threads.

  • Library: This tab will reflect a single repository of all files and links shared in the project, including those shared in project plan discussions as well as stand-alone discussion threads.

  • Reports: This tab will eventually reflect reports created on the project, including financial burndown, progress burndown, and delivery-specific reports, such as QA results.

  • Team Management: This tab will support the current team management capabilities, including inviting and removing users from a project.

• Underneath the primary navigation tabs in the left sidebar, the current project Topcoder and customer members will be displayed. Architects should be called out separately from Topcoder project members, as this is a professional service that customers are paying for and it would be good to highlight who is their Architect.

[$150] Sidebar: Design specification

Continuing from #3
Build the design deliverable specification; desktop and mobile; for the sidebar component.

[$75] Update Milestone Display

Overview

Update the timeline display from a vertical to a horizontal display on the work cards. The horizontal timeline should be viewable on both the closed and opened work card.

Requirements

• Update display of timeline from vertical to horizontal

Design project progress visualization per workstream type.

Connect displays a work card within a dedicated type of work, called workstream. Each card has its own progress bar and we need to visualize the total progress of the group (workstream).

On a higher level, a project can have several groups of work at the same time (design, development, qa, etc.), and we need to be able to create a cumulative report of all the work progress in a project.

https://docs.google.com/spreadsheets/d/1Gvjjx5weKFXu9pUrEZOiQRdSuEOXhVutKzCn8U2mB6o/edit#gid=0

[$150] Add feedback and rank from customer

In Connect, we need an option for the customers to add the general and individual feedback for the design submissions, as well as rank them. The design should also include a guideline for them to read on how to give feedback and a way to access the Marvel App presentations directly from the system, without the use of additional google documents.

[$75] Connect-0819:004: Temporary Reports Page Design

Format

• Size: Small.
• Payment: $75.
• Deadline: August 14 | 06:00 AM UTC-4.

Summary

We need to create a “coming soon” reports page design.

Screen/Features Details

1. Reports Page

• Remove all report cards below the work in progress card, that’s the only one that stays https://monosnap.com/file/07NKN8i0LLdz6H0eUE62i8vMpCb2OF.
• Below that mentioned card, place a message that reads "More Reports Coming Soon."
• Create a card/component that requests for input about what type of report the client would like to see. I think of a multiple-choice list with a free input text field where the client can enter manually in case any of the options is not her favorite.

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Abstract branch: https://share.goabstract.com/3bb5f957-5627-457e-bd46-5638fa9a86a3
  • Reports Artboard: https://share.goabstract.com/2132ddda-cbf1-4e9c-a60c-5109f1829d43

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4263416/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

[$1000] Connect-0819:005: Challenge Management Mobile Views

Format

• Size: Large.
• Payment: $850.
• Deadline: August 22 | 06:00 AM UTC-4.

Summary

We recently created a new experience for managing challenges within connect. We need to create mobile views for each one of the screens. Some of the proposals might require some interaction screens to display the workflow of the desktop - mobile transition.

Screen/Features Details

• Original screens: https://marvelapp.com/54cf844
• Create mobile views for each of the 31 screens (as long as it makes sense).
• Create a new branch and artboard Proto - Experience - TC Mobile to place the mobile versions.

Screen Specifications

• Mobile: 750px width. Height as much as needed.

Design Assets
Abstract branch:

• Proto - Experience - TC Artboard: https://share.goabstract.com/52298a36-e886-4024-9f99-51d87a7ff694?sha=635a497184013b106b3d3a8d22f2656b8dd9c83d

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4279036/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

[$150] Update Discussions Display & Functionality

Overview

Update in-work card discussions functionality so that discussions are grouped by milestone in the work card.

Requirements

• Link discussions to milestone on the work card. The user should be able to click forward/backward through milestones to review/manage discussions.

• On the closed work card, discussions should not be displayed. Instead, a summary message notification badge will indicate the number of new messages in the work card.

• On the opened work card, full discussion per milestone should be viewable.

• Enable new message notification badge that will display as a count of new messages on the upper right corner of the closed work card, and will display a count of new messages per milestone on the opened work card.

• Ensure that tagging of user handles in the message post is enabled

[$250] Update Milestone Mechanism

Overview

Currently, Architects/Copilots need to choose a phase template with their desired number of milestones. In the work card iteration of phase templates, we will give the Architects/Copilots enhanced control over managing milestones while also creating increased automation of milestone creation.

Requirements

All work card scenarios should begin with a minimum of two milestones (Start/Complete). The scenarios below indicate how milestone management capabilities will change based upon how the work card is used.

• Scenario 1: Work Card is kept generic.

  • Will have two required milestones: Start and Complete.

  • Architects/Copilots will have the capability to add-in an additional two milestones, if needed, for a total of four milestones in the work card.

  • Architect/Copilot milestone controls:

    • Add-in an optional two milestones and select the type of milestone they required from the list below:

      • Reporting Milestone: Generic functionality where the milestone is simply represented on the timeline.

      • Design Review/Final Design Selection Milestone: Enhanced functionality for conducting a design review/final design selection.

    • Update the title of the milestone

    • Set the date for the milestone while work card is in Draft and Planned status.

    • Mark the milestone complete.

• Scenario 2: Challenge(s)/Task(s) are linked to the work card.

  • By default, a complete "reporting" milestone should be added to the timeline for each challenge/task associated to the workcard, signifying the completion of the challenge or task.

  • The CP/Architect should be able to delete automatically created reporting milestones representing the end of a challenge or task

  • The CP/Architect should be able to update the description of the milestone for each automatically created reporting milestone

  • If a challenge/task is still in progress past beyond the planned end date, the milestone should shift to the new end date. The timeline should reflect the original and revised date, as well as update the total timeline duration.

  • Once a challenge/task is completed, it should automatically mark the associated reporting milestone as complete.

  • Architect/Copilot controls

    • Change the platform-generated milestone type (switch a reporting milestone to a design review milestone, vice versa)

    • Change the platform-generated milestone default date (move the milestone to another date before/after the completion of the challenge)

    • Delete platform-generated default reporting milestones representing the end of a challenge (cannot delete the start and complete milestones for the timeline)

    • Add-in a new milestone and choose milestone type

    • Update the milestone titles/descriptions

    • Manually mark a milestone complete

Discussion: Sharing link and files in a message

Redesign the display of shared links and content in a message or comment thread in Connect.

Project status manual update mechanism

Overview
Currently, project status and project plan status are two separate, independent entities. To streamline processes and increase adoption of the project plan, the project status should be integrated into project plan phases and the separate project status displayed should be eliminated.

Requirements
Total project status will still be indicated in left sidebar, but controls from the left sidebar should be modified to only allow the following actions:

• Pause the project: A user should be able to move the project to Paused from any other project status, except Complete. If a project is moved into Paused status, the user should have the capability to move it back to In Review from the left sidebar (this control option should only be available for projects in Cancelled or Paused status).
• Cancel the project: A user should be able to move the project to Cancelled from any other project status, except Complete. If a project is moved into Cancelled status, the user should have the capability to move it back to In Review from the left sidebar (this control option should only be available for projects in Cancelled or Paused status).

The remainder of project statuses will be automated

[$150] Add a link to project scope card & scope panel to download content as rendered PDF document

The closed and open scope card should display an option for users to download the project scope as a rendered PDF document. Our project scope should be rendered as a fully-expanded document, as it is not going to be interactive. Based on the designs from https://share.goabstract.com/77cf58df-b5c9-4be6-b5f9-e0e2b742670e and https://share.goabstract.com/0c23b803-75dd-49e4-91c0-228d2e0d345b design:

• A link on the scope card to download the scope as a PDF document (on card and opened panel)

• PDF render for scope document - print/view on desktop, Letter format. Reuse the form content and style as a guide, but build a text document styles for print/desktop use. PDFs are not interactive.

Connect: Milestone progress UI specification

Build design specification of the horizontal work card progress bar:

States:

• Planned
• Started
• Interaction from user pending
• Completed
• Paused

Variants:
Short form - on work card
Long form - on work panel opened

Interactions:

• Normal
• Hover with tooltip
• Past

Let's figure out if the progress bar can be used as a navigation to display the history of past milestones #5

Zurich "Approval Phase" template

When a new project is created by Zurich (identified via reference code) a default 'Approval' phase template should be displayed for users. This default phase should be displayed on all Zurich projects. This phase should be viewable should immediately be in In Progress status and should be viewable to customer users.

Phase Requirements: Note that in the attachment it shows the default text for each milestone that should be displayed.
Title: Project Initiation & Approval
Milestones:

• Approval for Game Plan & Proposal
• This is milestone that will be completed by the customer. They should have ability to click "Approve" or "Decline"
• Game Plan Development
• Game Plan Review & Approval
• Cost Proposal Development
• Cost Proposal Review & Acceptance
• This is milestone that will be completed by the customer. They should have ability to click "Approve" or "Decline"

Other Considerations:
When a customer selects "Decline" on the first milestone of this phase, the project should be moved to "Cancelled" status with the reason code of "Not a good fit for crowdsourcing."
When a customer selects "Decline" on the last milestone of this phase, the project should be moved to "Cancelled" status with the reason code of "Budget misalignment"

Connect: Work Card properties (optionality)

Overview
Enable Architects/Copilots to choose how to use the work card by either keeping it generic (for reflecting activities such as requirements alignment, research activities, etc), or by linking challenges, tasks, or challenges and tasks, to a work card.

Requirements

• By default, all work cards will begin as generic work cards, meaning that no challenges or tasks are linked to them.
• If an Architect/Copilot chooses to keep a work card generic, they will be responsible for manually creating optional milestones and for maintaining the work card status.
• Architects/Copilots should always see a button on the work card, "Add Challenge/Task," which should always be displayed even if a challenge or task has already been linked to the work card.

Add Challenge/Task

• Once the Architect/Copilot clicks this button, they should see a list of available challenge/task types for selection.
• Once the Architect/Copilot has selected a challenge/task type, it should be added to the work card. At this time, the Architect/Copilot should see the following information presented next to the challenge/task line item on the work card:
  • Challenge/Task Title
  • Start and End Date (blank until CP/Architect set-ups details via "Manage Details" workflow)
  • Challenge/Task Total Spend (blank until CP/Architect sets-up details via "Manage Details" workflow); The workstream budget should be updated to reflect the remaining available budget after the challenge/task details are set-up (Re: Budget Tracker feature)
  • A "Manage Details" button, which will launch the 'Challenge and Task Manager' overlay (Re: Challenge & Task Manager feature), where the Architect/Copilot can manage the set-up details and launch of the challenge/task.
  • "Remove" button, for removing the added challenge or task. This button should be interactable up until the time the challenge or task is in progress, at which time the capability to remove the challenge/task should be disabled for all user roles except Admins.
• Once the Architect/Copilot completes the challenge/task set-up, the work card timeline duration should be adjusted to match the duration of the challenge/task. If there are multiple challenges/tasks linked to work card, Connect should use the earliest start date and the last end date to calculate the total duration to display on the timeline. Additionally, Connect should automatically create a default milestone on the work card timeline at the end of each challenge/task, with the Architect/Copilot retaining editing privileges over these milestones. (Re: Update Milestone Mechanism feature)

Create Zurich 'Approval Phase' Template

When a new project is created by Zurich (identified via reference code) a default 'Approval' phase template should be displayed for users. This default phase should be displayed on all Zurich projects. This phase should be viewable should immediately be in In Progress status and should be viewable to customer users.

Phase Requirements: Note that in the attachment it shows the default text for each milestone that should be displayed.

Title: Project Initiation & Approval

Milestones:

• Approval for Game Plan & Proposal

  • This is milestone that will be completed by the customer. They should have ability to click "Approve" or "Decline"

• Game Plan Development

• Game Plan Review & Approval

• Cost Proposal Development

• Cost Proposal Review & Acceptance

  • This is milestone that will be completed by the customer. They should have ability to click "Approve" or "Decline"

Other Considerations:

• When a customer selects "Decline" on the first milestone of this phase, the project should be moved to "Cancelled" status with the reason code of "Not a good fit for crowdsourcing."

• When a customer selects "Decline" on the last milestone of this phase, the project should be moved to "Cancelled" status with the reason code of "Budget misalignment"

Work management: Challenge creation mock flow

Create a mock that illustrates the flow for creating a new challenge or task:

Objective: When a CP/Architect clicks "Manage Details" next to a challenge or task linked to a work card in Connect, the Challenge & Task Manager app should open as an overlay in Connect. This is where the CP/Architect will manage the remaining set-up activities for a challenge/task and where the challenge/task can be launched to the community.

Requirements:
When a CP/Architect clicks "Manage Details" next to a challenge/task linked to a work card, the Challenge & Task Manager app is opened as an overlay in Connect.
To exit the Challenge & Task Manager app, the CP/Architect can click "X" in the upper right of the modal window overlay. They should then be returned to the view of the open work card they were working on.

Work Card Optionality

Overview

Enable Architects/Copilots to choose how to use the work card by either keeping it generic (for reflecting activities such as requirements alignment, research activities, etc), or by linking challenges, tasks, or challenges and tasks, to a work card.

Requirements

• By default, all work cards will begin as generic work cards, meaning that no challenges or tasks are linked to them.

• If an Architect/Copilot chooses to keep a work card generic, they will be responsible for manually creating optional milestones and for maintaining the work card status.

• Architects/Copilots should always see a button on the work card, "Add Challenge/Task," which should always be displayed even if a challenge or task has already been linked to the work card.

  • Add Challenge/Task

    • Once the Architect/Copilot clicks this button, they should see a list of available challenge/task types for selection.

    • Once the Architect/Copilot has selected a challenge/task type, it should be added to the work card. At this time, the Architect/Copilot should see the following information presented next to the challenge/task line item on the work card:

      • Challenge/Task Title

      • Start and End Date (blank until CP/Architect set-ups details via "Manage Details" workflow)

      • Challenge/Task Total Spend (blank until CP/Architect sets-up details via "Manage Details" workflow); The workstream budget should be updated to reflect the remaining available budget after the challenge/task details are set-up (Re: Budget Tracker feature)

      • A "Manage Details" button, which will launch the 'Challenge and Task Manager' overlay (Re: Challenge & Task Manager feature), where the Architect/Copilot can manage the set-up details and launch of the challenge/task.

      • "Remove" button, for removing the added challenge or task. This button should be interactable up until the time the challenge or task is in progress, at which time the capability to remove the challenge/task should be disabled for all user roles except Admins.

    • Once the Architect/Copilot completes the challenge/task set-up, the work card timeline duration should be adjusted to match the duration of the challenge/task. If there are multiple challenges/tasks linked to work card, Connect should use the earliest start date and the last end date to calculate the total duration to display on the timeline. Additionally, Connect should automatically create a default milestone on the work card timeline at the end of each challenge/task, with the Architect/Copilot retaining editing privileges over these milestones. (Re: Update Milestone Mechanism feature)

Connect: Scope change workflow

Once a project is started, scope change can occur at several points of delivery, including:
Customer wants to add a new phase (i.e. a new workstream) of work (Ex. We sold them design, but now they also want us to do the development)
Customer wants to add an additional add-on(s) to an already planned phase
Customer wants to modify the "size" (# of screens, # of devices) of the existing scope of work

A change in scope should result in three changes to the project:

• The rendered summary scope document needs to be updated to reflect the increased project cost, timeline, and deliverables
• The new phase of work needs to be added, OR an existing phase needs to have its cost and timeline updated if the add-on or change in size modifies the existing phase(s)
• We need to send the change to SFDC and align it to the customer's billing account for this project

Workflow:

• Both customer and Topcoder Managers + Copilots should be able to modify the scope of the project, by:
• • Adding an additional phase of work (Ex. Going from just design, to design + dev & QA)
• • Including additional add-ons within the scope of an existing phase
• • Changing the "size" of the existing project (Increasing/decreasing number of screens or devices required)
• If a Topcoder user has modified the scope of the project, the a customer user on the project must approve this change. If the customer user initiated the scope change, this step is not required.
• Once the scope change is "approved" from the customer-end, an notification should be sent to the Account Manager (if there isn't an account manager already on the project, a notification should be sent to all Account Managers) that the customer has initiated a scope change on the project so they can follow-up with the customer and confirm things on the billing end.

Other Considerations:
There is the concept that we display "blank" phases, which represents the next unpurchased logical phase of work in a project, underneath the active (purchased) phase(s) of work. This "blank" phase should display text stating: "Continue work on your project with Topcoder. See your quote for the X (Ex. Development) phase of work." If a customer clicks on this to see their quote, an Account Manager should be notified.

P0: Work Card Status [$150]

Overview

Currently, the maintenance of phase template statuses is an entirely manual effort. In the work card iteration of phase templates, we seek to automate portions of the work card status maintenance.

Requirements: Topcoder/Copilot users should always have the capability to manually update the status of a work card, even if automations are in-place. Additionally, Topcoder/Copilot users should be able to "delete" a work card in Draft or Planned status.

• Draft: A work card will be in this status as an Topcoder/Copilot user is creating the work card.

  • This status will be automatically set as the first status of a work card

  • The work card should not be viewable to the client at this time.

• Planned: A work card should appear in 'Planned' status when the criteria and workflow listed below have occurred. Additionally, moving a work card into Planned status will automatically trigger the project status to move into 'Active.'

  • A work card can be manually moved into this status by Topcoder/Copilot user once they have completed the set-up of the work card by clicking a button that says, 'Publish.' At this time, the work card will become visible to clients.

  • Any challenges or tasks linked to the work card are planned, but not launched yet. If a challenge or task linked to the work card has already launched, then the work card status should automatically move from 'Draft' too 'In Progress' and skip the 'Planned' status. If this occurs, the project status should also automatically move into 'Active.'

• In Progress:

  • If a work card is has no challenges or tasks linked to it, the Topcoder/Copilot user will have to manually update the work card status too 'In Progress.'

  • If a work card has challenges/tasks linked to it, the work card should automatically be moved into In Progress as soon as the first challenge/task is initiated. If a challenge or task linked to the work card is launched prior to the work card being published (moving into 'Planned' status), the work card should automatically moved into 'In Progress' status and the project status should automatically move into 'Active.'

  • Topcoder/Copilot users should have the capability to revert the work card status back to Planned.

• Complete:

  • If a work card has no challenges/tasks are linked to it, the Architect/Copilot will have to manually update the work card status to Complete.

  • If a work card has challenges/tasks linked to it, the work card should automatically be moved to Complete once the final challenge/task has been completed.

  • Architects/Copilots should have the capability to move a work card back to In Progress from Complete in the event an additional challenge or task needs to be added to the work card.

Github ticket rules

How to work with git tickets

The basic flow for handling a ticket is as follows:

1. Assign the ticket to yourself, change the label to "tcx_Assigned", remove the "tcx_OpenForPickup" label. Please only assign tickets to yourself when you are ready to work on it. I don't want tickets assigned to someone and then not have them work on a ticket for 24 hours. The goal here is a quick turnaround for the client. If you can't work on a ticket immediately, leave it for someone else.

2. Complete the ticket and create a merge request within 24 hours. Please ensure your merge request can be merged automatically and that it's against the latest commit in Git when you create it.

3. Change the label on the ticket to "tcx_ReadyForReview"

After seeing a ticket marked as "tcx_ReadyForReview", the copilot will review that ticket, usually within 24 hours.

Note that you are expected to keep your changes in-sync with Git - make sure to do a pull before you push changes to make sure there aren't any merge issues.

Accepted fix

If a fix is accepted, a payment ticket will be created on the Topcoder platform within 5-10 minutes of the issue being closed. You should see the payment in your PACTs within 24 hours.

Rejected fix

If a fix is rejected, a comment, and possibly a screenshot, will be added to the ticket explaining why the fix was rejected. The status will be changed to "tcx_Feedback".

If a fix is rejected, that ticket is your priority. You should not assign yourself any more tickets until you complete the required additional fixes!

Payment amounts

Each ticket in GitLab has a dollar value. That is the amount you will be paid when the ticket is completed, merged, and verified by the copilot. Note that there is still a 30 day waiting period as the payment will be treated as a regular TopCoder challenge payment.

Important Rules:

• You can assign any unassigned issue to yourself with an "Open for pick up" label (first come first serve)

• You can only assign ONE AT A TIME. The nature of it being assigned will indicate it is not available to anyone else.

• You will fix the ticket by committing changes to the master branch.

• After marking a ticket "tcx_ReadyForReview" you are eligible to accept another. You do NOT need to wait for the copilot to validate your fix.

• You can do as many tickets as you want, as long as you follow the rules above.

• If an assigned task is not done in 24 hours, you will need to explain why it is not completed as a comment on the ticket.

• You can ask questions directly on the GitLab ticket.

ANYONE NOT FOLLOWING THE RULES ABOVE WILL BE WARNED AND POTENTIALLY LOSE THEIR GITLAB ACCESS!

[$75] Connect-0819:007: Pre-Packaged Solution Financial Report

Format

• Size: Small.
• Payment: $75.
• Deadline: August 22 | 06:00 AM UTC-4.

Summary

For customers who have purchased a pre-packaged solution, they will receive a report showing the fixed cost of their project. The report should indicate the amount to-date that they have been invoiced for the project, and the amount left to be invoiced.

Screen/Features Details

• Update this report (the Project Budget) to reflect how customers will see and understand their pre-packaged solution’s financials (remove the breakout of budget by work/fees/revenue/remaining) and instead follow the guidelines below - https://monosnap.com/file/Rjo8jj4CnMMCkqUsE5bgzIpTY7rDlf
• The report should be shown on the scope card (in Connect’s primary dashboard), as well as in the “Reports” tab of Connect, where all reports will be shown.
• The report should show:
  • The total cost of the project
  • The $ amount the customer has been invoiced to date
  • The $ amount the customer has not been invoiced yet
  • The most recent date of data refresh of the report

Screen Specifications

• Desktop: 1280px width. Height as much as needed.

Design Assets

• Reports and Project Dashboard pages https://share.goabstract.com/52298a36-e886-4024-9f99-51d87a7ff694?sha=635a497184013b106b3d3a8d22f2656b8dd9c83d

Final Deliverables

• Abstract
  • New branch with the updated design.
  • All original source files.
  • Files should be created in Sketch.
• Marvel Prototype
  • Project: https://marvelapp.com/project/4279065/
  • We need you to upload your screens to Marvel App.
  • Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.

[$250] Prototype Customer delivery with budget

Prototype Scenario 3 from attached document (https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit#heading=h.vl6hntysp92u)

This document outlines screen by screen what is desired to see on each screen for all four scenarios:

https://docs.google.com/document/d/11rFj_4C-eV2Fz0APlZa2VOI3gqxcz_AqtJyxZFx1kLU/edit?usp=sharing

Note: Several screens can be reused throughout the four scenarios. The primary goal is to illustrate a sample end to end workflow for the future work intake, work planning and execution process within Connect against the four scenarios described above.

Use https://share.goabstract.com/0c23b803-75dd-49e4-91c0-228d2e0d345b and https://share.goabstract.com/77cf58df-b5c9-4be6-b5f9-e0e2b742670e to build the screens. Create the prototype in a single sketch file. Create each prototype on its own page. Design for 1280px width. Use the TC Brand Library 2019 for buttons, forms, and fills. Do not redesign the form elements at this point.

Build the prototype as a series of screens in MarvelApp

P2: Budget Tracking & Repurchasing Workflow [$250]

Objective: In budget/capacity-driven scenarios, both the customer and Topcoder need to be able to manage their available spend consumption of their budget.

Requirements:

• At the top of the work delivery section in Connect both the customer and Topcoder can see information related to spend vs. budget, above the work cards listed below.

• Customer UI

  • The customer should be able to see the total spend related to their project, including both payments to the community as well as topcoder's fees. This "spend" should be displayed as a single spend.

  • The customer should be able to increase their budget at any time by clicking on a button, "Increase Capacity." When this button is clicked, a modal window should open where the customer can indicate their desired budget to purchase in $10K increments - ex. $10K, $20K, $30K, $40K, $50K, $60K, $70K, $80K, $90K, $100K). Once the customer has selected their desired budget amount, this information should be sent to SFDC. In SFDC, once a sales person has been assigned the opportunity that data should be sent to Connect and that sales person should be automatically added to the project in Connect to manage customer communications as the sale is closed. In the interim time, while SFDC processes are going on in the background, Connect should display the following message to customers once they have submitted their desired budget amount: "Thank you! A Topcoder sales executive will follow-up with you shortly to finalize billing on your increased budget capacity."

  • When the customer reaches their final $500 of spend with the community, an action alert in the work delivery section should be displayed indicating that the customer should buy additional budget. The customer should have two buttons displayed with this action alert, stating "Increase Capacity" or "Dismiss." Additionally, when the customer's spend reaches the final $500 in budget, a notification alert and an email should be sent as well. This process should be repeated each time a customer repurchases budget and then their spend reaches the $500 threshold limit again.

• Topcoder Copilot UI

  • Copilots should be able to see the Available Spend ($) (i.e. the community spend) for budget/capacity-driven solution efforts.

• Topcoder Managers/Admins/Account Executives

  • Topcoder Managers/Admins/Account Executives should see a budget consumption report showing both Topcoder's fees as well as available community spend, displayed as two separate values against budget.

  • Any Topcoder Managers/Admins/Account Executives on the project should receive an alert notification + email when the community spend has reached the last $500 threshold, to initiate conversations with the customer. Any of these roles should have the same capabilities as customers to request capacity increases (as outlined in the customer workflow).