We continuously work on LMS365 to improve and refine the product and ensure we always offer a learning environment meeting the needs of the modern workplace. This article will describe the release cycle and development process methodology of LMS365.
In this article
Every sixth week, we release a new major version of the LMS365 product that will introduce new features, improvements, and bug fixes.
As LMS365 is a pure Software as a Service (SaaS) product, releases are automatically rolled out on customers’ environment. Ensuring the most recent learning environment and experience for everyone.
The LMS365 product is developed using a Scrum agile delivery methodology where our development process is organized in cycles. Each cycle includes a series of recurring events such as task estimation, scoping, review, and testing. This ensures a stable development and performance of the product.
Every release cycle, describing the duration between major production updates, has a duration of six weeks. If critical bugs has been identified, we deliver hotfixes in between the major releases.
For customers to be best possibly prepared for product changes, before they are rolled out to their environment, we always announce coming changes in advance of releases.
Development team composition
Towards an LMS365 release, three Scrum teams are working in parallel sprints to deliver items in the sprint backlog.
Our Scrum teams are cross-functional teams that each includes all competencies needed to bring improvements of LMS365 from description of goal and success criteria to release into production.
Each team consists of:
- 1 product manager
- 1 Scrum master
- 3-4 full-stack developers
- 1 front-end specialist
- 3-4 QA engineers
Our product owners manage and prioritize the list of requirements for future product development and work in close collaboration with our UX designers, visual designers, and Scrum teams to ensure the LMS365 product continuously meets the needs of our customers.
Scrum masters coordinate and facilitate process improvements inside the team to improve collaboration and efficiency and facilitate collaborative problem-solving and idea generation.
Full-stack developers design, build, and maintain efficient, reusable, and reliable code and maintain the code quality.
Front-end specialists are responsible for creating reusable front-end components, and, in general, improving the quality and maintainability of LMS365 front-end parts, including their testability and integration with LMS365 core services.
QA engineers are responsible for performing and improving the different stages of quality assurance practices and processes, including quality control, functional and non-functional testing (for example, verification), validation of requirements, communication and coordination, quality assurance efforts, and processes within the team and organization.
Every release is supported by the LMS365 technical writers with release notes and documentation, and by LMS365 localization specialists with internationalization and localization updates.
The team together is responsible for breaking down features into work items.