Skip to content

2025-05-06

  • Day 2

Confidence and retrospect Tuesday

What helped us learn (let us move forward) 2 min

- A: The active, hands-on approach, the letting us explain concepts, working in smaller groups
- A:
- A: interaction; helping each other; structured exercises
- A: Working in a group, material, instructors, copilot
- A: more coding than yesterday
- A: A lot of coding time
- A: Enough material for people at different levels
- A:
- A: exercises (that include breaking things intentionally), good level of complexity (directory structure, using git(hub), testing exercises), breakout rooms (being able to ask for help/compare)
- A: The exercises, practical coding from scratch and not just filling out pre-existing files
- A: Interaction with teachers: questions asked and questions answered
- A: Hand-on practice

What stopped us from learning (What held us back) 2 min¶

- A: 
- A: Technical issues
- A: Missed big part of the first day, Github access gave me a slow start but was possible to get into it with help of colleagues. It's an extensive  
- A:
- A: Not so much feedback on exercises
- A:
- A: VS Code configuration sometimes confusing (Git config, testing setup)
- A: Not clear what we wanted to achieve during the lectures, specially the first one
- A: not enough time to digest/review
- A: the requirements for the project are a bit unclear to me, so creating suitable issues was challenging
- A: A bit rushed "theory" part (just a little: nothing that couldn't be figured out on our own)
- A:

What could we do to improve learning (What can we invent) 2 min¶

- A: 
- A: Show how a topic connects to the other topics or when it would be useful in the course (or if this is not the case)
- A: I like the theorical background, a bit more would be neat
- A: Have some time reserved in the schedule for self study and QA
- A: 
- A: I think there are two requirements/design files?
- A: Could be good with a summary session to see that everyone got the important points from the exercises
- A: Clearer goals, such as, are we doing this for the next steps or just as a generic example? E.g: the requirements file
- A: 
- A: Could have been useful with a recap after the exercises
- A: Have a clear (and finished) file for the project requirements
- A: Extend the course time or crop the program a bit to give more time for labs/digesting/lecturing

What will we do(Act) [Teachers only]¶

  • RB improves feedback on exercises
  • RB also wants to experiment with a 5-mins-to-read exercise
  • Lars rework hour one
  • Mix theory and practice more
  • Consider moving one hour to "Pardigms and SDLC MDD features lecture"

Confidence Report: (10min)

Give you confidence levels of the following statements, using this scale:

  • 0: I don't know even what this is about ...?
  • 1: I have no confidence I can do this
  • 2: I have low confidence I can do this
  • 3: I have some confidence I can do this
  • 4: I have good confidence I can do this
  • 5: I absolutely can do this!

I can create, assign and close an issue"

  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 4

I can use TDD to develop functions

  • A: 4
  • A: 5
  • A: 4
  • A: 3
  • A: 3
  • A: 3
  • A: 5
  • A: 3
  • A: 5

I can use a kanban board

  • A: 4
  • A: 5
  • A: 4
  • A: 4
  • A: 5
  • A: 4
  • A: 3
  • A: 3
  • A: 3

I know how to make a risk for a requirment

  • A: 3
  • A: 3
  • A: 3
  • A: 4
  • A: 3
  • A: 3
  • A: 4
  • A: 1
  • A: 5

I know the major parts of a development cycle

  • A: 4
  • A: 4
  • A: 4
  • A: 5
  • A: 4
  • A: 3
  • A: 4
  • A: 1
  • A: 5

I know the major technichal risks with a SW project

  • A: 3
  • A: 3
  • A: 2
  • A: 2
  • A: 3
  • A: 0
  • A: 4
  • A: 0
  • A: 0

I know where to find the 'latest' best practices,3.375

  • A: 0
  • A: 2
  • A: 2
  • A: 2
  • A: 0
  • A: 0
  • A: 2
  • A: 0
  • A: 0

I understand what SDLC is

  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 4
  • A: 5
  • A: 5
  • A: 0
  • A: 5

I know what a Feature is

  • A: 4
  • A: 5
  • A: 5
  • A: 5
  • A: 3
  • A: 5
  • A: 5
  • A: 2
  • A: 4

I understand how features relate to Requirments

  • A: 4
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 4
  • A: 5
  • A: 2
  • A: 4

I understand why TDD is important

  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 4
  • A: 5

I understand why assert is important

  • A: 5
  • A: 5
  • A: 4
  • A: 4
  • A: 5
  • A: 4
  • A: 5
  • A: 4
  • A: 5

I understand why a kanban board is important

  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 4
  • A: 4
  • A: 5

I understand why issues are important

  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5
  • A: 5