T-76.4115/5115Customer InfoAalto UniversitySchool of Science and Technology

Agenda

• 16:15 – 16:55 Info for the customers

• 16:55 – 17:00 Break

• 17:00 – 19:00 Topic presentations by customers

• 19:00 – 19:45 Free discussion between customers and students

9/14/20102

Jari Vanhanen

Educational Goal for the Students

• To provide a realistic context where the students can try in practice common SE methods and tools that have been taught in theory on other courses.

Allow and encourage the students spend enough effort for the

educational aspects of the project too.

9/14/20103

Jari Vanhanen

Project Stakeholders - Responsibilities

• Customer representatives– provide the topic and problem description/requirements for the system

– often can also help with technical issues

– take the responsibility of the system after the project

• Project group– ~9 students

– develop the system

• Mentor– course personnel

– observes and helps the group with the working methods

9/14/20104

Jari Vanhanen

Course Personnel’s Support for the Project Groups• SW development process framework• Mentoring

– helping with the SE work methods– evaluation and feedback

• Experience exchange sessions– peer support from other groups– tips from industry representatives (Accenture) and teachers

• Infrastructure– some hardware & software

9/14/20105

Jari Vanhanen

Software Process – Framework

• A basis to decide the group’s work methods quickly– a group has not worked together previously

– physically and temporarily distributed setting

• Enforces certain work practices and documents– some educational exercises (that also contribute to the project)

– some crucial activities & tools for this context– lower probability of total failures (vs. maximizing output)

• only successful projects rather than 13 very successful and 2 failed– standardized projects

• more visibility, better control and easier evaluation

• Allows lots of freedom (and responsibility) for customization

9/14/20106

Jari Vanhanen

design; 8

documenting; 17

infrastructure; 4

meetings; 17programming; 32

proj. management; 8

studying; 8

testing; 6

Software Process – Project Control Variables• Effort fixed

– 5-8 cr/person * 27h/cr = 135-216h/person• project preparation (~15h) • project work• educational exercises

• Calendar time fixed– project end date and major control points such as iteration demos

• Quality ”fixed”– high quality recommended, but customer may explicitly state if certain

quality aspects are not important (e.g. in prototype projects)

• Scope flexible– tuned based on the group’s size, skills and domain knowledge

9/14/20107

Jari Vanhanen

Software Process – Iterations

9/14/20108

Jari Vanhanen

Software Process – Iteration Planning

• Group and customer plan each iteration’s goals and deliverables – goals are higher level ideas of what is expected from the iteration– deliverables include software units and documents to be created/updated

• Customer selects and prioritizes iteration’s content based on– business importance– group’s effort allocation for the iteration– group’s rough effort estimates for implementing sw units – group’s estimates about architectural impact

• Group concretizes goals and deliverables into required tasks – re-planning, if task effort estimates and allocated resources differ largely

9/14/20109

Jari Vanhanen

Iteration planning meeting

Software Process – Iteration Demo

• Arranged in the end of each iteration– exact times (8:00-19:00) published several weeks before demos

• tell impossible dates/times to the teacher immediately

– at SoberIT (Innopoli 2, 4th floor, Tekniikantie 14)

• Participants– customer, student group, mentor, teacher– a consultant from Accenture (quality award)

• Group presents project status and iteration’s results including sw demo

• Customer evaluates the work performed– private discussion about the given points with the mentor after the demo– prepare in advance and comment evaluation to the group

Tip! Arrange the next iteration planning meeting

right after the iteration demo.

9/14/201010

Jari Vanhanen

Software Process – Controlling the Projects• Arrange regular meetings

– especially early in the project

• Demand some regular, low overhead reporting

• Ask to arrange access to project materials

– version control system, defect tracking tool etc.

• Check the intermediate results, including the code

• Give concrete feedback early

9/14/2010Jari Vanhanen

11

Software Process – Project Management

9/14/201012

Jari Vanhanen

Software Process – Requirements Engineering

9/14/201013

Jari Vanhanen

Software Process – Design and Implementation

9/14/201014

Jari Vanhanen

Software Process – Quality Assurance

9/14/201015

Jari Vanhanen

Software Process – Required Documentation• Project plan

– including description of work practices and QA plan

• Requirements document • Technical specification* • User’s manual*• Progress reports (a slide set for the iteration demos)• Final report

• Course provides some document templates– their use is mandatory, but irrelevant topics can be omitted

*the course sets no requirements on the content or format of these two documents

9/14/201016

Jari Vanhanen

Infrastructure

• Hardware– several computer classes at TKK

• Software– Microsoft MSDN AA

• licenses for students’ own computers

– Magic Draw Personal Edition UML tool• licenses for students’ own computers

– TKK wiki, CVS, subversion, …

Customer must provide other necessary hardware/software: e.g. server computers, phones for testing, …

9/14/201017

Jari Vanhanen

Evaluation – General

• Customer evaluates– intermediate and final results, and slightly also working methods– mentor ensures the objectivity of the evaluations

• realistic expectations

• Mentor evaluates working methods

• Group members evaluate personal contribution of the other group members

9/14/201018

Jari Vanhanen

Evaluation – Iterations (Customer)

9/14/201019

Jari Vanhanen

Evaluation – Project Results (customer)

• Compare to the original/updated project goals

9/14/2010Jari Vanhanen

20

Customer Satisfaction (2004-05)

9/14/201021

Jari Vanhanen

Project Topics – Legal Issues

• Intellectual property rights (IPR) – open source, or

– customer gets IPRs

• Non-disclosure agreement (NDA)– must have been mentioned in the topic

proposal

• Contracts prepared by Aalto lawyers– customers signs a contract with Aalto

– Aalto signs a similar contract with students

– students cannot be forced to sign any additional contracts

• Project documentation is published on the web at least in the end iterations

– if NDA required customer must review documents before publication

– code and technical specs can remain unpublished

• Participation fee– external: 3000e + VAT

– Aalto: 1500e

– Aalto/T-dep: 0e

– invoices sent in November

http://www.soberit.hut.fi/T-76.4115/10-11/instructions/contracts/TKK-yritys.pdf

Send two signed originals to Jari Vanhanen, PL 19210, 00076 Aalto(DL 20.10.)

9/14/201022

Jari Vanhanen

Project Topics – Selection Process

• Students have formed 14 groups– 3 SE experts + max. 3 developers

– teacher adds 3-4 developers 17.9.

• A group contacts 2-4 customers

• Groups appreciate– customer’s commitment to the project

– customer’s domain understanding

– customer’s appreciation towards the educational goals

– provided infrastructure

– provided technical guidance

– realistic description of the expected skills from the group

• Customer can choose any of the interested groups

– …if they are still available

• If you get a group– e-mail to Jari and he removes your

topic from the list

• If you don’t get any serious contacts– e-mail to Jari and he highlights your

topic on the list

9/14/201023

Jari Vanhanen

Topic Presentations

• 17:00 -19:00 presentations every 5 min– if the presentation lasts < 5 min students can ask questions– next customer to the stage while questions are answered

• 19:00 – 19:30– customers should discuss with all groups that show interest to

their topic before making their final decision

• After 19:30– customer-group pairings may be fixed if both parties are already

sure about their decision• pairings registered by sending e-mail to the teacher

9/14/201024

Jari Vanhanen

Topics

9/14/201025

Jari Vanhanen

Announcements to Students

• Groups are allowed to recruite 7th member by Fr 13:00– several late registrations added to the student list

• Final group size will be 9-10 persons

• Remaining developers may send their preferences on groups they would like to join to t764115##soberit.hut.fi– deadline next Friday 13:00

• most of the group-customer pairs are fixed by Friday morning

– Subject: “T-76.4115 prefs: g6, g3, g2, g14, …”

9/14/2010Jari Vanhanen

26