1. 1SEP Software / Web Engineering Projects 2IPE0 Spring 2016 http://wwwis.win.tue.nl/2IPE0/ Lou Somers

2. 2SEP Today: kick-off n General information about the way of working n Coupling of groups to cases n Start of projects… n Customers will give more details about their case to each group

3. 3SEP General information n A real project n A real customer n A team consists of 8-10 students n Separate project and quality manager (students 2IMP15) n Each team has a CS staff member as supervisor n Timing n Available time: 10 Ects  280 hours per person n Start: April 18, 2016 n End: July 1, 2016 (hard deadline) n Marking n General mark for group n Individual adjustment (peer reviews by group, managers, supervisor)

4. 4SEP Main players n Senior management – global organization n Lou Somers n Study counselors – admission, portfolio assignments, poster printing n Roel Bloo, Yves Houben (posters) n BCF – project ICT facilities n Joe Joe Wong n Student administration – project room facilities n Elle van den Hurk n Supervisors – coaching, supervision on projects, marking n Ion Barosan n Kees Huizing n Serguei Roubtsov (2x) n Erik Scheffers n Tom Verhoeff n Anton Wijs n Nicola Zannone n Customers – external clients with an assignment n Project and quality managers – steering a project n You

5. 5SEP Project organization n Each group has a project room (some shared) n Must be kept clean ! n Key codes will be arranged in the first week

6. 6SEP Documentation n According to the ESA standard n 6 product documents n URD: User Requirements Document n SRD: Software Requirements Document n ADD: Architectural Design Document n DDD: Detailed Design Document n SUM: Software User Manual n STD: Software Transfer Document n 3 test plans: UTP, ITP, ATP n All documents delivered to customer + senior management n ESA standard is guideline n Project documents (SVVP,SCMP,SQAP) not needed n Omit non applicable sections n Examples of documents from previous years are available n See also the SEP marking form for more details about the required contents of each document.

7. 7SEP Project planning

8. 8SEP Sprint planning

9. 9SEP Scrum

10. 10SEP Standup meetings n Each team member must be present at every standup meeting n One exception: last two weeks during examination period n Missing two meetings will have as a consequence that the student receives an official warning (“yellow card”) n After the third missed meeting the student is excluded from the project and cannot pass anymore n The project manager keeps track of presence

11. 11SEP Assessment / marking n Necessary conditions for passing the project: n All professional skills assignments are completed n One has not been excluded from the project, e.g. because of free- riding, or missing three scrum meetings n The mark is calculated as follows: 1)Documents and code delivered by each group are marked using the SEP marking form (see website) n A copy of this form will be filled in by at least 2 staff members n Code quality is checked by tooling n The results will form the main (average) mark for the group 2)The individual contribution of each student is judged based on the peer reviews, held twice during the project. Filled by: n The students of the group n The project manager and quality manager n The supervisor n The mark for each student is the result from (1) with a correction [-1,+1] from (2)

12. 12SEP Peer reviews n Halfway and at the end of the project n Use a standard peer evaluation form n Available at website n At the start of the project: n The group defines the characteristics of a “reliable team member” n Discuss the notion of “contribution”, “commitment” (inzet) and “reliability” to obtain a common understanding n These characteristics should be added to the review form

13. 13SEP Other project procedures n Review of documents n Attention points from checklists n Customer involved in: n URD, SRD, SUM, and Acceptance Test review n Approval signature needed of supervisor and customer n Reporting: time metrics (weekly) n Every project member keeps track of time spent n Exception: project manager and quality manager n Time spent and planned for each back log item n Some standard items (documentation writing,...) n All user stories as separate item (white index cards in “Scrum and XP from the Trenches”) n Collected by project manager n Ready every Monday, then sent to senior management

14. 14SEP Time metrics (each week)

15. 15SEP Management roles and tasks n Project manager / scrum master n Planning: chairs planning sessions, stand up meetings, demos and retrospectives n Organizes scrum board, keeps back log up to date n Reports progress to senior management: n Weekly progress sessions n Weekly e-mail metrics (time tracking) n Quality engineer / manager n Checks quality of documents n Takes care that reviews are held n Takes care that a proper testing environment is set up by the group n Enforces “continuous testing” approach n Organizes peer reviews

16. 16SEP Planned meetings n Daily standup meetings n Total team n Headed by project manager n Weekly project meetings (sprint planning, demo, retrospective) n Total team n Headed by project manager n Preferably also supervisor present n Weekly progress meetings n Project manager, quality manager and senior management n 15 minutes for each group, Monday n Individual meetings of team members and supervisor n Two times: halfway the project and near the end n General meetings n Intermediate presentation n Project status n Final presentation n Presentation + poster n For general public (invite: parents, relatives, friends, ….)

17. 17SEP Short term work n Define project name n Establish meeting schedule n Contact between group and project manager n Contact supervisor n Assign tasks and responsibilities n Start UR group (2-3 people) n Go to customer n Ask questions n Write iteratively versions of URD n Involve customer as much as possible n Set up development environment n Including configuration management n Perform research into technical questions n Read about scrum

18. 18SEP Customer presentations