Title: Date Objective
Title: Date Objective
Objective: To enhance and optimise the learning experience by applying a remote and
centralised learning management platform and developing a comprehensive Learning
Management System (LMS) that enhances online education delivery, streamlines
administrative tasks, and provides a fast platform for students, teachers, and administrators.
Problem statement: It is hard for students to access the current system, difficult to
manage, and it lacks essential features for effective learning and administration. Also,
students and teachers should be able to learn and manage from remote locations
respectively. This project aims to develop an integrated LMS that solves these problems.
Business needs:
- Centralised platform for course management and delivery.
- Improved user experience for students and teachers.
- Enhanced tracking and reporting of student progress.
- Streamlined administrative processes.
- Reduction in administrative overhead and manual processes.
Short-term goals:
- Develop core LMS features (course creation, enrollment, content delivery).
- Implement basic user roles (student, teacher, administrator).
- Ensure the system is secure and reliable for early users.
- Create a short term improvement plan according to the user feedback for further
improvement.
Long-term goals:
- Expand the feature set with advanced tools (analytics, gamification, social learning).
- Integrate with other educational tools and platforms.
- Achieve widespread adoption across multiple educational institutions.
- Continuously improve the system based on user feedback and technological
advancements.
Stakeholders:
End-users:
- Students: Primary users who will access course materials, submit assignments, and track
their progress.
- Teachers: Users who will create and manage courses, provide feedback, and assess
student performance.
Higher management:
- School Administrators (Principal/ CEO of University/School): Oversee the system's
implementation and ensure it meets educational standards.
- Educational Board Members: Approve and review the system's effectiveness and
compliance with educational policies.
Method(s):
- Interviews:
Conducted with students, teachers, and administrators to understand their needs and pain
points. For example, one-on-one interviews were held to gather detailed feedback on user
requirements and preferences.
- Workshops:
Facilitated with stakeholders to brainstorm features and functionalities. These workshops
included interactive sessions where participants could discuss and prioritise features.
- Surveys:
Distributed to a larger audience to gather quantitative data on desired LMS features. The
surveys included questions on current system shortcomings and desired improvements.
- Prototyping:
Developed interactive prototypes to validate design concepts and gather feedback. These
prototypes were used in user testing sessions to observe how users interact with the
proposed designs.
- Focus Groups:
Held with representative users to discuss and refine requirements. These groups included a
mix of students, teachers, and administrators to ensure diverse perspectives.
- User-friendly Interface:
- Simple and intuitive design
- Easy navigation and accessibility for all users
- Mobile Accessibility:
- Full functionality on mobile devices
- Supports learning on the go
- Content Variety:
- Supports videos, documents, quizzes, and other content types
- Provides a rich and diverse learning experience
- Collaboration Tools:
- Features for discussion forums, group projects, and peer reviews
- Enhances collaborative learning
- Integration Capabilities:
- Ability to integrate with tools like Google Classroom and Zoom
- Ensures a seamless user experience
Prioritising requirements:
Team feedback:
- Developers: Emphasised the need for a scalable architecture that can handle a large
number of users and content.
- UX/UI Designers: Highlighted the importance of user testing to ensure the LMS is easy to
use and meets user needs.
- QA Testers: Suggested early implementation of automated testing frameworks to ensure
the system remains reliable as it scales.
- Stakeholders: Stressed the need for a quick turnaround for the pilot version to gather initial
feedback and make necessary adjustments.
- Jira: For tracking project tasks and requirements, ensuring all aspects of the project are
documented and monitored.
- Microsoft 365: For documenting requirements and collaboration, providing a central
repository for project information.
- Figma: For prototyping and design feedback, allowing designers to create and share
interactive prototypes with stakeholders.
- Google Forms: For surveys and feedback collection, enabling the team to gather
quantitative data from a large audience.
- Miro: For virtual workshops and brainstorming sessions, facilitating remote collaboration
and idea sharing.