Project startup slides - IDT

DVA313 – Software Engineering 2: Project Teamwork
Project j start
Jan Carlson
Mälardalen University
School of Innovation, Design and Engineering
jan.carlson@mdh.se
Project setup
Provide idea
Discuss results
Customer Steering group
Initiate meetings
Deliver results
Report status
Project manager
SVN manager
Project group
Discuss progress
Provide feedback
Deal with serious problems
Grade project
Customer
contacts
DVA312 – Software Engineering 3
Responsibilities of the Steering group
● Steering group responsibilities:
● Dealing with serious problems in the project group
● Discuss the progress of the project
● Give feedback on artifacts
● Approve (and grade) the project work
● Not part of responsibilities:
● Identify problems in the project group
● Make the project approvable
● Prevent bad decisions
DVA312 – Software Engineering
Juraj Feljan
…
Jan Carlson
Andreas Johnsen
5
DVA313 basics
● Apply theory from previous courses in a real/realistic project
● Relatively large project groups (7-8 students)
● External customers (from industry or MDH)
● Examination only consists of the project work
● Development
● Documentation
● Presentations
DVA312 – Software Engineering
Responsibilities of the Customer
● Customer responsibilities:
● Have product ideas
● Have (some) time to discuss the ideas
● Give feedback to the group (on issues of interest to the customer)
● In some cases, technical expertise
● Not part of responsibilities:
● Initiate meetings
● Limit the project
● Always be available
DVA312 – Software Engineering
Page 1
Responsibilities of the Project manager
● Project manager responsibilities:
● Lead the work of the project group
● Keep an eye on the communication within the group
● Be up-to-date on project progress
● Not included l d d in the h responsibilities: b l
● Do all the work, or work harder than the rest of the group
● Always remind people about their responsibilities
DVA312 – Software Engineering
2
4
6

Additional roles in the project group
● Good to define responsible for example for:
● Configuration management (SVN / Git)
● Customer contact
● Particular technologies or languages
● User experience, document templates, requirements, testing, …
● These can (should) start with their respective tasks early!
● Study tools, survey literature, gather ideas, prepare documents, etc.
DVA312 – Software Engineering
Meeting and presentations
● Each phase ends with a presentation
● Mandatory to attend the presentations of all groups
● Each student must present once during the course
● Project plan and requirements (Nov 28)
● Preliminary design and implementation (Dec 12)
● Final presentation (Jan 9)
● Weekly status report meetings with the steering group
● Mandatory to attend all meetings of your group
● Project status and problems encountered
● Activities during the previous week and plans for the coming week
● Customer meetings and internal group meetings
DVA312 – Software Engineering
Design
● Your responsibility
IImplementation l t ti
Deliverable
Presentation
Project Timeplan
Project Planning
Test
Requirements
Project wrap-up
W46 W47 W48 W49 W50 W51 W52 W01 W02
DVA312 – Software Engineering 11
7
9
Page 2
Process overview – project phases
1. Planning and requirements capturing
● Decide on forms for the group work and assign responsibilities
● Meet customer, capture and formulate requirements
22. Design and implementation
● Early minimal (working) version of the software
● Rapid iterations
3. Test and delivery
● Define and perform acceptance tests
DVA312 – Software Engineering
Deliverables
● The work should result in a number of deliverables:
● Weekly reports (every week)
● Project description and plan (w47)
● Requirement specification (initial version W47, final version w51)
● Design documentation (initial version w49, final version w02)
● Product d (i (initial i i l version i w49, fi final l version i w02) )
● Test specification (w51)
● Test report (w02)
● Final project report (w02)
● All deliverables should be available to the steering group latest
Thursday at midnight in the respective week (possibly earlier for w02).
DVA312 – Software Engineering
Passing the course
● Active participation in the project work!
● 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.
● Passed project
● Deliverables approved and deadlines met
DVA312 – Software Engineering
8
10
12

Grading
● Project grade calculated from:
● Project work (as perceived by customer and steering group)
● Technical documentation
● Final product (as perceived by customer and steering group)
● Presentations
● Individual grade:
● Based on project grade
● Work distribution can influence the individual grade
DVA312 – Software Engineering
Dirty Tricks…
● More dirty tricks:
● Ban overtime (restrict number of working hours)
● Give additional tasks to disrupt the schedule
● Change the deadlines
● Introduce quality inspections
● Change the teams
● Really dirty:
● Upgrade the software during the course
● Occasionally crash the hardware
● Slow down the software
● Disrupt the file storage
● When students complain, say “I told you so”!
DVA312 – Software Engineering
Project group 1
Photovoltaic solar-powered water pump system
Client: Hailong Li, HST, MDH (hailong.li#mdh.se)
Steering group: Andreas Johnsen, Jan Carlson
● Daniel i lJensen Samuelsson l
● Gonzalo Laso Ferrer
● Pedro Martínez Roig
● Thomas Åkerlund
● Axel Embretsen
● Dimitar Minovski
● Oskar Palmgren
● Viktor Nikolovski
DVA312 – Software Engineering
13
15
17
Dirty Tricks...
Page 3
● From the instructions to 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:
● Give inadequate specifications
● Make sure all assumptions are wrong
● Present an uncertain and naive customer
● Customers with conflicting ideas
● …
DVA312 – Software Engineering
Project group allocations
● Project 1: Photovoltaic solar-powered water pump system
● Project 2: Tool for calculations in the construction business
● Project 3: XC-SkiLab – Coach tool: Motion-data and Video
synchronized
● Project 4: A digital Project Office Tool
● All students assigned to a project they ranked 1, 2 or 3
● Average score for assigned project: 1.7
DVA312 – Software Engineering
Project group 2
Tool for calculations in the construction business
Client: Peter Valfridsson, Byggwalle AB (peter#byggwalle.se)
Steering group: Juraj Feljan, Jan Carlson
● Miraldi Fifo
● Dzana Kujan
● Ditmar Parmeza
● Filip Andersson
● Simon Yildiz
● Rafael Armesilla Sánchez
● Anders Pantzar
DVA312 – Software Engineering
14
16
18

Project group 3
XC-SkiLab – Coach tool: Motion-data and Video synchronized
Client: Magnus Jonsson, Internet of sports, SICS (magnus#tii.se)
Steering group: Juraj Feljan, Jan Carlson
● David Reypka
● Robin Cocks
● Joakim Lindborg
● Ayan Azmat
● Kostopoulos Dimitrios Symeon
● Karl Arvidsson
● Emil Gerebo
● Abed Hassan Ali
DVA312 – Software Engineering
First follow-up meeting on
Wednesday (Nov 14)
● Tasks to do before the meeting:
●Group meeting(s)
● Get to know the group, individual backgrounds, skills and ambition
levels
●Select project manager
●Contact customer, , schedule meetingg
●Prepare a small presentation of the group and the work so far
● Schedule:
DVA312 – Software Engineering
09:15 – 09:45 Group 2
09:50 – 10:20 Group 3
10:25 – 10:55 Group 4
11:00 – 11:30 Group 1
19
21
Project group 4
A digital Project Office Tool
Page 4
Client: Peter Ohlman, Tritech Technology AB (peter.ohlman#tritech.se)
Steering group: Andreas Johnsen, Jan Carlson
● Niklas Johansson
● Andreas Lundqvist
● Egidi Sara
● Nikola Radisavljevic
● Tomas Agirman
● Bal Krishna Nyaupane
● Antonio Corrales Gámiz
DVA312 – Software Engineering
20