Hoppa till huvudinnehållet
Till KTH:s startsida Till KTH:s startsida

EH2070 Project Management and Business Development 6.0 hp

Course memo Autumn 2023-52107

Version 2 – 09/07/2023, 8:55:45 PM

Course offering

Autumn 2023-52107 (Start date 28 Aug 2023, English)

Language Of Instruction

English

Offered By

EECS/Computer Science

Course memo Autumn 2023

Course presentation

Development, procurement, and delivery of complex technical systems normally occur in the form of a project, that is, personnel from different parts of an organization collaborate in working towards a well-defined goal. Since the project organization is temporary, effective routines and methods are required for planning, managing, following-up, and documenting the different phases of the project. This is so that the submitted technical requirements placed on the project are reached within the given time frame and at budgeted cost. A complex technical system is a plant or product where software and hardware together comprise the completed system.

In order to provide the students a versatile insight in the management of industrial projects, realistic cases are combined with theoretical studies and guest lectures. In the theoretical parts of the course, fundamental skills in project management such as planning, documenting, and following up are treated. Further, important areas such as risk management, group dynamics and project leadership is be discussed throughout a series of more practically oriented guest lectures.

Headings denoted with an asterisk ( * ) is retrieved from the course syllabus version Spring 2023

Content and learning outcomes

Course contents

The course focuses more on understanding and awareness of the problems associated with project management than on giving practical skills in a certain method for projects. Examples of different project models are, however, given by invited guest lecturers.
In the course, the following topics are covered: the project as work method, development , delivery and purchasing projects, the interaction between customer and supplier, overview and examples of project models, the different phases of a project, tender procedure, leadership, group dynamics, risk analysis, the project document (for example the opening for estimates, tender, contract, documentation of the project, project plan, final report and evaluation.

Intended learning outcomes

After the course, the participant should understand what a project manager does and how one works in an industrial project and be able to:

  • describe and apply the different phases in a project i.e. planning, follow-up and completion of a project
  • use methods and tools to plan and follow up projects taking into consideration time, cost and resources
  • give examples of how activities such as planning, project meetings, documentation and oral presentation should be carried out
  • based on a model for projects, create necessary documentation for a project
  • plan and carry out a risk analysis
  • analyse an industrial project, present results using oral and written communication

Learning activities

Learning activities Content Preparations
Grundläggande lektioner Provides the basic knowledge and theories of project management. The information needed to pass the assignments will be presented in the lectures.
Most of these lectures will be provided as videos you can watch whenever you want.
Read through the handbook
Gästföreläsningar Guests with different specialications and different backgrounds come and present their take on how to manage projects Come to the lecture on time if you are provided a slot or follow the streaming
Inlämningsuppgifter The assessment of the course, is where you test and document your knowledge.

You might need to resubmit your assignments
Read through the assignment specifications, watch relevant material and read the chapters in the handbook that you find relevant (it is a handbook, so you need to look for what you need)

Detailed plan

Learning activities Content Preparations
Basic lectures Provides the basic knowledge and theories of project management. The information needed to pass the assignments will be presented in the lectures.
Most of these lectures will be provided as videos you can watch whenever you want.
Read through the handbook
Guest lectures Guests with different specialications and different backgrounds come and present their take on how to manage projects Come to the lecture on time if you are provided a slot or follow the streaming
Assignments The assessment of the course, is where you test and document your knowledge.

You might need to resubmit your assignments
Read through the assignment specifications, watch relevant material and read the chapters in the handbook that you find relevant (it is a handbook, so you need to look for what you need)

Lectures

Please note that the lectures marked with "GUEST" is mandatory (80% attendance requriement).

Week

Time and place

Lectures

w35 2023-08-31 15.15 17.00 E1 Project planning -
Joakim Lilliesköld
w35 2023-09-01 15.15 17.00 F1 (Alfvénsalen) Management of risk -
Joakim Lilliesköld
w36 2023-09-04 15.15 17.00 B2 (GUEST)
Example of a project model - Anna Burack
w36 2023-09-05 15.15 17.00 M1 Project economy -
Elias Flening
w36 2023-09-08 08.15 10.00 F2 Project organization -
Elias Flening
w37 2023-09-11 08.15 10.00 F1 (Alfvénsalen) Feedback and group dynamics - Gabriel Montgommery
w37 2023-09-11 10.15 12.00 F1 (Alfvénsalen) Feedback and group dynamics - Gabriel Montgommery
w37 2023-09-14 08.15 10.00 D1 (GUEST)
Leadership in practise -
Peter Roos
w38 2023-09-20 13.15 15.00 F1 (Alfvénsalen) (GUEST)
Agile -
Henrik Kniberg
w38 2023-09-21 08.15 10.00 F2 Backup
w38 2023-09-22 10.15 12.00 D1 (GUEST)
Scrum and agile project planning - Martin Bäcklund
w39 2023-09-25 08.15 10.00 M1 (GUEST)
Project management from the inside -
Terence Acton
w39 2023-09-26 10.15 12.00 Q1 (GUEST)
Covid management at KTH
w39 2023-09-29 08.15 10.00 D1 (GUEST)
TBA
w40 2023-10-03 08.15 10.00 E1 Backup
w40 2023-10-06 10.15 12.00 Q1 (GUEST)
Agile Leadership -
Björn Sandberg
w41 2023-10-09 10.15 12.00 M1 (GUEST)
The secret key tosuccessful project management? -
Jon Fangel
w41 2023-10-11 08.15 10.00 E1 Summary & outlook -
Elias Flening

Preparations before course start

Literature

Eriksson & Lilliesköld: Handbok för mindre projekt/Handbook for small projects (Liber)

Examination and completion

Grading scale

A, B, C, D, E, FX, F

Examination

  • PRO1 - Project Task, 1.5 credits, Grading scale: P, F
  • PRO2 - Project Task, 1.5 credits, Grading scale: P, F
  • PRO3 - Project Task, 1.5 credits, Grading scale: P, F
  • PRO4 - Project Task, 0.7 credits, Grading scale: P, F
  • SEM1 - Seminars, 0.8 credits, Grading scale: P, F

Based on recommendation from KTH’s coordinator for disabilities, the examiner will decide how to adapt an examination for students with documented disability.

The examiner may apply another examination format when re-examining individual students.

The section below is not retrieved from the course syllabus:

Projektuppgift ( PRO1 )

Projektuppgift ( PRO2 )

Projektuppgift ( PRO3 )

Projektuppgift ( PRO4 )

Seminarium ( SEM1 )

Other requirements for final grade

Attendance on lectures 80%

Grading criteria/assessment criteria

The different submissions get graded with a number of course points, see Table 2 below. Some assignments can give either 3, 4 or 5 course points, whereas others are pass/fail only. To get more than three points, the assignment must be very well done when submitted the first time. This means that it should be clear that the authors have fully understood and mastered the important concepts and skills tested in that particular assignment in addition to having fulfilled the specific requirements. Both contents and form are important in this respect; i.e. no important contents or analysis should be missing, the structure and formatting should adhere to the relevant templates, and the text should be carefully proof-read.

Note that a higher grade can be rewarded for an assignment that is very well done, even if a re-submission is required due to some minor details. Whenever an assignment requires a re-submission to pass, the comments from the course staff will make it clear whether the final grade after re-submission is likely to be a pass or a pass with a higher grade. However, a higher grade is never guaranteed, but is completely determined by the quality of the final submission.

Table 2. Project phases with submission and grades.

Assignment

Submission

Course points

Assignment 1

Project plan

3-5 points

Status report 1

pass/fail (no points)

Status report 2

pass/fail (no points

Final report

3-5 points

Assignment 2

Project description

3-5 points

Oral presentation (optional)

3 points

Assignment 3

Risk analysis

3-5 points

Assignment 4

Reflection report

3-5 points

Peer review

3 points

Guest lecture attendance

 

3 points

A total number of 34 course points can be obtained in the course. The total sum determines the final grade, as follows:

 

Course points

Grade

21-23

E

24-26

D

27-29

C

30-32

B

33-34

A

 

Goal oriented grading

Mål Assignment  G VG
Beskriva och tillämpa de olika faserna i ett projekt, dvs. planera, följa upp och avsluta ett projekt Assignment 1 Project documents are created that fulfills the requirment of the assignment (following the project model) It is clear from the document in every step, what should be done, how the work is structure, what has been done, is there problem, what is the lessons learned
Använda metoder och verktyg för att planera och följa upp projekt med hänsyn till tid, kostnad och resurser Assignment 1  Project plan is creaeted that includes a WBS EVM is used in status report The status report is a tool not only used to report status but to make a forcast
Ge exempel på hur aktiviteter som planering, projektmöten, dokumentation och muntlig presentation skall genomföras Assignment 1 Assignment 2 & Assignment 4 Examples are given in the assignments Examples are analysed and there are suggestions on what works good and why and vice versa
Med utgångspunkt från en projektmodell skapa nödvändig projektdokumentation Assignment 1 & Assignment 3 Project documents are created that fulfills the requirment of the assignment (following the project model) There is a reflection on what was god and bad in the process 
Planera och genomföra en riskanalys Assignment 3 A risk analysis is performed and documented so it fulfills the requirment of the assignment There is a reflection on what was god and bad in the process and how the risk analysis could be improved. Actions to identified risks are both procative and reactive, and is not always the obvoius choise
Analysera ett industriellt projekt redovisa resultat genom muntlig och skriftlig kommunikation Assignment 2 An interview is performed and documented There is an analysis on the differences and similarities between what was done in the industial case you studied and what was taught in class

Ethical approach

  • All members of a group are responsible for the group's work.
  • In any assessment, every student shall honestly disclose any help received and sources used.
  • In an oral assessment, every student shall be able to present and answer questions about the entire assignment and solution.

The section below is not retrieved from the course syllabus:

Please note that when solving the project assignments co-operation between students is allowed and even encouraged. However, both project group members are responsible for the content of their own reports and any plagiarism will result in an immediate failing of the assignment in addition to a written report to KTH’s central disciplinary committee.

This means that all groups should write their own reports. You are not allowed to copy text from other students; you are not allowed to copy text from the internet. If you want to use a quote from a source, it must be clearly indicated that it is a quote.

The use of references is mandatory. When you use a fact from some source you should include a reference to this source.

NOTE!  The better the sources, the more accurate the facts, therefore please note that reports that use credible sources (as for instance peer-reviewed scientific papers) will receive higher grades than those that only rely on Wikipedia as a source.

Use references according to this or some similar standard but be consistent. For instance:

”Early assessment of system characteristics in software projects is one of the main concerns of the discipline of software architecture [1] [2] [3].”

List of references:

[1] Heineman, G., W. Councill (Eds), Component-based software engineering: Putting the pieces together, Addison-Wesley, 2001.

If the source is a web-page use the following standard.[name of page],[URL],[access date]

Wikipedia: Requirement, http://en.wikipedia.org/wiki/Requirements, 2015-08-26

General information on the assignments

The members of the course staff correct hundreds of assignments every week. In order to give you quick and relevant feedback on your work, the following rules apply:

  • Assignments are done in groups of two, with the exception of assignment 3. These groups must be formed and reported on lists available at the lectures before Assignment 1 is submitted! Note that the members of a group must aspire to the same grade.
  • A prerequisite for obtaining a higher grade than an E is that all assignments and re-submissions are submitted on time!
  • The assignments are submitted in the pdf format via the Canvas system. Pdf files can be created with the Adobe Acrobat software, which is not free-of-charge. There are, however, several services on the Internet which can be used free-of-charge to create pdf files.
  • Any reports suggesting mass duplication will be unconditionally failed, and no opportunity to complete the course will be offered
  • Build a single pdf for each assignment. Do not hand in any appendices separately if not explicitly specified. Either build the pdf from a single document containing everything, or merge separate pdf files into a single one using Adobe Acrobat or free software services available on the internet.
  • Please name your files after the following formate, where “XX” is your group number (two digits, 01, 02, 03, etc), “Y” is a number between 1 and 3 indicating whether it is the first, second or third submission of the assignment, and “assignment” is one of the following: projectplan/ statusreport/ finalreport/ projectdescription/ riskanalysis/ agilereport (EH2720) / reflection (EH2070) / peerreviewAll submissions should be in pdf format. 

Example: G06_2019_projectplan_2.pdf is group 6’s project plan, which after correction had to be submitted a second time.

  • Optional parts of an assignment will only be corrected twice, i.e. if you don´t perform the necessary corrections after the first submission the chance to get a higher grade will be lost.
  • Assignments submitted after the deadline will be corrected during the next re-exam period.
  • Any complaints about the corrections are to be submitted in writing to the course responsible or examiner.

 

 

Deadlines for assignments and presentations

Suggested dates for optional oral presentation of Assignment 2:

A doodle will be available on Canvas. Your time allocation is the hour you present - you stay and listen to all presentations. The oral presentations will take place during week 40.

Dates for peer review seminars in Assignment 4:

A doodle will be available on Canvas. The peer review seminars will take place during week 41. Please submit the written version of you peer review on Canvas no later than 7.00 p.m. the day before your peer review seminar. 

Submission deadlines

 

Week

Date

Submissions due

Corrections complete

Re-submissions due

Corrections of re-submissions complete

36

Fri

Sep 8

A1 Project plan
7.00 p.m.

 

 

 

37

Fri

Sep 15

 

A1 Project plan
7.00 p.m.

 

 

38

Mon

Sep 18

A1 Status report 1
7.00 p.m.

 

 

 

 

Fri

Sep 22

A3 Risk analysis
7.00 p.m.

A1 Status report 1
7.00 p.m.

A1 Project plan
7.00 p.m.

 

39

Wed

Sep 27

 

 

A1 Status report 1
7.00 p.m.

 

Fri

Sep 29

A2 Project description
7.00 p.m.

A3 Risk analysis
7.00 p.m.

 

A1 Project plan
7.00 p.m. 

40

Mon

Oct 2

A1 Status report 2

7.00 p.m.

 

 

A1 Status report 1
7.00 p.m.

Fri

Oct 6

A4 Agile report (EH2720)
/Reflection (EH2070)
7.00 p.m

 

A1 Status report 2
7.00 p.m.

A2 Project description
07.00 p.m.

A3 Risk analysis
7.00 p.m.

 

41

Wed

Oct 11

 

 

A1 Status report 2
7.00 p.m.

 

Fri

Oct 13

 

 

A2 Project description
7.00 p.m.

A1 Status report 2
7.00 p.m.

A3 Risk analysis
7.00 p.m.

42

Mon

Oct 16

A1 Final report
7.00 p.m.

 

 

 

Wed

Oct 18

 

 

 

A2 Project description
7.00 p.m.

Fri

Oct 20

 

A1 Final report
7.00 p.m.

A4 Agile report
7.00 p.m.

 

43

Wed

Oct 25

 

 

A1 Final report
7.00 p.m.

A4 Agile report  
7.00 p.m.

Fri

Oct 27

 

 

 

A1 Final report
7.00 p.m.

Further information

Kursadministration (in english)

  • The course administration and communication are handled on Canvas, the learning management system, reached via https://kth.instructure.com (NB: we are not using KTH Social): Canvas is used for:
  • Signing up in groups
  • Posting questions to the course administration
  • Communicating with other course participants
  • Reading and accessing instructions and other material needed for the assignments
  • Submission and re-submission of assignments
  • Obtaining corrected assignments and comments, and lists of results
  • Booking time slots for seminars
  • The course leaders are located at Teknikringen 33, ground floor (NSE department).
  • Attendance will be registered on one or more lists that are passed around during the guest lectures. Approved attendance of a minimum of 80% of guest lectures (marked GUEST in the lecture schedule) yields 0.8 ECTS credits, which means that the attendance requirement is a grading factor. Therefore, cheating with the attendance list is equivalent to cheating on an exam. You are required to inform the course staff if you have to leave a lecture. Show respect to our guest lecturers by being on time to the lectures!

Round Facts

Start date

28 Aug 2023

Course offering

  • Autumn 2023-52107

Language Of Instruction

English

Offered By

EECS/Computer Science

Contacts

Communication during course

All kommunikation sker genom Canvas med kursens lärare.

För snabbare svar är det bra om frågorna ställs på engelska.

Course Coordinator

Teachers

Examiner