.png){kind=logo}
Technical Deployment - Project Plan
Legend:
Optional Deliverable | Mandatory Deliverable | Subsection of Each Point |
|---|
Deliverables/Tasks | Details | Customer Actions | SocialTalent Actions | Persons Responsible | Due Date | Status | |
1 | Sandbox Environment is stood up. | If the customer is in pre launch, it is likely that a Sandbox environment will not be required. Usually just a small number of users are set up to use the Sandbox Environment. |
|
|
|
|
|
1.1 | Assess requirements as to whether a Sandbox environment is required | Decision on need for Sandbox environment | Discuss with SocialTalent | Discuss and assist with decision making |
|
|
|
1.2 | Setup company admin user(s) | Company admin users are setup manually by SocialTalent. Typically, no more than 2 or 3 users would be set up as company adminswould be set up | Share details with Customer Success names and email addresses of users that may be company admins | Customer Success setup company admin users, assign learning path regarding Platform Administration |
|
|
|
1.3 | Plaform Administration learning completed by Company Admins | Company Admins are required to complete Platform Administration training. Company Admins need to have a sufficient understanding of how the platform works. This is essential to success of the deployment and on going operation of the platform | Project Manager nudges Company Admins to complete the Platform Administration training | Assist when questions regarding the training arise |
|
|
|
1.4 | Learners and Team Leader setup | Learners and Team Leaders have been set up, depending on the numbers this may be done manually (one-by-one) or through the use of the bulk-uploader. | Load users | Assist when questions regarding the training arise. |
|
|
|
2 | Production Environment is setup. | Production Environment is stood up with (at a min.) the first batch of users on boarded. |
|
|
|
|
|
2.1 | Setup company admin user(s) | Company admin users are setup manually by SocialTalent. Typically, no more than 2 or 3 users would be set up as company adminswould be set up | Share details with Customer Success names and email addresses of users that may be company admins | Customer Success setup company admin users, assign learning path regarding Platform Administration |
|
|
|
2.2 | Plaform Administration learning completed by Company Admins | If there is no Sandbox environemnt this step is necessary. Company Admins are required to complete Platform Administration training. Company Admins need to have a sufficient understanding of how the platform works. This is essential to success of the deployment and on going operation of the platform | Project Manager nudges Company Admins to complete the Platform Administration training | Assist when questions regarding the training arise |
|
|
|
2.3 | Test user access for a few users | Ideally the test users should be from different teams, groups, countries and IT organisations. Users should also engage in system testing using the following link https://app.socialtalent.com/test | Identifiy a few users and share the details with SocialTalent for loading | Customer success to set up the selected users |
|
|
|
2.4 | Learners and Team Leader setup | Learners and Team Leaders have been set up, depending on the numbers this may be done manually (one-by-one) or through the use of the bulk uploader. | Load users | Assist when questions regarding the training arise |
|
|
|
3 | Single Sign-on (SSO) | SSO is enabled. Users may log in via SSO |
|
|
|
|
|
3.1 | Review SocialTalent SSO Documentation on this knowledge base article | Documentation has been reviewed | Review documentation | Promptly address questions as the arise |
|
|
|
3.2 | SSO configuration details are populated | Per knowledge base article, populate details regarding configuration of SSO | Populate SSO details | Promptly address questions as the arise |
|
|
|
3.3 | SSO is validated and tested | An email is sent to the team validating that SSO has be set up and is working | Test SSO | Promptly address questions as the arise |
|
|
|
3.4 | Exclude certain users from SSO. | On occasion, some users may need to be exluded from SSO. Theses need to be defined and configured. | Exclude users | Promptly address questions as the arise |
|
|
|
3.5 | Indentify Employee ID in SAML string | On occasion, the customer might want the employee id field to be passed from the SAML string and populated in a custom field on SocialTalent | Specify the location of the employee ID in SAML | Map the employee ID value from SAML to a custom ID field |
|
|
|
4 | SSO Auto Provisioning (Self-registration) | Users may self-register/auto provision. This is an optional step. The bulk-uploader may be used as an alternative to auto provisioning. |
|
|
|
|
|
4.1 | Trusted Domains have been configured | Email domains relating to all users have been defined and configured. Only users with emails will be permitted to self register. | Communicated trusted domains to SocialTalent. | Configure the trusted domains |
|
|
|
4.2 | Configure trunk questions and teams | When users log in the team they are assigned to may need to have learning paths assigned by default. | Confer with SocialTalent and share details re the Learning paths that should be assigned based on Trunk questions and teams | Configure trunk teams |
|
|
|
4.3 | If necessary, configure Branch Questions and Branch Teams | Depending on the complexity of the question structure, they may need to be forked to create branch teams | Confer with SocialTalent and share details re the Learning paths that should be assigned based on Branch questions and teams | Configure branch teams |
|
|
|
4.4 | Restrict reporting and data analysis for users of particular countries. | There are cases where the personal data from users that live in some countries may need to be restricted e.g. it may be the case that users based in Germany have exposure to their learning progress restricted. | Confer with SocialTalent and share details re requirements for data restrictions | Configure data restrictions for countries |
|
|
|
4.5 | Test and validate Auto provisioning | Users need to be able to register and authenticate via SSO and be assigned to the correct teams and learning paths. | Execute test | Assist in validating tests |
|
|
|
5 | User Auto Provisioning API setup (SCIM) | Instead of bulk update or self-registration, the customer can choose to use SCIM API, which automated user management |
|
|
|
| |
5.1 | Share understanding of SCIM with Customer PM and Customer tech team | Discuss what SCIM is, how would it solve their problems, how could it impact existing users if any. Decisions about should company admins continue to be allowed to make changes etc. |
| Share documentation, answer any questions. |
|
|
|
5.2 | Share credentials to the SCIM API endpoint. | This could be for production or sandbox environment, depending on customer's comfort level with SCIM and status of production roll-out. |
| Create sandbox company, create admin@company.com account, create and share the API security token and documentation. |
|
|
|
5.3 | Configure and integrate SCIM. | This integration could be done with customer Identity Management systems like Azure or Okta, or in some cases LMSs like Workday as well. | Integration tasks. | Answer any queries arising in the process. |
|
|
|
5.4 | Test, test, test. Integration testing for the API. |
| Run test cases. | Assist in validating test results. |
|
|
|
5.5 | Incrementally add users to SCIM | If for example there are 10k users, add 100 users first, to see how their experience is and if there are any issues. | IDP admin to incrementally add users. |
|
|
|
|
6 | File Content Integration | Assess intergation options | Customer Success rep to arrange a meeting with Product Development as necessary |
|
|
| |
6.1 | Content File Formats | The format of the Content File(s) needs to be defined: | Review this document for sample data fields and other details | Export content data in a file that conforms to the Completion File requirements |
|
|
|
6.2 | Test and iterate on Content Files until validated | Content files will need to undergo riogorous testing to ensure they are consistent with requirements | Test content file uploads and share feedback re testing | Address any requirements for iteration. |
|
|
|
6.3 | Completion File Formats | The format of the Completion File needs to be defined: | Communicate Completion File requirements in detail | Export content data in a file that conforms to the Completion File requirements |
|
|
|
6.4 | Test and iterate on Content Files until validated | Content files will need to undergo riogorous testing to ensure they are consistent with requirements | Test content file uploads and share feedback re testing | Address any requirements for iteration. |
|
|
|
6.5 | SFTP Server Setup | Customer needs to setup an SFTP server as the location as to where the Content and Completion files will reside. | Share with SocialTalent | Export Content and Completion files to SFTP Server. |
|
|
|
Please feel free to reach out to your onboarding specialist with any issues here and you can also download this guide in excel format SocialTalent Technical Deployment - High Level Project Plan.xlsx their is also a project scheduler included in the excel to keep everything on track if you need this as well.