Presentation on Story Design for CI Methodology week 2#2707
Presentation on Story Design for CI Methodology week 2#2707sofiabobadilla merged 6 commits intoKTH:2025from
Conversation
Added contribution presentation files
|
Missing student registration :contributions If not from your group, fetch the upstream. |
|
Readme is not correctly formatted Got: ['Task 1: Continuous Integration & Continuous Delivery', 'Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
|
Readme is not correctly formatted Got: ['Assignment Proposal', 'Title', 'Names and KTH ID', 'Deadline', 'Category', 'Description', 'Relevance'] |
|
Hi @SaiBon99, Good initial draft 👍 Yet, the description is a bit vague. |
|
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 🤠 . |
Assignment Proposal
Title
Story Design for CI Methodology
Names and KTH ID
Deadline
Category
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:
In our presentation we want to illustrate:
An example of a article we draw inspiration from is “Continuous Integration In Agile DevOps: A Comprehensive Guide”.