The LMS365 Software Development Life Cycle

We continuously work to improve and refine LMS365 to ensure we always offer you a learning environment that meets the needs of the modern workplace. In this article, we describe the LMS365 release cycle and development process methodology.

 

In this article

 

Release cycle

Approximately every fourth week, we will release a new major version of the LMS365 product that will introduce new features and capabilities, enhancements, and fixes. If critical bugs are identified between major releases, we'll deliver hotfixes between major releases.

LMS365 is a pure Software as a Service (SaaS) product so releases will be automatically rolled out to ensure organizations always experience the most up-to-date learning environment.

LMS365 is developed using Scrum agile delivery methodology, where our development process is organized in cycles. To ensure a stable development and performance of the product, each cycle includes a series of recurring events, such as refinement, prioritization, scoping, reviewing, and testing.

 

LMS365_Scrum_development.png

 

For information about how customers can prepare for product changes before they are rolled out to their environment, see this article.

 

Development team composition

Four Scrum teams work in parallel sprints to deliver items in the sprint backlog. 

Each of our cross-functional Scrum teams has all the competencies needed to deliver these items, from description of the goal and success criteria, to release into production. Together, the teams are responsible for breaking down features into individual work items.

Each team consists of:

  • one Product manager. The Product manager fulfils the role of the Product owner for the Scrum team.
  • one Scrum master.
  • Full-stack engineers.
  • Front-end engineers.
  • QA engineers.

 

Product managers

Product managers fulfil the role of the Product owner for Scrum teams and prioritize the list of requirements for future product development and work closely with our UX designers, visual designers, and Scrum teams to ensure LMS365 continues to meet our customers' needs.

 

Scrum masters

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 engineers

Full-stack developers design, build, and maintain efficient, reusable, and reliable code, and maintain the code quality.

 

Front-end engineers

Front-end specialists are responsible for creating reusable front-end components, and generally improving the quality and maintainability of LMS365 front-end parts, including their testability and integration with LMS365 core services.

 

QA engineers

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.

 

Support from other teams

Every release is supported by localization specialists, who provide internationalization and localization updates, a team of technical writers, who prepare the release notes and updated user documentation, and video specialists, who deliver product videos.

 

Was this article helpful?
3 out of 3 found this helpful