1. Software / Web Engineering Projects 2IPE0
Autumn 2017
Lou Somers

2. Today: kick-off General information about the way of working
Coupling of groups to cases
Start of project…

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

4. Main players Senior management – global organization
Lou Somers
Study counselors – admission, portfolio assignments, poster printing
Roel Bloo, Yves Houben, Elisabeth Melby (portfolio, posters)
BCF – project ICT facilities
Joe Joe Wong
Student administration – project room facilities
???
Supervisors – coaching, supervision on projects, marking
Nicola Zannone / Serguei Roubtsov
Customers – external clients with an assignment
Project and quality managers – steering a project
You

5. Project organization Each group has a project room
Must be kept clean !
Key codes will be arranged in the first week

6. Documentation According to the ESA standard 5 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
2 test plans: UTP, ATP
All documents delivered to customer + senior management
ESA standard is guideline
Project documents (SVVP,SCMP,SQAP) not needed
Omit non applicable sections
Examples of documents from previous years are available
See also the SEP marking form for more details about the required contents of each document

7. Project planning 7

8. Sprint planning 8

9. Scrum 9

10. Standup meetings
Each team member must be present at every standup meeting
One exception: last two weeks during examination period
Missing two meetings will have as a consequence that the student receives an official warning (“yellow card”)
After the third missed meeting the student is excluded from the project and cannot pass anymore
The project manager keeps track of presence
Permission of absence is granted by supervisor or (if needed because of personal circumstances) study counselor

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

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

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

14. Time metrics (each week)

15. 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
Reports progress to senior management:
Weekly progress sessions
Weekly metrics (time tracking)
Quality engineer / manager
Responsible for quality of documents
Use marking form as check list
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

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

17. Short term work Define project name Establish meeting schedule
Contact between group and project manager
Contact supervisor
Assign tasks and responsibilities
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