Tag Archives: exam

Software Engineering I Registration

Software Engineering I, SS13

This is the registration form to participate in the lecture “Software Engineering I” in summer term 2013.
You can specify one partner in the field “Partner of choice” – if this partner also chooses you, this will raise the probability that both of you will make it into one group.

Registration is closed! Teams are generated now and you should get an email till tuesday 30th of april.

PMWS11/12 Klausuraufteilung

Programming Methodologies, WS1112

Da mehr Studenten zur Klausur angemeldet sind als in Raum 0446 klausurgerecht untergebracht werden können, wird die Klausur parallel in Raum 0446 (bei der Bibliothek) sowie Raum 0315 (an der Säulenhalle in Richtung Mensa) stattfinden.
Die Aufteilung erfolgt nach Nachnamen:

Raum 0446: A – Me

Raum 0315: Mi – Z

Diese Information wird am Tag der Klausur ebenfalls an den Türen der betreffenden Räume aushängen.

Examination Rules

Software Engineering I, WS1011

To make the grading system as transparent as possible we decided to publish our assessment criteria here. The final grade of each team member will be calculated as follows:

  • 50% individual- and 50% team effort, where
    • The individual effort is
      • 10% individual time
      • 15% presentation (each release) and
      • 25% role (perception of the role you had in the scrum process during the release)
    • The team effort is
      • 10% team time
      • 40% assessment of the releases (4 releases, each 10%)

What is individual and team time? What is important for the presentation and how do we assess the preception of your different roles? Here are the answers:

  • Individual and team time
    • At least one hour of each individual and team time to get a 4.0.
    • Two hours of each individual and team time to get a 1.0.
    • At the end of each weekly meeting you will get an assessment in the range (-2,…,+2) which will be summarized at the end of SE1 and build your individual/team grade.
    • Individual time
      • Starts counting if at least two team members start working on the project (two because we want to boost pair programming) in the SE lab.
    • Team time
      • Starts counting if at least 75% of the team comes together in the SE lab and start working on the project.
      • Team time also counts into individual time!
  • Presentation
    • Each release ends with the presentation of the results.
    • Present the new features which you developed within the last 4 weeks
    • 50% content. We assess how efficient you’ve worked within the last 4 weeks. Efficency is meant as the relation between the planned and realized features. However you’ll not get a bad grade if you have good arguments why the planned features didn’t get into the product.
    • 50% presentation style.
    • You will get feedback at the end of each presentation!
  • Roles
    • Dependent on the role you had within a release, we will asses as follows
      • Scrum Master
        • “The scrum master has to ensure that the team has everything it needs to get the work done.”
        • Contacts the SE experts and arranges the weekly meetings
        • We will asses how you did this job!
      • Product owner
        • Maintains the Agilo instance and writes “User Stories”.
        • Prioritizes the tasks in the product backlog
        • We will asses how you did this job by having a look at your agilo.
      • Developer
        • We will have a look at the Agilo burndown charts to get a picture what you did