1Lou Somers

Software Engineering Projects2IP35

Autumn 2014

http://wwwis.win.tue.nl/2IP35/

2Lou Somers

Today: kick-off

General information about the projects

Presentation by the customers

Groups subscribe to cases Coupling of groups to cases

3Lou Somers

General information

A real project A real customer A team consists of 8-10 students Separate project and quality manager (students 2IP45) Each team has an advisor (staff member)

Timing Available time: 12 Ects 336 hours per person Start: September 1, 2014 Deadline: October 24, 2014 (eight weeks later)

Marking General mark for group Individual adjustment (peer reviews by group, managers, advisor)

4Lou Somers

Organization

Team leader

Software engineers

Senior management

Project manager

Software librarian

Software engineers

Quality manager

Advisor

Software engineers

Project team

Team leader Team leader

5Lou Somers

Documentation

According to the ESA standard

Project documents: SPMP: Software Project Management Plan SVVP: Software Verification and Validation Plan SCMP: Software Configuration Management Plan SQAP: Software Quality Assurance Plan

Product documents: URD: User Requirements Document SRD: Software Requirements Document ADD: Architectural Design Document DDD: Detailed Design Document SUM: Software User Manual STD: Software Transfer Document

Project includes “provisional” acceptance, no maintenance All product documents delivered to customer All documents delivered to senior management

6Lou Somers

Project planning

Global planning

week 36 37 38 39 40 41 42 43 44 45

tentamen tentamen

Sprint planning

Each sprint starts with a planning session (1 hour) and ends with a demo (30 min) and a retrospective (15 min).During the sprint, each morning a standup meeting (scrum) is held (15 minutes).

day before 1 2 3 4 5 after

Planning sessionPrecondition: functionalities (stories) have been defined and tasks have been assigned to functionalities

The functionalities are documented in the URD (more detail follows in SRD).Priorities are assigned by the product owner.

During the session: planning poker is used to assign points to the tasks and assemble all tasks for this sprint

RetrospectivePrecondition: everybody has three items, categories "keep", "stop", "try"During the session everybody mentions one item. SEP autumn 2014

URD

SRD

Sprint 3 Sprint 4 Sprint 5Sprint 1 Sprint 2

1 sep: kick of f 27 oct: hand in + peer reviews

29 sep: intermediate presentation + peer reviews

ADD

planning session retrospective

demoscrum scrum scrum scrumscrum

AT

20 oct: end presentation

24 oct: deadline

Setup / Research Code

15 sep: URD deadline

Sprint n

7Lou Somers

Sprint planning

Global planning

week 17 18 19 20 21 22 23 24 25 26 27

kon.dag hemelvaart pinksteren tentamen tentamen

Sprint planning

Each sprint starts with a planning session (1 hour) and ends with a demo (30 min) and a retrospective (15 min).During the sprint, each morning a standup meeting (scrum) is held (15 minutes).

day before 1 2 3 4 5 after

Planning sessionPrecondition: functionalities (stories) have been defined and tasks have been assigned to functionalities

The functionalities are documented in the URD (more detail in SRD).Priorities are assigned by the product owner.

During the session: planning poker is used to assign points to the tasks and assemble all tasks for this sprint

RetrospectivePrecondition: everybody has three items, categories "keep", "stop", "try"During the session everybody mentions one item.

URD

SRD

Sprint 2 Sprint 3 Sprint 4 Sprint 5Sprint 1

23 april: kick off 25 june: hand in

22 june: deadline

18 june: end presentation

21 may: intermediate presentation

ADD

planning session retrospective

demoscrum scrum scrum scrumscrum

AT

8Lou Somers

Scrum

9Lou Somers

Some project procedures

First requirements, than agile coding (scrum) URD contains backlog list. Some prototyping in early phase. Tackle technical risks by advanced research

Formal review procedure of documents Pre-check by advisor Attention points from checklists Customer involved in:

URD, SRD, SUM, and Acceptance Test review Results and review metrics reported to senior management Signature needed of customer and/or advisor

Reporting to management Time metrics (weekly) Progress (weekly) Review metrics

10Lou Somers

Management roles and tasks

Project manager / scrum master Planning: chairs planning sessions, stand up meetings,

demos and retrospectives Organizes scrum board, keeps back log up to date Takes care that management documents are written Reports progress to senior management:

Weekly progress sessions Weekly e-mail metrics (time tracking)

Quality engineer / manager Checks quality of documents Takes care that reviews are held Takes care that a proper testing environment is set up by

the group Enforces “continuous testing” approach Organizes peer reviews

11Lou Somers

Devils triangle

Time

Money Quality

We have Fixed budget Fixed time

12Lou Somers

Group work

Write project plans

Work according to plans Registration of hours spent Divide work into work packages Choose replacements for project manager, librarian and quality

engineer

Write product documents Advisor “helps” One person responsible for customer contacts Contacts with senior management via project manager

Facilities Project rooms: MF 3.061, 3.104 Network, (virtual) server

13Lou Somers

Formal meetings

Weekly project meetings Total team, circa 1 hour Headed by project manager Preferably also advisor present In the scrum phase:

replaced by sprint planning, demo, retrospective.

Weekly progress meetings Project manager, quality engineer and senior management 20 minutes for each group, Monday

Document reviews

General meetings Intermediate presentation: September 29, 2014

URD, (part of) SRD, prototype End presentation: October 20, 2014

Project overview, product demo

14Lou Somers

Short term work

Define project name Establish weekly meeting schedule

Contact between group and project manager Contact advisor

Assign responsibilities Write project plans

Look at examples from previous years (lead time decreased!) Make inventory of available time (exams, holidays, …)

Start UR group (2-3 people) Go to customer Ask questions Write iteratively versions of URD Involve customer as much as possible

Set up development environment Including configuration management

Perform research into technical questions Read about scrum

15Lou Somers

Customer presentations

Kees van Overveld Michiel Seerden