How can we shape up the Cubyts implementation?

Modified on Fri, 31 Jan at 7:38 AM

Table stakes first:

If you are signing in for the first time then, sign-in to Cubyts using the email address provided in the request form (you must have received the password to the same email address). We have the following recommendations for you:

1. If you like to continue using the email based sign-in then, we recommend you to change the password from the user profile page.

2. Alternatively, you may sign-in using Google or Microsoft (using the same email address provided in the request form).

If you plan to use sign-in using Microsoft then refer to this troubleshooting article to enable Microsoft sign-in.

The recommended phases of Cubyts implementation:

1. Phase 1: Pilot

This phase is designed to build confidence in the platform while maintaining a minimal footprint in terms of data, integration, drift discovery, and resolution.

Outcomes: Measure time saved for resolving code drifts.

Implementation guide: Guide for the pilot phase.

2. Phase 2: Stablize

This phase is designed to expand the integration and drift footprint to discover feature drifts in the system.

Outcomes: Coming soon.

Implementation guide: Coming soon.

3. Phase 3: Growth

This phase is designed to expand the integration and platform footprint to measure the impact of work executed by the team members.

Outcomes: Coming soon.

Implementation guide: Coming soon.