Stories

Stories

Team members work on one personal work item (within the profile) and one group item per sprint (outside of the profiles). A work item is a combination of a Learning Story and a User Story.

Learning Story (LS)

Learning Stories focus on establishing a solid approach for realizing a User Story. Example:

As a developer I want to create, based on relevant literature, a well‑substantiated approach for producing a BPMN diagram of the business process, so that I can deliver a robust and traceable product.

An LS includes sources that may later be used in a report to justify the approach. For each source the contribution is noted, and a Word document is produced that details the LS outcome, the intended approach, and the methodology. The LS is executed by the developer and answers three questions:

1. What is the product? What choices can be made? (Theoretical framework)
2. How will I tackle the product? (Methodology)
3. How will I evaluate the realized result? (Acceptance criteria)

User Story (US)

User Stories describe a deliverable result, which can be a product, a piece of software, or an action aimed at improving collaboration. The format is:

As a [role], I want [product], so that [goal].

Each US must be linked to a related LS that contains the definition, approach, and acceptance criteria. The team records issues in GitLab as user stories. Related Learning Stories are added as linked items.

A User Story can be divided into multiple tasks.