Hide menu

TDDD83 Automatic translation; Swedish version is authoritative

Sprints

The course has 4 sprints:

  1. Start-up and training.
  2. Bachelor's report version 1.
  3. Implementation.
  4. Bachelor's report, final presentation, experience summaries.
An approved bachelor's project gives 18 hp, which corresponds to 480 hours where all time the student spends in the course counts, including participation in scheduled activities such as lectures, workshops, and supervision meetings.
  • Approximately 6 hp of the course can be completed during VT1 (approx. 150 hours) and the rest during VT2 (approx. 330 hours).
  • During sprint 3 each student shall spend at least 150 hours on implementation (backend and frontend development, writing HTML code, CSS, logic implementation, etc.) and this shall be clearly visible.
  • After sprint 3 each student should have spent approximately 350 hours.
For more details go to Course structure under the Course information page.
Tid18hp = 480h
 350h
Sprintar Sprint 1:
Uppstart och utbildning
Sprint 2:
Kandidatrapport
version 1
Sprint 3:
Implementation
(minst 150h på implementation)
Sprint 4:
Kandidatrapport, framläggning, erfarenhetssammanfattningar
Datum 2026-01-19 2026-02-10 2026-02-11 2026-03-05 2026-03-06 2026-04-28 2026-04-29 2026-05-31

Sprint 1: start-up and training

During this sprint the group shall get to know each other, the bachelor's project is planned, the development project is started, and the group shall educate itself in web development. During this sprint the following shall be done:

  • Training - The group learns the technical foundation on its own, and to give students support and get started faster each student shall complete the mandatory work. All lab assignments must be presented orally and via Git.
  • Administration
    1. Each group creates its own folder in Lisam under "Collaborative workspace/Group XX" where XX is the group's number, e.g. Group03. The following subfolders shall exist in each group folder: Sprint 1, Sprint 2, Sprint 3, Sprint 4, Report.
    2. All students register in WebReg under two tabs (both Lab assignments and Bachelor's project). More info about WebReg under Course administration on the Course information page.
  • Time reporting - A time report (Lisam has a template) with the current sprint's time spent and the total time shall be submitted in Lisam under "Collaborative workspace/Group XX/Sprint 1" where XX is the group number.
  • Project plan - A project plan is submitted in Lisam under "Collaborative workspace/Group XX/Sprint1". The purpose of the project plan is for the group to plan their bachelor's project. The project plan also provides a shared description for the group of what is expected of them, what routines they shall follow, and what they can expect of each other, etc. Below are listed typical points for your project plan. If a point is irrelevant for the project it may be omitted:
    1. Project organisation: project members, contact details, group contract and areas of responsibility
    2. Timeline 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 as well as relevant meetings, etc. Each sprint during the bachelor's project shall be planned. When planning, take into account the group members' conditions.
    3. Risk analysis: what risks exist in the project, how likely are they to occur and what impact do they have (Likelihood of occurrence x Impact) and what measures are taken to minimise these risks, which may be long-term or short-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 shall be held and reported in Lisam under "Collaborative workspace/Group XX/Sprint1"
Deadlines for the sprint are listed below and in the schedule in TimeEdit.

vecka 4
2026-01-19Fö1: Introduktion
2026-01-20TiGIT i praktiken - introduktion
2026-01-21OnFö2: Webbutveckling
2026-01-22ToLabb
WS
DATALAB
WSHOP

WS1: projekt kick-off
2026-01-23FrDeadline
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
2026-01-25DeadlineDEADLAlla studenter är registrerade i WebReg i både labbar och kandidatarbete
vecka 5
2026-01-26Fö3: Kandidatarbetet
2026-01-27TiLabb
Handledning
DATALAB
HA

2026-01-28On
2026-01-29ToLabbDATALABRedovisning Labb 1
2026-01-30FrDeadline
Frågestund om programmering
DEADL
RESURS
Projektplan lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 1"
2026-01-31
2026-02-01
vecka 6
2026-02-02LabbDATALAB
2026-02-03TiHandledning
HA

GIT i praktiken - att samarbeta med andra
2026-02-04OnLabbDATALABRedovisning Labb 2
2026-02-05ToFrågestund om programmering
Handledning
WS
RESURS
HA
WSHOP


WS2: Kandidatarbete och rapport
2026-02-06FrLabbDATALABRedovisning Labb 3
2026-02-07
2026-02-08
vecka 7
2026-02-09LabbDATALABAlla labbar ska redovisas vid senast detta tillfälle (sprint 1 redovisning).
2026-02-10TiDeadline
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).

Sprint 2: bachelor's report version 1 - R1

In this sprint the focus is on:

  • Writing bachelor's report version R1 with the following chapters: Introduction, Background, Theory, Method and References, as well as the appendix Marketing plan.
  • WHAT shall be developed by producing the vision for the web-based business system, visualised with a prototype, a product backlog and user stories for each item in the product backlog. The vision shall be based on your own and others' research (which forms the basis for the theory and the marketing plan).
  • HOW the group shall work together to succeed with the assignment: the development process (i.e. when testing shall be done, definition of done, how acceptance tests are carried out), ways of working (i.e. communication, group goals, group contract)
  • Setting up the technical development environment

The following is expected to happen during the sprint:

  • Before the sprint a sprint planning meeting shall be held.
  • At the end of the sprint a sprint retrospective shall be held
  • At least three daily Scrum meetings are held per week
Deadlines for the sprint are listed below and in the schedule in TimeEdit.

Written submission

The following shall be submitted in writing during the sprint.

  1. Project plan - At the start of the sprint an updated version of the project plan with a detailed sprint plan shall be submitted in Lisam.
  2. Bachelor's report version R1 - The chapters Introduction, Background, Theory, Method and References, as well as the appendix Marketing plan shall be written during this sprint. On the Report page there is more detailed information about the report.
    • Note that these chapters and the appendix shall be well-written so that they are final, and during the last sprint only the remaining chapters (Results, Discussion and Conclusions) need to be written.
    • It is very important here that you have a good research question to focus on during the bachelor's project. 
    • Follow the Guidelines for the bachelor's report in the course TDDD83 and the Assessment template for the bachelor's report which will be used when assessing the bachelor's reports.
    • The submitted chapters shall be supported by scientific references and the requirement on the number of references in the bachelor's report shall be met in the submitted report. On the literature page there are tips on relevant literature.
    • The methods chapter shall describe what will be done to answer the research question, with an evaluation based on a method established in the field and supported by scientific references. On the literature page there are tips on evaluation methods.
    • The marketing plan shall also be included as its results shall form the basis for the implementation during the next sprint.
    • The report is submitted in Lisam.
  3. Development environment - Each group member has a working development environment for the project corresponding to what is done in Lab 0, on the computer that will be used during the project.
  4. A time report with the current sprint's time spent and the total time
  5. Sprint retrospective - Report of the outcome of the sprint 2 retrospective workshop.
  6. System description:
    • prototype, basic system architecture, standards and APIs, etc.
    • Initial risk analysis of the development of the system, which becomes input for the next sprint planning and the project plan.
All submissions in Lisam shall be made under "Collaborative workspace/Group XX/Sprint 2" where XX is the group number.

Oral presentation

At the sprint 2 review you shall secure funding for your project.
The review takes place with 2 or 3 groups at a time. During this review all projects are presented to an investor (played by the examiner and supervisors). Since product development and marketing costs a great deal of money, the investor will approve projects carefully. Your task is to ensure that your project gets started and can continue as a real product. All students in the group shall be ready to present and at the review it is drawn randomly which two group members present. The investor expects to learn about:

  • the vision for the system - a pitch according to the NABC model, see the course literature page for tips
  • the outcome of the risk analysis
  • profitability - when does the product break even and can we recover the investment costs (~1700 hours = one annual salary = 2 MSEK incl. overhead)?
Conclude by presenting the outcome of the sprint retrospective.

The expectation of the other group is that they are active, provide oral feedback that moves the work forward, draw the presenting group's attention to any deficiencies or problems, ask a number of questions, etc.

The review takes place in Swedish or English (recommended) and shall take approximately 20 minutes/group including at least 5 minutes for discussion and questions from the other group. Attendance at the review is mandatory. The time for your group is in TimeEdit.

Each group member shall also demonstrate their working development environment during the supervision meeting.

Report feedback

  • Each group shall also provide written feedback and an assessment of the other group's bachelor's report using the Assessment template for the bachelor's report and answer the following questions for the relevant chapters with justification.
  • The supervisor and examiner provide feedback on the chapters and Thomas Rosenfall provides feedback on the Marketing plan appendix.
  • All feedback is submitted in the respondent's folder in Lisam where the report is located.
vecka 7
2026-02-11OnHandledningHA
2026-02-12ToDeadline
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-13FrScrummastermöte
2026-02-14
2026-02-15
vecka 8
2026-02-16
2026-02-17TiRedovisning

WS
RE

WSHOP
Extra redovisningstillfälle
Fö 4: Utveckling av användbara system
WS4: Användbara system.
2026-02-18On
2026-02-19ToHandledningHA
2026-02-20FrScrummastermöte
2026-02-21
2026-02-22
vecka 9
2026-02-23
2026-02-24TiHandledningHA
2026-02-25On
2026-02-26To
2026-02-27FrSeminariumSEEtikseminarium 1. Samling i S41
2026-02-28
2026-03-01
vecka 10
2026-03-02
2026-03-03Ti
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-04OnWSWSHOPWS3: Sprintretrospektiv. Gör förberedelse för workshopen på kurssidan innan workshopen
2026-03-05ToRedovisningRESprint 2 redovisning. Obligatorisk närvaro. se kurssida för exakt tid och plats.

Sprint 3: implementation

Sprint 3 is the implementation sprint where the implementation of the business system takes place. The result of the sprint is a web-based business system (web application) according to the backlog functionality developed during the previous sprint. The following is expected to happen during the sprint:
  • Before the sprint a sprint planning meeting shall be held.
  • At the end of the sprint a sprint retrospective shall be held
  • At least three daily Scrum meetings are held per week
  • Code refactoring takes place at the end of the sprint
  • Use of acceptance tests
  • During each supervision meeting the business system shall be demonstrated to the supervisor
  • The implementation shall be done iteratively so the sprint shall be divided into smaller sprints

Note that it is difficult to make a good estimate of time and resources at the start of a project. So if all items in the product backlog are complete according to the group's definition-of-done criteria then new items shall be added. Remember that you have a research question that needs to be answered, which means that some kind of evaluation needs to be done to be able to answer the research question. Plan for this.

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

Written submission

Each group shall submit the following material in Lisam under the sprint's folder (under "Collaborative workspace/Group XX/Sprint 3" where XX is the group number):

  1. An updated project plan containing a sprint plan for the sprint
  2. User stories for the sprint
  3. Updated version of the bachelor's report based on feedback comments and a list of changes made since the previous submission, clearly showing what actions have been taken regarding all comments.
  4. Report of the outcome of the current sprint's retrospective
  5. A time report with the current sprint's time spent and the total time
Before the oral review each group shall both test the other group's system and submit a test report in Gitlab, and provide written feedback on the code by adding issues in Gitlab. The purpose is for you to help each other so that the system and code become better. Each group shall also give reporter access in Gitlab to their project to the other group, the supervisor and the examiner.

Oral presentation

Attendance at the oral review is mandatory. The review shall take approximately 20 minutes/group including at least 10 minutes for presentation and 5 minutes for discussion and questions. Each group attends only during their allocated review time. The review takes place with 2 or 3 groups at a time. Each group shall address the following about their project during the presentation (which shall take a maximum of 15 minutes - make sure you keep to time):

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

The review takes place in Swedish or English (recommended).

All students in the group shall be ready to present and at the review it is drawn randomly which 3 group members present.

After the review the other group shall highlight the most important comments in the test report and regarding the code. That part shall take a maximum of 5 minutes.

Attendance at the review is mandatory. The time for your group is in TimeEdit.

vecka 10
2026-03-06FrWSWSHOPWS: Sprintplanering
2026-03-07
2026-03-08
vecka 11
2026-03-09
2026-03-10TiHandledningHA
2026-03-11OnTeknisk SupportRESURS
2026-03-12ToDeadlineDEADLSprintplan + uppdaterad projektplan + user stories för sprinten lämnas in i Lisam under "Collaborative workspace/Group XX/Sprint 3"
2026-03-13FrScrummastermöte
2026-03-14
2026-03-15Å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
2026-03-17Ti
2026-03-18On
2026-03-19To
2026-03-20Fr
2026-03-21
2026-03-22
vecka 13
2026-03-23
2026-03-24TiHandledningHAExtra möjlighet; kan ombokas eller avbokas
2026-03-25On
2026-03-26To
2026-03-27Fr
2026-03-28
2026-03-29
vecka 14
2026-03-30Teknisk SupportRESURS
2026-03-31TiHandledningHA
2026-04-01OnSeminariumSEEtikseminarium 2. Samling i S41
2026-04-02ToScrummastermöte
2026-04-03FrLångfredag
2026-04-04Påskafton
2026-04-05Påskdagen
vecka 15
2026-04-06Annandag Påsk
2026-04-07TiDeadline
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-08OnTeknisk SupportRESURS
2026-04-09To
2026-04-10Fr
2026-04-11
2026-04-12
vecka 16
2026-04-13
2026-04-14TiHandledningHA
2026-04-15OnTeknisk SupportRESURS
2026-04-16ToScrummastermöte
2026-04-17Fr
2026-04-18
2026-04-19
vecka 17
2026-04-20
2026-04-21TiHandledningHA
2026-04-22OnTeknisk SupportRESURS
2026-04-23To
2026-04-24Fr
2026-04-25
2026-04-26
vecka 18
2026-04-27Deadline
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-28TiRedovisningRERedovisning Sprint 3. Se kurshemsidan för exakt tid

Sprint 4: bachelor's report, final presentation, experience summaries

In this sprint the focus is on the bachelor's report, final presentation (opposition, presentation and observation) and individual experience summaries.

The various submissions and activities during the sprint are shown in the figure below. Deadlines for the sprint are also shown in the figure below and in the schedule in TimeEdit.
vecka 18
2026-04-29OnDeadline
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-30ToValborgsmässoafton
2026-05-01FrFörsta maj
2026-05-02
2026-05-03
vecka 19
2026-05-04
2026-05-05TiHandledningHA
2026-05-06On
2026-05-07ToSeminariumSEEtikseminarium 3
2026-05-08FrScrummastermöte
2026-05-09
2026-05-10
vecka 20
2026-05-11
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-12TiDeadline
Handledning
DEADL
HA
Alla studenter ska registrera sig för opposition i webreg enligt instruktioner på kurssidan under Sprint 4
2026-05-13On
2026-05-14ToKristi himmelsfärdsdag
2026-05-15Fr
2026-05-16
2026-05-17
vecka 21
2026-05-18RedovisningREOpposition och oppositionsauskultation. Tidbokning finns i webreg
2026-05-19Ti
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-20OnScrummastermöte
2026-05-21To
2026-05-22Fr
2026-05-23
2026-05-24
vecka 22
2026-05-25
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-26TiRedovisningREPresentation och presentationsauskultation.
2026-05-27On
2026-05-28To
2026-05-29FrInlämningINLInlämning erfarenhetssammanfattning i LISAM
2026-05-30
2026-05-31

Page responsible: Martin Sjoelund
Last updated: 2026-02-27