LearningBuilder Upgrade Guide
Introduction
As part of your LearningBuilder software subscription agreement, you are entitled to one upgrade per year. A LearningBuilder upgrade moves your instance from its current version to the latest available release. This document provides LearningBuilder clients with guidance around the upgrade process.
The following sections outline the timeline, people, and actions involved in your upgrade.
Participants
A successful upgrade depends on involving the right people at the right time. The process includes participants from both your organization and the Heuristics team.
Client Participants
To ensure a smooth upgrade, please identify the following participants from your organization:
Role | Description |
|---|---|
LearningBuilder Administrator | The primary point of contact for the upgrade. This should be someone who regularly works in LearningBuilder and is familiar with your testing processes. |
Technical Contact | A person who should be informed about technical aspects of the upgrade, such as exam integrations or other advanced system functions. This may be the same person as the Administrator, but not necessarily. |
Informed Parties | Other client contacts who need to stay informed about key decisions, milestones, or scheduling related to the upgrade. |
Heuristics Participants
The following members of the Heuristics team will participate in the upgrade:
Role | Description |
|---|---|
Upgrade Coordinator | Manages the overall upgrade schedule and ensures components align. Your Upgrade Coordinator will reach out via Jira-tracked emails. |
Account Manager | Your primary contact for all LearningBuilder matters. They will assist with special cases, such as Assisted Upgrades or Risk Assessments. |
Project Manager | If you are working with Professional Services, your assigned Project Manager may coordinate the upgrade effort. |
Subject Matter Expert | Has deep knowledge of your LearningBuilder implementation, including any customizations and integrations. |
Upgrade Responsibilities & Timeline
For your standard annual upgrade, we’ll work with you to find an upgrade timeframe that aligns with your business and operational calendar. Upgrades are planned well in advance to reduce surprises and ensure a smooth experience.
The upgrade spans approximately 12 weeks from scheduling to post-upgrade monitoring. The table below outlines responsibilities and actions across the timeline. All dates are shown relative to the Production Upgrade Date.
Date Relative to Prod Upgrade | Length of Time | Action | Responsible Party | Details |
|---|---|---|---|---|
11 Weeks Prior | 1 day | Invitation to Schedule Kickoff Meeting | Heuristics | Your Support Lead will reach out with a Jira-tracked message to establish your upgrade timeframe. Please respond within one (1) week to confirm your timeframe and avoid delays. |
9 Weeks Prior | 1 day | Upgrade Kickoff Meeting | Heuristics & Client | We will meet to confirm roles, expectation, timeline, risk assessment review, etc. for your upgrade. |
7 Weeks Prior | 1 - 2 weeks | Deliver & Review Risk Assessment | Heuristics & Client | We will deliver your upgrade Risk Assessment for your review. |
5 Weeks Prior | 1 day | Test Approach Decision Deadline | Client | Please ensure your Risk Assessment is signed and returned by this point to preserve your upgrade timeline. |
3 Weeks Prior | 2 weeks | UAT Testing | Heuristics & Client | The UAT environment is ready. Testing is conducted per the roles defined in the Risk Assessment, with both Heuristics and the client ensuring system functionality is unaffected. Testing must be completed within 1 week. |
2 Weeks Prior | 1 day | Testing Feedback Deadline | Client | Report any findings or confirm that testing is complete. Note: If issues are identified, Heuristics will resolve them within one (1) week. |
1 Week Prior | 1 day | Production Upgrade Approval Deadline | Client | Confirm testing is complete and approve moving forward with the production upgrade. |
Production Upgrade Date | 1 day | Upgrade Production | Heuristics | Your production environment is upgraded to the new version. |
For 1 Week After | 1 week | Monitor Production | Client | Monitor the live system post upgrade to ensure everything is running as expected. |
What’s Changing in LearningBuilder?
LearningBuilder publishes detailed release notes on our blog. When you upgrade, your instance will include all changes introduced in each interim release between your current version and the new version. We recommend that all LearningBuilder administrators subscribe to the blog and review release notes regularly to stay informed about newly released features, enhancements, and resolved issues.