TheEduAssist e-learning design agency logo
Trust Centre

A Structured Method for Planning, Building and Reviewing Learning Projects

A Structured Method for Planning, Building and Reviewing Learning Projects.

Discuss Delivery Requirements
Home / Trust Centre / Delivery Methodology

Delivery Phases

Our typical delivery methodology encompasses the following phases. Specific project phases are confirmed during the definition stage and documented in an agreed Statement of Work.

1

DISCOVERY

Understand goals, audiences, content, technology and constraints.

2

DEFINITION

Confirm scope, deliverables, responsibilities, dependencies and acceptance expectations.

3

DESIGN

Develop curriculum, learning structure, learner journeys, activities and technical plans.

4

DEVELOPMENT

Build approved learning content, assets, platform configuration or supporting materials.

5

REVIEW

Conduct internal, subject-matter and stakeholder reviews.

6

QUALITY ASSURANCE

Review content, learning alignment, functionality, responsive behavior, accessibility considerations and platform delivery.

7

ACCEPTANCE AND LAUNCH

Resolve agreed findings, confirm handover requirements and prepare release.

8

SUPPORT AND IMPROVEMENT

Maintain content or platforms under an agreed follow-on scope.

Note: We do not present this as a fixed timeline; actual timelines vary by project scale and complexity.

Responsibility Model

Clear responsibilities ensure smooth project progression. Final responsibilities depend on the contract and scope, but typically follow this framework.

CLIENT MAY OWN

  • business goals
  • final content accuracy
  • subject-matter approval
  • legal and regulatory decisions
  • platform contracts
  • user and data policy
  • timely access
  • stakeholder decisions
  • final acceptance

THEEDUASSIST MAY SUPPORT

  • learning strategy
  • instructional design
  • development
  • platform configuration
  • content organization
  • quality assurance
  • documentation
  • handover

SHARED RESPONSIBILITIES

  • planning
  • scope clarification
  • reviews
  • risk identification
  • prioritization
  • acceptance criteria
  • launch decisions
  • maintenance planning

Change Control

To manage risk and maintain delivery quality, requests outside the agreed scope are evaluated systematically:

  • requested change
  • scope evaluation
  • effort and dependency review
  • impact on schedule or cost
  • approval
  • implementation
  • testing
  • documentation
Important: Not every change is included automatically. Changes may affect other content or systems. Approved scope controls delivery, and urgent requests may require separate agreement. Unlimited revisions are not assumed.

Quality and Acceptance

Acceptance reviews ensure deliverables meet agreed objectives. We do not claim a universal fixed acceptance checklist; instead, criteria are defined per project.

Possible Review Categories

  • content accuracy
  • instructional alignment
  • functionality
  • responsive behavior
  • assessment logic
  • accessibility observations
  • platform behavior
  • links and downloads
  • media
  • stakeholder requirements

Issue Classifications

Blocking: Prevents learning completion or critical functionality. Requires immediate resolution before launch.
Important: Affects usability or accuracy significantly, but a workaround may exist. Should be resolved.
Minor: Typographical errors, minor visual inconsistencies, or non-critical functionality. Addressed within scheduled review cycles.
Observation: Suggestions for improvement or future consideration that do not prevent acceptance of the current deliverable.

Frequently Asked Questions

Does every project use the same process?
No. While we follow standard principles, the specific phases and depth of review are adapted to the project's complexity, scope, and agreed Statement of Work.
How is scope confirmed?
Scope is initially defined during discovery, formalized in a contract or Statement of Work, and refined during the Definition phase before major development begins.
Who approves learning content?
The client remains responsible for final subject-matter accuracy, business alignment, and legal or regulatory approval.
How are changes handled?
Changes requested outside the agreed scope are evaluated for their impact on timeline, cost, and dependencies before being formally approved and implemented.
Is quality assurance included?
Yes, QA is integrated into our delivery methodology. The specific types of testing (e.g., functionality, accessibility observations, responsive design) are defined in the project scope.
Can projects use milestone reviews?
Yes, we frequently establish milestone reviews (e.g., prototype review, Alpha/Beta releases) to gather feedback and ensure alignment before final delivery.
How is final acceptance handled?
Final acceptance involves resolving agreed findings from the QA and stakeholder review phases against the defined acceptance criteria, followed by formal client sign-off.
What happens after launch?
Post-launch activities, such as handover documentation, training, or ongoing maintenance, are executed as agreed in the project scope. Extended support requires a separate agreement.
Are unlimited revisions included?
No, unlimited revisions are not assumed. Projects include defined review cycles. Additional revisions beyond the agreed scope are managed through the change control process.
AI Assist

AI can help you understand the page. For confirmed scope, timeline, and pricing, talk to TheEduAssist sales team.