PSI Exam Scheduling Integration - Internal Feature Summary
- Steve Ross
- Seth Petry-Johnson
Feature Overview
Feature Summary
PSI Exam Scheduling Integration allows clients who use PSI as their testing vendor to capture exam scheduling information in LearningBuilder.
Feature Documentation
See https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/2784690975. Also, refer to the chart here https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/2785706043/PSI+Exam+Integration+Feature+Road+Map+Analysis#State-of-Documentation
PSI API Documentation https://apidocs.psiexams.com
Prerequisites
Versions:
Any version from 10.0 or above can be configured to use this integration. (@Scott Reed to verify)
Limitations
This integration will only work if LearningBuilder hosts an Identify Server. This means that if a client using SSO and thus authenticating through a system other than LearningBuilder, this integration is not feasible without further innovation.
Feature Road Map
Where do we want the feature to go in the future
Sales?
Scope of Work
Dimension | Pricing | Comments |
|---|---|---|
Installation | Included at no extra cost as part of the test vendor integration fee | The feature is included in the base installation fee when that fee included integration with a test vendor. |
Subscription | Included at no extra cost |
|
Configuration | None | All work is T&M consulting |
Consulting | ~20-30 T&M Hours; may be reduced as integration is refined though other client implementations |
|
Timeline |
| 2-4 weeks |
Sample Statement of Work
None.
Marketing
This feature should be shared with prospective clients during the sales process if they use PSI Atlas as the testing vendor. It should also be discussed at annual upgrade calls for clients who use PSI Atlas but have not implemented the scheduling integration.
Rever to the Exam Scheduling Business Case for the reasons why a client may want to implement this feature.
Sample Clients
Feature Delivery
Training Plan - This may be a link to another page.
How do IAs and clients learn to use the feature
Roll-out Plan - This may be a link to another page.
How do IAs deliver the feature to a client
A detailed list of steps to roll out the feature – likely a separate page
Maintenance Plan - What is needed to make sure this feature keeps works - May be link to another page
Vendor Management
Are their client instance-specific steps?
Are their product-wide steps?
Feature Management / History
Idea Summary - the key values of the feature, high-level uses cases, user stories, workflow diagrams, and feature-specific business rules identified that prompted development of the feature.
Feature Summary - This Confluence article captures the overarching approach to the project to set the stage for individual feature artifacts. The Summary explains, for example, that a feature maintenance plan is unnecessary because it relies exclusively on internal code.
Feature Design - the technical design of the feature and notes what is in and out of scope. Likely its own set of confluence pages which should further reference Jiira cases.
Financial Analysis
What was the funding plan -
Client Innovation dollars
R&D
Fixed Setup Cost
Annual Subscription Fee Add On
How much did the feature actually cost in points
Feature Management Checklist