Skip to content

Presentation on Story Design for CI Methodology week 2#2707

Merged
sofiabobadilla merged 6 commits intoKTH:2025from
SaiBon99:patch-1
Aug 30, 2025
Merged

Presentation on Story Design for CI Methodology week 2#2707
sofiabobadilla merged 6 commits intoKTH:2025from
SaiBon99:patch-1

Conversation

@SaiBon99
Copy link
Copy Markdown

@SaiBon99 SaiBon99 commented Aug 28, 2025

Assignment Proposal

Title

Story Design for CI Methodology

Names and KTH ID

Deadline

  • Week 2

Category

  • Presentation

Description

This week we want to present how story/task design—the way user stories and development tasks are written, scoped, and broken down—can impact the success of continuous integration (CI).

Poorly defined stories (e.g., too broad, ambiguous, or lacking acceptance criteria) often lead to large, hard-to-merge branches, unclear responsibilities, and lengthy code reviews. This slows down integration and creates bottlenecks that undermine the core purpose of CI, which is rapid and reliable integration of small changes.

By contrast, well-structured stories with clear scope, testable outcomes, and manageable size enable more frequent commits, faster feedback cycles, and easier conflict resolution. This is supported by industry practices such as:

  • Agile user story principles (INVEST model: Independent, Negotiable, Valuable, Estimable, Small, Testable)

In our presentation we want to illustrate:

  1. What “good” vs. “bad” story/task design looks like from a CI perspectiv.
  2. How story size and clarity directly affect merge frequency and review overhead.
  3. Why CI is not only about tools, but also about disciplined design practices.

An example of a article we draw inspiration from is “Continuous Integration In Agile DevOps: A Comprehensive Guide”.

@dd2482-bot
Copy link
Copy Markdown
Collaborator

Missing student registration :contributions

If not from your group, fetch the upstream.

@dd2482-bot
Copy link
Copy Markdown
Collaborator

Readme is not correctly formatted
Need exactly: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description']

Got: ['Task 1: Continuous Integration & Continuous Delivery', 'Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance']

@dd2482-bot
Copy link
Copy Markdown
Collaborator

Readme is not correctly formatted
Need exactly: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description']

Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance']

@sofiabobadilla sofiabobadilla self-assigned this Aug 28, 2025
@sofiabobadilla
Copy link
Copy Markdown
Collaborator

Hi @SaiBon99,

Good initial draft 👍

Yet, the description is a bit vague.
Could you explain further what you mean by story/task and what your sources are on this "problem"?

@sofiabobadilla sofiabobadilla changed the title Add presentation on Story Design for CI Methodology Presentation on Story Design for CI Methodology week 2 Aug 30, 2025
@sofiabobadilla
Copy link
Copy Markdown
Collaborator

@SaiBon99

Please, next time tag the reviewer so we know it is ready for a second pass.

The current changes are more descriptive, and the presentation looks interesting. Remember to cite your sources, either research papers or industry material.

Merging 🤠 .

@sofiabobadilla sofiabobadilla merged commit ad53f78 into KTH:2025 Aug 30, 2025
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants