Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connect: Scope change workflow #10

Closed
vic-tian opened this issue May 6, 2019 · 0 comments
Closed

Connect: Scope change workflow #10

vic-tian opened this issue May 6, 2019 · 0 comments
Labels
Connect Designs for the Customer app

Comments

@vic-tian
Copy link

vic-tian commented May 6, 2019

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.

@vic-tian vic-tian added the Connect Designs for the Customer app label May 6, 2019
@vic-tian vic-tian closed this as completed May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Connect Designs for the Customer app
Projects
None yet
Development

No branches or pull requests

1 participant