Our Implementation Process

Implementation is where we design, develop, test, and prepare your learning platform for launch. It’s a structured, Agile-led process focused on delivering what matters most, based on the priorities defined during your Blueprint.

Your Implementation is driven by a Backlog of features and requirements, created during the Blueprint phase and prioritized using the MoSCoW framework.

We’ll use this backlog to guide delivery, adapting as needed to ensure we stay on track and maximize your budget.

The Implementation Phases

1. UX/UI Design & Requirements Finalization

Based on the outcomes of your Blueprint, we’ll either:

  • Continue and refine existing Lo-Fi wireframes into Hi-Fi visual designs, or
  • Pick up from previously completed designs to fill in any gaps

During this phase, we’ll also:

  • Finalize detailed functional requirements
  • Align design decisions with user needs, accessibility best practices, and your brand identity
  • Give you the opportunity to review, iterate, and approve designs before development begins

Feedback is important during this stage, as design helps us validate ideas quickly and cost-effectively, before we write a single line of code.

2. Development in Sprints

Development is delivered in two-week Agile sprints.

While we’ll start with a high-level plan of how the scope fits across the sprints, the details are flexible by design.

At the end of each sprint, you’ll be invited to a Sprint Demo, where we’ll show completed work and gather your feedback. This structure allows us to:

  • Adjust based on your feedback
  • Reprioritize when needed
  • Make progress visible and traceable
  • Work in focused bursts that increase quality and velocity

Billing is tied to sprint milestones, based on the resources allocated for each sprint. This means you’ll always know what’s being delivered and when, with a clear link between progress and payments.

It helps avoid surprises, ensures full transparency, and allows you to see the tangible value of our time every step of the way.

3. User Acceptance Testing (UAT), Launch Preparation & Content Migration

The final stage of Implementation is focused on preparing for launch, rather than introducing new features.

The last development sprint typically includes fewer new features. Instead, we focus on:

  • User Acceptance Testing (UAT)

    Your team reviews the platform to confirm everything functions as expected. This is your chance to test against agreed requirements, flag bugs, and request clarifications while there is still Implementation budget available.

  • Bug-fixing and final polish

    Based on UAT feedback and our own internal QA, we’ll resolve outstanding issues, smooth out edge cases, and ensure the product is production-ready.

Your Project Manager will ensure your team is equipped to log issues in ClickUp, and guide you through the UAT period.

It's important to participate actively during the Development phase. Any issues raised after budget is exhausted will be handled through Continuous Delivery, which ensures ongoing support and iteration.

4. Migration (if applicable)

If you’ve purchased a Content Migration package as part of your project, this will also be planned into the final sprint.

Migration may include:

  • Moving content from an existing LMS
  • Uploading course materials, users, or assessments
  • Formatting assets for compatibility

If Content Migration isn’t included in your Implementation contract, your Project Manager will discuss options for handling it via an Addendum or Continuous Delivery.