project&start=up - mälardalen university sweden · jonathan larsson sebastian lindgren avalika...

DVA313 – Software Engineering 2: Project Teamwork

Project start-upJan CarlsonMälardalen UniversitySchool of Innovation, Design and [email protected]


DVA313 basics

● Apply theory from previous courses in a real/realistic project

● Relatively large project groups (6-8 students)

● External clients (from industry or MDH)

● Examination consists only of project work● Planning and running the project● Software development● Documentation● Meetings and presentations

2


Previous course evaluations

● Course evaluations from 2010 – 2015 available from the course page

● Some comments from previous course evaluations:● Great experience to work in large group and with real clients ● Not enough teaching from the teachers● Uneven groups and difficulties to assess individual students

● Changes since last year● Tool for managing planned and finished activities● New routines for weekly meetings ● Much better students…right?

3


Outline

● Roles and responsibilities

● Presentations, deliverables and timeplan

● Grading criteria

● Group allocations

4


Project group

…

Project setup

5

Client Steering group

Provide ideaDiscuss results

Initiate meetingsDeliverables

Report statusDeliverables

…Project

manager

Discuss progressProvide feedbackHandle serious problemsGrade project

Clientcontact


Responsibilities of the group

● Group responsibilities:● Plan and carry out the work● Communicate with the client● Identify problems and decide how to handle them

● Missing knowledge or skills● Unbalanced work distribution● Deviation from the plan

● Project manager responsibilities:● Be up-to-date on project progress● Keep an eye on the communication within the group● Be the main contact point towards the steering group

● Not included in the project manager responsibilities:● Do more of the work, or work harder than the rest of the group● Constantly remind people of their responsibilities

6


Additional roles in the project group

● Good to define responsible for example for:● Client contact● Configuration management (SVN / Git)● Document templates● Particular technologies or languages● Individual project deliverables

● These can (should) start with their respective tasks early!● Study tools, survey literature, gather ideas, prepare documents, etc.

7


Responsibilities of the Client

● Client responsibilities:● Have product ideas● Have (some) time to discuss the ideas● Give feedback to the group (on issues of interest to the client)● In some cases, technical expertise

● Not part of responsibilities:● Initiate or drive the meetings● Limit the project● Always be available

8


Responsibilities of the Steering group

● Steering group responsibilities:● Discuss the progress of the project● Give feedback on deliverables● Deal with serious problems in the project group● Approve (and grade) the project work

● Not part of responsibilities:● Identify problems in the project group● Make the project approvable● Prevent bad decisions

Juraj Feljan

Jan Carlson

9


Process overview – project phases

1. Planning and initial requirements (~2 weeks) ● Decide on forms for the group work and assign responsibilities● Meet customer, capture and formulate requirements

2. Design and implementation (~4 weeks)● Early minimal (working) version of the software● Rapid iterations

3. Delivery and project wrap-up (~1 week)● Define and perform acceptance tests● Deliver product to client● Summarize the project work

10


Presentations and meetings

● Each phase includes a presentation● Mandatory to attend the presentations of all groups● Each student must present once during the course

● Project plan and requirements (Nov 23)● Preliminary design and implementation (Dec 7)● Final presentation (Jan 11)

● Weekly status report meetings with the steering group● Mandatory to attend all meetings of your group● Present project status and problems encountered

● Activities during the previous week and plans for the coming week

● Customer meetings and internal group meetings● Your responsibility

11


Deliverables

● The work should result in a number of deliverables:● Project plan (Nov 17)● Design documentation (First version Dec 1, final version Jan 12)● Product (First version Dec 1, final version Jan 12)● Project report (Jan 12)

12


Project Timeplan

13

W1 W2 W3 W4 W5 W6 W7 W9

Design

Implementation

Project planning &Initial requirements

Project wrap-up

Deliverable

Presentation

W8

Nov 7 Jan 9Nov21 Dec 5 Dec 19


Passing the course

● Passed project●Deliverables approved and deadlines met

●Mandatory attendance● Attended all weekly meetings● Attended all three project presentation occasions – presenting once● If you have valid reason to be absent, contact steering group and

your project manager in advance or as soon as possible.

●Active participation in the project work!● Active participation in meetings and presentations

(both scheduled, internal and client meetings)● Contribution to both documentation and design/implementation

14


Grading

● Project grade calculated from:● Project work (as perceived by the client and the steering group)● Final product (as perceived by the client and the steering group)● Documentation● Presentations

● Individual grade:● Based on project grade● Work distribution can influence the individual grade

15


● From a SE project course at Loughborough University, UK

(Published paper by Ray Dawson: “Twenty dirty tricks to train software engineers”, at 2nd International Conference on Software Engineering, 2000)

● Dirty tricks:● Uncertain and naive customers with conflicting ideas● Ban overtime (restrict number of working hours)● Give additional tasks to disrupt the schedule (e.g. quality inspections)● Change the deadlines or change the teams● Upgrade software or disrupt the file storage during the course● Occasionally crash the hardware ● When students complain, say “I told you so”!

Dirty Tricks...

16


Project group allocations

● Projects● Project 1: CoPilot driver statistics (Volvo Construction Equipment)● Project 2: Solar energy calculator (Future Energy Center, MDH)● Project 3: Project management tool (Robotdalen)● Project 4: Radar visualization (Maximatecc)● Project 5: Room allocation planner (IDT/MDH)

● All students assigned to a project they ranked 1 or 2

17


Project 1: CoPilot driver statistics

● Project group● Léa Brunschwig● Leslie Dahlberg● Vladimir Djukanovic● Eric Engtorp● Fredrik Frenning● Pooria Ghavamian● Hamza Sabljakovic

● Client● Patrik Wahlström, Volvo CE <patrik.wahlstrom#volvo.com>

● First steering group meeting● Wed Nov 9, 9:15 – 9:40

18


Project 2: Solar energy calculator

● Project group● Lukas Hamacek● Aliya Hussain● Charlie Höglund● Jonathan Larsson● Sebastian Lindgren● Avalika Podduturu Reddy

● Client● Bengt Stridh, Future Energy Center, MDH <bengt.stridh#mdh.se>


19


Project 3: Project management tool

● Project group● Nicklas Brindstedt● Filip Lagerholm● Luis Martin de la Rubia● Milos Ojdanic● Javier Ramos Segui● Elisa Sobaler Cuerno

● Client● Erik Hellström, Robotdalen <erik.hellstrom#robotdalen.se>


20


Project 4: Radar visualization

● Project group● Filiph Eriksson-Falk● Martin Erkers● Carl Larsson● Erik Liljeqvist● Kari Päivärinne● Henrik Runge

● Client● Ken Lindfors, Maximatecc <ken.lindfors#maximatecc.com>


21


Project 5: Room allocation planner

● Project group● Mohamed Ahmed● Luis Baquera● Robin Chef● Robin Eriksson● Milos Jovovic● Sebastian Lindfors● Andrei Radulescu

● Client● Susanne Fronnå, IDT, MDH <susanne.fronna#mdh.se>


22


To do before the first weekly meeting on Wednesday (Nov 9)

● Internal group meeting(s)● Get to know the group, individual backgrounds, skills and ambition levels● Select project manager (and other roles)

● Contact customer, arrange initial meeting

● Prepare a small presentation of the group and the work so far● A projector will be available● See course page for details

● Prepare questions in case something is unclear

● Keep an eye on the course homepage for news:www.idt.mdh.se/kurser/dva313/16/

● Take a group photo for the projects page

23

project&start=up - mälardalen university sweden · jonathan larsson sebastian lindgren avalika...

Documents