Hoppa till huvudinnehållet

EH2070 Projektstyrning och verksamhetsutveckling 6.0 hp

Kurs-PM HT 2022-52089

Version 1 – 2022-08-29 15:12:14

Kursomgång

HT 2022-1 (Startdatum 2022-08-29, Svenska)

Undervisningsspråk

Svenska

Kursen ges av

EECS/Datavetenskap

Kurs-PM HT 2022

Presentation av kursen

Idag sker utveckling, leverans och upphandling av komplexa tekniska system normalt i projektform. Projekt genomförs i tillfälligt sammansatta organisationer med personal från olika delar av en organisation som samarbetar för att uppnå ett väldefinierat mål. För att ett projekt skall fungera krävs effektiva rutiner och metoder för planering, styrning och uppföljning samt dokumentation under ett projekts olika faser. Detta för att uppnå ställda tekniska krav på projektet inom givna tids- och kostnadsramar. Ett komplext tekniskt system är en anläggning eller en produkt där program- och maskinvara tillsammans utgör det färdiga systemet.

Kursen har som syfte att ge en mångsidig insikt i hanteringen av industriella projekt. I kursen kombineras verklighetsanknutna inlämningsuppgifter och gästföreläsningar med teoretiska studier. I de teoretiska avsnitten behandlas färdigheter i projektstyrning såsom planering, dokumentering och uppföljning av projekt. Dessutom behandlas viktiga områden som kvalitet, riskhantering samt ekonomistyrning. Föreläsningsserien har tonvikt på projektledarrollen och ledarskapets betydelse i projekt.

Rubriker markerade med en asterisk ( * ) kommer från kursplan version VT 2019

Innehåll och lärandemål

Kursinnehåll

Kursen fokuserar mer på att ge förståelse för problemställningarna förknippade med projektstyrning än på att ge praktisk färdighet i någon projektmetod. Exempel på olika projektmodeller ges dock av inbjudna gästföreläsare.
I kursen behandlas följande moment: projektet som arbetsform, utvecklings-, leverans- och upphandlingsprojekt, samspelet mellan kund och leverantör, genomgång och exempel på projektmodeller, ett projekts olika faser, anbudsförfarande, ledarskap, gruppdynamik, riskanalys, projektdokument (t.ex. offertförfrågan, anbud, kontrakt, projekthandbok, projektplan/startrapport, progressrapport), projektavslut och utvärdering samt kvalitetsstandarder.

Lärandemål

Efter kursen skall deltagaren förstå vad en projektledare gör och hur man arbetar i ett industriellt projekt genom att kunna:

  • beskriva och tillämpa de olika faserna i ett projekt, dvs. planera, följa upp och avsluta ett projekt
  • använda metoder och verktyg för att planera och följa upp projekt med hänsyn till tid, kostnad och resurser
  • ge exempel på hur aktiviteter som planering, projektmöten, dokumentation och muntlig presentation skall genomföras
  • med utgångspunkt från en projektmodell skapa nödvändig projektdokumentation
  • planera och genomföra en riskanalys
  • analysera ett industriellt projekt redovisa resultat genom muntlig och skriftlig kommunikation

Läraktiviteter

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)

Detaljplanering

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

v 35

Wednesday

30-aug

10-12.

F1 (Alfvénsalen)

Introduction to project management (Liv Gingnell, KTH)

v 35

Thursday

01-sep

13-15

F1 (Alfvénsalen)

Project planning (Liv Gingnell, KTH)

v 36

Tuesday

06-sep

13-15

E1

Management of risk (Joakim Lilliesköld, KTH)

v 36

Thursday

08-sep

15-17

D1

Anna Burack (GUEST): example of a project model

v 36

Friday

09-sep

13-15

E1

Ermal Hetemi (GUEST): project organization

v 37

Monday

12-sep

13-15

On zoom

Project economy (Liv Gingnell, KTH)

v 37

Wednesday

14-sep

15-17

F2

Henrik Kniberg (GUEST): Agile project management

v 38

Thursday

22-sep

15-17

E1

Feedback and group dynamics (Liv Gingnell, KTH)

v 38

Friday

23-sep

10-12.

D1

Martin Bäcklund (GUEST): Scrum and agile project planning

v 39

Thursday

29-sep

10-12.

F2

Jon Fangel (GUEST)

v 39

Friday

30-sep

10-12.

E1

Backup

v 40

Tuesday

04-okt

10-12.

E1

Peter Roos (GUEST): Leadership

v 40

Thursday

06-okt

13-15

E1

Backup

v 40

Friday

07-okt

10-12.

E1

GUEST: How KTH handled the covid pandemic

v 41

Monday

10-okt

10-12.

C

Björn Sandberg (GUEST): Leadership

v 41

Thursday

14-okt

15-17

E1

Summary & outlook (KTH)

Förberedelser inför kursstart

Kurslitteratur

Ingen information tillagd

Examination och slutförande

Betygsskala

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

Examination

  • PRO1 - Projektuppgift, 1,5 hp, Betygsskala: P, F
  • PRO2 - Projektuppgift, 1,5 hp, Betygsskala: P, F
  • PRO3 - Projektuppgift, 1,5 hp, Betygsskala: P, F
  • PRO4 - Projektuppgift, 0,7 hp, Betygsskala: P, F
  • SEM1 - Seminarium, 0,8 hp, Betygsskala: P, F

Examinator beslutar, baserat på rekommendation från KTH:s samordnare för funktionsnedsättning, om eventuell anpassad examination för studenter med dokumenterad, varaktig funktionsnedsättning.

Examinator får medge annan examinationsform vid omexamination av enstaka studenter.

Avsnittet nedan kommer inte från kursplanen:

Projektuppgift ( PRO1 )

Projektuppgift ( PRO2 )

Projektuppgift ( PRO3 )

Projektuppgift ( PRO4 )

Seminarium ( SEM1 )

Övriga krav för slutbetyg

80 % Närvaro på föreläsningar (SEM1; 0,8 p).

Fem inlämningsuppgifter (PRO1: 1,5p + PRO2: 1,5p + PRO3: 1,5 p + PRO4: 1,5 p + PRO: 5 2,2p).

Målrelaterade betygskriterier/bedömningskriterier

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

Etiskt förhållningssätt

  • Vid grupparbete har alla i gruppen ansvar för gruppens arbete.
  • Vid examination ska varje student ärligt redovisa hjälp som erhållits och källor som använts.
  • Vid muntlig examination ska varje student kunna redogöra för hela uppgiften och hela lösningen.

Avsnittet nedan kommer inte från kursplanen:

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.
  • You must name your assignment by the following convention: pdf, 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) / peerreview.

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. The presentations will take place during week 39. 

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 23.59 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 9

A1 Project plan

11.59 p.m.

 

 

 

37

Fri

Sep 16

 

A1 Project plan

11.59 p.m.

 

 

38

Mon

Sep 19

A1 Status report 1

11.59 p.m.

 

 

 

Sep 21

 

 

A1 Project plan

11.59 p.m.

 

Fri

Sep 23

A2 Project description

11.59 p.m.

A1 Status report 1

11.59 p.m.

 

 

39

Wed

Sep 28

 

 

A1 Status report 1

11.59 p.m.

A1 Project plan

11.59 p.m.

Fri

Sep 30

A3 Risk analysis

11.59 p.m.

A2 Project description

11.59 p.m.

 

A1 Status report 1

11.59 p.m.

40

Mon

Oct 3

A1 Status report 2

11.59 p.m.

 

 

 

Wed

Oct 5

A4 Reflection

11.59 p.m.

 

 

 

Fri

Oct 7

 

A1 Status report 2

11.59 p.m.
A3 Risk analysis

11.59 p.m.

A2 Project description

11.59 p.m.

 

41

Wed

Oct 12

 

 

A1 Status report 2

11.59 p.m.

 

Fri

Oct 14

 

 

A3 Risk analysis

11.59 p.m.

A1 Status report 2

11.59 p.m.
A2 Project description

11.59 p.m.

42

Mon

Oct 17

A1 Final report

23.59 p.m.

 

 

 

Wed

Oct 19

 

 

 

A3 Risk analysis

11.59 p.m.

Fri

Oct 21

 

A1 Final report

A4 Reflection

11.59 p.m.

 

43

Wed

Oct 26

 

 

A1 Final report

23.59 p.m.

A4 Reflection
23.59 p.m.

Fri

Oct 28

 

 

 

A1 Final report

Ytterligare 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 6 guest lectures 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!

Kommunikation i kursen

Kursansvarig

Lärare

Examinator

Fakta om kursomgång

Startdatum

Obligatoriskt innehåll saknas

Kursomgång

  • HT 2022-52089

Undervisningsspråk

Svenska

Kursen ges av

EECS/Datavetenskap

Kontakter

Kommunikation i kursen

All kommunikation sker genom Canvas med kursens lärare.

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

Kursansvarig

Lärare

Examinator