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

[mahestro]

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.

[Dara-K]

Contest https://www.topcoder.com/challenges/30097706 has been created for this ticket.

This is an automated message for darak via Topcoder X

[arnandosimanjuntak]

Hey guys, I want to confirm several things for this task.

"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)"

The part you mean is this one right?


But I see screen https://marvelapp.com/54cf844/screen/59213988 coming from this section (which I know is called work cards)


Can you clarify that? Did I misunderstand?

I need to know clearly the flow of users when using it, so I can try to find the best solution to solve that :)

[mahestro]

Hi @arnandosimanjuntak, fair doubt.

Scope card refers actually to what's entitled as work cards as you guessed (your second image reference). When user clicks the work card (design the product .. etc), it opens the details view with options to modify the requirements.

Let me know if that makes sense.

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[arnandosimanjuntak]

Can you invite me to MarvelApp project?
I will try to upload it tonight (if there are no obstacles)

[Dara-K]

@arnandosimanjuntak, please sign-up with Topcoder X tool

This is an automated message for darak via Topcoder X

[arnandosimanjuntak]

Hi @mahestro

If you don't mind, Could you explain more about work card functions/scenarios?

I'm a little confused by that.

When users click on a work card, they can do design review, edit requirements, etc. I see there is a tab "Delivery Management" for the users to add a challenge/task and can also add it as a work card.

Based on what changes the scope want to display? - Is it displayed based on the work card (which includes the "Delivery Management" section) or based on changes to each challenge/task (without the "Delivery Management" section)?

[Dara-K]

Contest https://www.topcoder.com/challenges/30097706 has been updated - it has been assigned to ndondo_.

This is an automated message for darak via Topcoder X

[mahestro]

Hi @arnandosimanjuntak, good questions.

Work cards represent project phases. Let's say we have a project with design and development phases, the design phase can contain one, two or N amount of challenges/tasks to complete such phase. Similar to dev phase. That also means that a single design challenge can also be a work card, that's what happens when the challenge is added through the delivery management section.

As for the scope changes, any item modified either from a specific challenge/task or from the general details of the project can be considered as reviewable for scope approval.

For this design exercise, we look forward to seeing two short user flows, for seeing the items to be reviewed (1. Pending Scope Changes) and for requesting (2. Request Customer Approval).

Let me know if that makes sense.

[mahestro]

Just finished reviewing the design. It was a good start.

I understand there is confusion in the flow, and your design definitely helps to start seeing things we didn’t anticipate. Thanks!!

I liked the simplicity of the scope review page. What would be missing is a way to compare what’s the new change of that scope, I think. Something that tells the user: this is new (requirements wise), how do we call that out so that’s easy to notice what I am approving? What’s different from the previous version?

It doesn't have to be super detailed at this stage since this is an initial approach for us to start validating but a comparison would be helpful if you caught my drift. What do you think would be the best way to put that together in the page you designed?

Thanks again for the efforts!

[Dara-K]

Payment task has been updated: https://software.topcoder.com/review/actions/ViewProjectDetails?pid=30097706

This is an automated message for darak via Topcoder X