During this sprint, the group will get to know each other, plan the bachelor's thesis, initiate the development project, and train in web development. The following tasks must be completed during this sprint:

• Training - The group will learn the technical fundamentals independently. To support the students and help them get started faster, every student must complete the mandatory assignments. All labs must be submitted both orally and via Git.
• Administration
  1. Each group creates its own folder in Lisam under "Collaborative workspace/Group XX", where XX is the group number (e.g., Group03). The following subfolders must exist in each group folder: Sprint 1, Sprint 2, Sprint 3, Sprint 4, Report.
  2. All students must register in WebReg under two tabs (both Labs and Bachelor's Thesis). More information about WebReg can be found under Course Administration on the Course Information page.
• Time Reporting - A time report (Lisam provides a template) detailing the time spent on the current sprint and the total time must be submitted to Lisam under "Collaborative workspace/Group XX/Sprint 1", where XX is the group number.
• Project Plan - A project plan must be submitted to Lisam under "Collaborative workspace/Group XX/Sprint1". The purpose of the project plan is for the group to plan their bachelor's thesis. The plan also provides a shared description for the group of what is expected of them, which routines they should follow, and what they can expect from each other, etc. Below are typical points for your project plan. If a point is irrelevant to the project, it may be omitted:
1. Project Organization: project members, contact details, group contract, and areas of responsibility.
2. Schedule with calendar dates/week numbers: for example, time for planning, research, technical studies, and user studies, sprints and their meetings, milestones and deliverables (e.g., project report and prototypes), and relevant meetings, etc. Each sprint during the bachelor's thesis must be planned. When planning, consider the group members' prerequisites.
3. Risk Analysis: what risks exist in the project, how likely they are to occur, and what impact they will have (Likelihood of occurrence x Impact), and what measures will be taken to minimize these risks, which may be short-term or long-term. (Tip: The Owner's Role in Project Risk Management (2005), Chapter: 4 Risk Identification and Analysis: )
4. At the end of the sprint, a sprint retrospective workshop must be held and reported in Lisam under "Collaborative workspace/Group XX/Sprint1".

Deadlines for the sprint are listed below and in the TimeEdit schedule.

vecka 4
2026-01-19	Må	Fö		FÖ	Fö1: Introduktion
2026-01-20	Ti	Fö		FÖ	GIT i praktiken - introduktion
2026-01-21	On	Fö		FÖ	Fö2: Webbutveckling
2026-01-22	To	Labb WS		DATALAB WSHOP	WS1: projekt kick-off
2026-01-23	Fr	Deadline Labb		DEADL DATALAB	Varje grupp skapar en egen mapp i Lisam under "Collaborative workspace/Group XX" där XX är gruppens nummer. Följande mappar ska finnas i varje gruppmapp: Sprint 1, Sprint 2, Sprint 3, Sprint 4, Rapport Redovisning av Lab 0
2026-01-24	Lö
2026-01-25	Sö	Deadline		DEADL	Alla studenter är registrerade i WebReg i både labbar och kandidatarbete
vecka 5
2026-01-26	Må	Fö		FÖ	Fö3: Kandidatarbetet Bibliotekets tjänster och resurser
2026-01-27	Ti	Labb Handledning		DATALAB HA
2026-01-28	On
2026-01-29	To	Labb		DATALAB	Redovisning Labb 1
2026-01-30	Fr	Deadline Frågestund om programmering		DEADL RESURS	Projektplan lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 1"
2026-01-31	Lö
2026-02-01	Sö
vecka 6
2026-02-02	Må	Labb		DATALAB
2026-02-03	Ti	Handledning Fö		HA FÖ	GIT i praktiken - att samarbeta med andra
2026-02-04	On	Labb		DATALAB	Redovisning Labb 2
2026-02-05	To	Frågestund om programmering Handledning WS		RESURS HA WSHOP	WS2: Kandidatarbete och rapport
2026-02-06	Fr	Labb		DATALAB	Redovisning Labb 3
2026-02-07	Lö
2026-02-08	Sö
vecka 7
2026-02-09	Må	Labb		DATALAB	Alla labbar ska redovisas vid senast detta tillfälle (sprint 1 redovisning).
2026-02-10	Ti	Deadline Labb		DEADL DATALAB	Sprintretrospektiv ska lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 1" (boka tid för retrospektivet själva; krockar annars med LARM) Alla labbar ska redovisas vid senast detta tillfälle (sprint 1 redovisning).

In this sprint, the focus is on:

• Writing Bachelor thesis version R1 with the following chapters: Introduction, Background, Theory, Method, and References, as well as the appendix Marketing Plan.
• WHAT is to be developed by defining the vision for the web-based business system, visualized through a prototype, a product backlog, and user stories for each item in the product backlog. The vision should be based on own and others' investigations (which form the basis for the theory and marketing plan).
• HOW the group will collaborate to successfully complete the assignment: the development process (i.e., when testing should be performed, definition of done, how acceptance testing is conducted), and working methods (i.e., communication, group goals, group contract).
• Setting up the technical development environment.

The following is expected to occur during the sprint:

• A sprint planning meeting should be held before the sprint.
• A sprint retrospective should be held at the end of the sprint.
• At least three daily Scrum meetings are held per week.

Deadlines for the sprint are listed below and in the TimeEdit schedule.

Written submission

The following must be submitted in writing during the sprint.

1. Project plan - At the beginning of the sprint, an updated version of the project plan, including a detailed sprint plan, must be submitted in Lisam.
2. Bachelor's thesis report version R1 - The chapters Introduction, Background, Theory, Method, and References, as well as the appendix Marketing Plan, must be written during this sprint. More detailed information about the report can be found on the Report page.
   • Note that these chapters and the appendix must be well-written and finalized, so that during the final sprint only the remaining chapters (Results, Discussion, and Conclusions) need to be written.
   • It is crucial that you have a well-defined research question to focus on throughout your bachelor's thesis.
   • Follow the Instructions for the bachelor's thesis report in course TDDD83 and the Assessment template for the bachelor's thesis report, which will be used to evaluate the reports.
   • The submitted chapters must be supported by scientific references, and the requirement regarding the number of references in the bachelor's thesis report must be met in the submitted report. Tips on relevant literature can be found on the Literature page.
   • The Method chapter must specify what will be done to answer the research question, including an evaluation based on a method established in the field, supported by scientific references. Tips on evaluation methods can be found on the Literature page.
   • The Marketing Plan must also be included, as its results will serve as the basis for implementation in the next sprint.
   • The report is submitted in Lisam.
3. Development environment - Each group member must have a functional development environment for the project, corresponding to what was done in Lab 0, on the computer that will be used during the project.
4. A time report detailing the time spent during the current sprint and the total time.
5. Sprint retrospective - A report on the outcome of the Sprint 2 retrospective workshop.
6. System description:
   • prototype, basic system architecture, standards, APIs, etc.
   • Initial risk analysis of the system development, which will serve as input for the next sprint planning and the project plan.

All submissions in Lisam must be made under "Collaborative workspace/Group XX/Sprint 2", where XX is the group number.

Oral Presentation

During the Sprint 2 presentation, you must secure funding for your project.
The presentation will involve two or three groups at a time. During this session, all projects will be presented to an investor (played by the examiner and supervisor). Since product development and marketing require significant investment, the investor will approve projects with great care. Your task is to ensure your project gets the green light and evolves into a viable product. All students in the group must be prepared to present, as two group members will be randomly selected to speak. The investor expects to learn about:

• the system's vision – a pitch following the NABC model; see the course literature page for tips
• the results of the risk analysis
• profitability – when will the product become profitable, and can we recover the investment cost (~1700 hours = one annual salary = 2 MSEK including overhead)?

Conclude by presenting the outcomes of the sprint retrospective.

The expectation for the other groups is that they remain active, provide oral feedback that drives the work forward, alert the presenting group to any shortcomings or issues, ask a series of questions, and so on.

The presentation should be delivered in Swedish or English (recommended) and will last approximately 20 minutes per group, including at least 5 minutes for discussion and questions from the other groups. Attendance at the presentation is mandatory. Your group's time slot is listed in TimeEdit.

Each group member must also demonstrate their functional development environment during the supervision meeting.

Report Feedback

• Each group must also provide written feedback and an assessment of the bachelor's thesis report to the other group by using the Bachelor's Thesis Report Assessment Template and answering the following questions for the relevant chapters with justification. (If there were three groups at the presentation, the group you are opposing is listed in TimeEdit or in the table below generated from TimeEdit)
• The supervisor and the examiner provide feedback on the chapters, and Thomas Rosenfall provides feedback on the Marketing Appendix.
• All feedback is submitted to the respondent's folder in Lisam where the report is located.

vecka 7
2026-02-11	On	Handledning		HA
2026-02-12	To	Deadline WS		DEADL WSHOP	Grupperna får ISRN-numret till rapporten Frågeställningen + sprintplan + uppdaterad projektplan lämnas in i Lisam i gruppens mapp under "Collaborative workspace/Group XX/Sprint 2" WS: sprintplanering
2026-02-13	Fr	Scrummastermöte		MÖ
2026-02-14	Lö
2026-02-15	Sö
vecka 8
2026-02-16	Må
2026-02-17	Ti	Redovisning Fö WS		RE FÖ WSHOP	Extra redovisningstillfälle Fö 4: Utveckling av användbara system WS4: Användbara system. Gör förberedelse på kurssidan
2026-02-18	On
2026-02-19	To	Handledning		HA
2026-02-20	Fr	Scrummastermöte		MÖ
2026-02-21	Lö
2026-02-22	Sö
vecka 9
2026-02-23	Må
2026-02-24	Ti	Handledning		HA
2026-02-25	On
2026-02-26	To
2026-02-27	Fr	Seminarium		SE	Etikseminarium 1. Samling i S41
2026-02-28	Lö
2026-03-01	Sö
vecka 10
2026-03-02	Må
2026-03-03	Ti	Handledning Deadline		HA DEADL	Skriftlig redovisning av Sprint 2 i Lisam under gruppens mapp "Collaborative workspace/Group XX/Sprint 2". Studenterna lämnar återkoppling till den andra gruppen samtidigt som kursledningen under Sprint 3. Rapportinlämning i Lisam
2026-03-04	On	WS		WSHOP	WS3: Sprintretrospektiv. Gör förberedelse för workshopen på kurssidan innan workshopen
2026-03-05	To	Redovisning		RE	Sprint 2 redovisning. Obligatorisk närvaro. 13-14: Grupp 3+6 (Xin) 14-15: Grupp 4+5 (Animesh+Reyhane) 15-16:30 Grupp 2+7+1 (Máté+Ahmad+Dominik; grupp 2 opponerar på 7, grupp 7 på 1, grupp 1 på 2)

Sprint 3 is the implementation sprint, during which the business system is built. The outcome of this sprint is a web-based business system (web application) aligned with the backlog functionality developed in the previous sprint. The following activities are expected during the sprint:

• A sprint planning meeting must be held before the sprint begins.
• A sprint retrospective must be held at the end of the sprint.
• At least three daily Scrum meetings are held per week.
• Code refactoring takes place at the end of the sprint.
• Acceptance testing is utilized.
• The business system must be demonstrated to the supervisor during each supervision meeting.
• Implementation is carried out iteratively, meaning the sprint is divided into smaller sub-sprints.
  

Note that it is difficult to make accurate estimates of time and resources at the beginning of a project. Therefore, if all items in the product backlog are completed according to the group's definition of done, new items should be added. Remember that you have a research question to answer, which implies that some form of evaluation must be conducted to address it. Plan accordingly.

Deadlines for the sprint are listed below and in the TimeEdit schedule.

Written submission

Each group must submit the following materials in Lisam under the Sprint folder (under "Collaborative workspace/Group XX/Sprint 3" where XX is the group number):

1. An updated project plan including a sprint plan for the sprint
2. User stories for the sprint
3. An updated version of the bachelor's thesis based on feedback comments, along with a list of changes made since the previous submission, clearly indicating which actions were taken in response to all comments.
4. Report on the outcome of the current sprint's retrospective
5. A time report detailing the time spent on the current sprint and the total time

Before the oral presentation, each group must test the other group's system and submit a test report in GitLab, as well as provide written code feedback by creating issues in GitLab. The purpose is to help each other improve both the system and the code. Each group must also grant reporter access to the GitLab project for the other group, the supervisor, and the examiner.

Oral Presentation

Attendance at the oral presentation is mandatory. The presentation should take approximately 20 minutes per group, including at least 10 minutes for the presentation itself and 5 minutes for discussion and questions. Each group is present only during their assigned time slot. Presentations are conducted with 2 or 3 groups at a time. Each group should address the following aspects of their project during the presentation (which must not exceed 15 minutes – ensure you keep to the time):

• demonstrate the system
• technical challenges
• examples of code refactoring
• a brief summary from the current sprint's retrospective

The presentation may be given in Swedish or English (recommended).

All students in the group must be prepared to present; during the session, three group members will be randomly selected to present.

After the presentation, the other group should highlight the most important comments from the test report and regarding the code. This part should take a maximum of 5 minutes.

Attendance at the presentation is mandatory. Your group's time slot is listed in TimeEdit.

vecka 10
2026-03-06	Fr	WS		WSHOP	WS: Sprintplanering
2026-03-07	Lö
2026-03-08	Sö
vecka 11
2026-03-09	Må
2026-03-10	Ti	Handledning		HA
2026-03-11	On	Teknisk Support		RESURS
2026-03-12	To	Deadline		DEADL	Sprintplan + uppdaterad projektplan + user stories för sprinten lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 3"
2026-03-13	Fr	Scrummastermöte		MÖ
2026-03-14	Lö
2026-03-15	Sö			Återkoppling	Återkoppling på rapporten från handledare, examinator, Thomas Rosenfall och den andra gruppen lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 2"
vecka 12
2026-03-16	Må
2026-03-17	Ti
2026-03-18	On
2026-03-19	To
2026-03-20	Fr
2026-03-21	Lö
2026-03-22	Sö
vecka 13
2026-03-23	Må
2026-03-24	Ti	Handledning		HA	Extra möjlighet; kan ombokas eller avbokas
2026-03-25	On
2026-03-26	To
2026-03-27	Fr
2026-03-28	Lö
2026-03-29	Sö
vecka 14
2026-03-30	Må	Teknisk Support		RESURS
2026-03-31	Ti	Handledning		HA
2026-04-01	On	Seminarium		SE	Etikseminarium 2. Samling i S41
2026-04-02	To	Scrummastermöte		MÖ
2026-04-03	Fr	Långfredag
2026-04-04	Lö	Påskafton
2026-04-05	Sö	Påskdagen
vecka 15
2026-04-06	Må	Annandag Påsk
2026-04-07	Ti	Deadline Handledning		DEADL HA	I Lisam under "Collaborative workspace/Group XX/Sprint 3" ska följande lämnas in: En uppdaterad version av rapporten En lista på ändringar gjorda från förra inlämningen där det framgår tydligt vilka åtgärder gjorda gällande rapporten
2026-04-08	On	Teknisk Support		RESURS
2026-04-09	To
2026-04-10	Fr
2026-04-11	Lö
2026-04-12	Sö
vecka 16
2026-04-13	Må
2026-04-14	Ti	Handledning		HA
2026-04-15	On	Teknisk Support		RESURS
2026-04-16	To	Scrummastermöte		MÖ
2026-04-17	Fr
2026-04-18	Lö
2026-04-19	Sö
vecka 17
2026-04-20	Må
2026-04-21	Ti	Handledning		HA
2026-04-22	On	Teknisk Support		RESURS
2026-04-23	To
2026-04-24	Fr
2026-04-25	Lö
2026-04-26	Sö
vecka 18
2026-04-27	Må	Deadline WS		DEADL WSHOP	Sprintinlämning inklusive skriftlig redovisning av Sprint 3 i Lisam i gruppens mapp under "Collaborative workspace/Group XX/Sprint 3" WS: Sprintretrospektiv
2026-04-28	Ti	Redovisning		RE	Redovisning Sprint 3. Se kurshemsidan för exakt tid

In this sprint, the focus is on the bachelor thesis, the final presentation (including opposition, presentation, and auscultation), and individual experience summaries.

All submissions and activities for the sprint are shown in the figure below. Deadlines for the sprint are also listed in the figure below and in the TimeEdit schedule.

vecka 18
2026-04-29	On	Deadline WS		DEADL WSHOP	Sprintplan för sprint 4 + uppdaterad projektplan lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 4 WS: Sprintplanering
2026-04-30	To	Valborgsmässoafton
2026-05-01	Fr	Första maj
2026-05-02	Lö
2026-05-03	Sö
vecka 19
2026-05-04	Må
2026-05-05	Ti	Handledning		HA
2026-05-06	On
2026-05-07	To	Seminarium		SE	Etikseminarium 3
2026-05-08	Fr	Scrummastermöte		MÖ
2026-05-09	Lö
2026-05-10	Sö
vecka 20
2026-05-11	Må	Deadline		DEADL	Publiceringsgodkännande för rapporten mailas till Administratören Lämna in Rapport version 3 - R3 under "Collaborative workspace/Group XX/Rapport/Opposition" Rapportinlämning i Lisam senast kl 24:00. Kom överens med den andra gruppen om exakt tid om tidigare tid önskas
2026-05-12	Ti	Deadline Handledning		DEADL HA	Alla studenter ska registrera sig för opposition i webreg enligt instruktioner på kurssidan under Sprint 4
2026-05-13	On
2026-05-14	To	Kristi himmelsfärdsdag
2026-05-15	Fr
2026-05-16	Lö
2026-05-17	Sö
vecka 21
2026-05-18	Må	Redovisning		RE	Opposition och oppositionsauskultation. Tidbokning finns i webreg
2026-05-19	Ti	Handledning		Återkoppling kursledning HA	Bedömning och godkännande från handledare och examinator för presentation i Lisam under "Collaborative workspace/Group XX/Rapport/Opposition". Rapporter som inte är godkända för presentation kan inte presenteras vid redovisningställfället. Återkoppling på marknadsföringsplanen av Thomas Rosenfall.
2026-05-20	On	Scrummastermöte		MÖ
2026-05-21	To
2026-05-22	Fr
2026-05-23	Lö
2026-05-24	Sö
vecka 22
2026-05-25	Må	Deadline		DEADL	Alla studenter med godkända rapporter för presentation ska registrera sig i webreg enligt instruktioner på kurssidan under slutlig redovisning. Nedan lämnas in i Lisam under "Inlämningar" samt i gruppens mapp under "Collaborative workspace/Group XX/Rapport/Presentation": Rapport version 4 - R4 En lista på ändringar gjorde från förra inlämningen ska också lämnas in. Det ska tydligt framgå vilka åtgärder som vidtagits gällande de tre oppositionskommentarerna och eventuella kommentarer från handledare och examinator. Motivera även samtliga kommentarer som ni valt att inte åtgärda. Tidrapporten ska vara uppdaterad (likt alla veckor) Rapportinlämning i Lisam senast kl 24:00
2026-05-26	Ti	Redovisning		RE	Presentation och presentationsauskultation. Tidbokning i webreg för presentationen (och kolla tider för arbeten ni kan auskultera på)
2026-05-27	On
2026-05-28	To
2026-05-29	Fr	Inlämning		INL	Inlämning erfarenhetssammanfattning i LISAM
2026-05-30	Lö
2026-05-31	Sö