You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@colliand and the P&S team have been working on refining the sales strategy for the P&S MVP 2.0. One of the aspects in need of further refinement is the "fine print" regarding what exactly 2i2c will require in order to manage billing and infrastructure when the the account is owned by a third party.
This is to avoid issues such as with Columbia University, where a lack of adequate privileges raised obstacles to our ability to manage and maintain their infrastructure.
What we need to do
Develop and document a set of customer-facing caveats that clearly illustrate what we need in order to maintain a customer's infrastructure, to be included in the language of a contract
Definition of Done
The fine print and language has been signed off by @colliand and has been incorporated into our standard contracts
The text was updated successfully, but these errors were encountered:
Context
@colliand and the P&S team have been working on refining the sales strategy for the P&S MVP 2.0. One of the aspects in need of further refinement is the "fine print" regarding what exactly 2i2c will require in order to manage billing and infrastructure when the the account is owned by a third party.
This is to avoid issues such as with Columbia University, where a lack of adequate privileges raised obstacles to our ability to manage and maintain their infrastructure.
What we need to do
Develop and document a set of customer-facing caveats that clearly illustrate what we need in order to maintain a customer's infrastructure, to be included in the language of a contract
Definition of Done
The text was updated successfully, but these errors were encountered: