The EUM Software Development Life Cycle

We continuously work on EUM 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 EUM.

In this article:

  • Release Cycle
  • Development Team Composition

Release Cycle

We strive to release a new version of the EUM product that will introduce new features, improvements, and bug fixes every eight weeks.  We may choose to skip or shorten a release cycle if necessary.  

Even though EUM is a pure Software as a Service (SaaS) product, releases are coordinated to be rolled out on Customers’ installations. Ensuring the most applicable environment and experience for everyone with minimum disruption.  

The EUM 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 stable development and performance of the product. 

Every release cycle, describing the duration between major production updates, has an average duration of eight weeks. If critical bugs have been identified, we deliver hot-fixes in between the major releases. 

Agile Diagram

We contact our clients to schedule the upgrade before they are rolled out to their environment to ensure Customers are prepared for product changes.

Development Team Composition

Towards an EUM release, two Scrum teams are working in parallel sprints to deliver items in the sprint backlog. 

Our Scrum teams are cross-functional teams that each include all competencies needed to bring improvements to EUM from description of goal and success criteria to release into production. 

Each team consists of: 

  • 1 Product Manager 
  • 1 Scrum Master 
  • 4 Full-Stack Developers 
  • 1 Front-end Specialist 
  • 2 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 EUM 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 EUM front-end parts, including their test-ability and integration with EUM 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 EUM technical writers with release notes and documentation.

The team collectively is responsible for breaking down features into work items.