The term called User Story is widely used in agile management tools. User Stories or Stories are the requirements written in descriptive texts. The User Stories are further broken down to create Product Backlogs. In agile management tools, Product Backlogs are written in the form of tasks. User Stories are broken down to create transparent Product Backlogs. Product Backlogs have descriptions.

An Epic is a collection of several User Stories. Several User Stories are written under an Epic. The following example shows the relationship between an Epic and its User Stories.

Epic : – Development of simulation of electric vehicles

Description : – The objective is to develop simulation environment of electric vehicles. This simulation environment shall be used in validating different algorithms.

User Story 1 : – To develop a vehicle dynamics model.

Description : – The objective is to develop a detailed vehicle dynamics model having dynamics in (X, Y, Z) directions.

Product Backlog 1 : – To develop the framework of a vehicle dynamics model.

Description : – The objective is to develop the interface of the vehicle dynamics model. This interface needs to be connected to other plant models.

Product Backlog 2 : – To develop the longitudinal dynamics.

Description : – The objective is to develop and parameterize the mathematical model of longitudinal dynamics.

User Story 2 : – To develop a battery model.

Description : – The objective is to develop models of cell chemistry and thermal properties of a battery and parameterize them.

Product Backlog 3 : – To develop state-of-charge model of a battery.

Description : – The objective is to develop state-of-charge model of a battery based on cell chemistry.

Product Backlog 4 : – To develop thermal model of battery to simulate the effect of coolant flow.

Description : – The objective is to develop a coolant flow model and a heat transfer model between the coolant and the battery.

User Story 3: – To develop an electric motor model.

Description : – To develop a detailed model of electric motors to simulate torque generation and cooling effect.

Product Backlog 5 :- To develop a torque generation model.

Description : – The objective is to model torque generation l of electric motors having the specified power rating. The model needs to be parameterized with test-bench data.

Product Backlog 6 :- To develop a thermal model of electric motors.

Description : – The objective is to develop a cooling model of electric motors with mathematics and parametrize the equations with test-bench data.

A Product Owner creates the Product Backlogs from User Stories along with the Scrum Team and orders them and prioritizes them to maximize the value of the product.