Software Engineering Projects
2IP35
Autumn 2014
http://wwwis.win.tue.nl/2IP35/
Lou Somers
1
Today: kick-off
 General information about the projects
 Presentation by the customers
 Groups subscribe to cases
 Coupling of groups to cases
Lou Somers
2
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)
Lou Somers
3
Organization
Senior
management
Advisor
Project team
Project
manager
Software
librarian
Team leader
Team leader
Team leader
Quality
manager
Software
Software
engineers
Software
engineers
engineers
Lou Somers
4
Documentation
 According to the ESA standard

Project documents:





Product documents:







SPMP: Software Project Management Plan
SVVP: Software Verification and Validation Plan
SCMP: Software Configuration Management Plan
SQAP: Software Quality Assurance Plan
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


Lou Somers
All product documents delivered to customer
All documents delivered to senior management
5
Project planning
Global planning
week
36
37
38
39
40
41
42
43
44
45
tentamen tentamen
URD
SRD
ADD
Setup / Research
Code
Sprint 1
1 sep: kick of f
Sprint 2
15 sep: URD
deadline
Sprint 3
AT
Sprint 4
Sprint 5
29 sep: intermediate
presentation
27 oct: hand in
+ peer reviews
+ peer reviews
24 oct: deadline
20 oct: end presentation
Sprint planning
Each sprint starts with a planning session (1 hour) and ends with a demo (30 min) and a retrospective (15 min).
Lou Somers
6
During
the sprint, each morning a standup meeting (scrum) is held (15 minutes).
Sprint planning
21 may: intermediate presentation
23 april: kick off
25 june:
22 june: dea
18 june: end pres
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
planning session
after
retrospective
scrum
scrum
scrum
scrum
scrum
demo
Planning session
Precondition: 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
Retrospective
Precondition: everybody has three items, categories "keep", "stop", "try"
During the session everybody mentions one item.
Lou Somers
7
Scrum
Lou Somers
8
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
Lou Somers
9
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
Lou Somers
10
Devils triangle
Time
We have


Money
Lou Somers
Fixed budget
Fixed time
Quality
11
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
Lou Somers
12
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

Lou Somers
Project overview, product demo
13
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
Lou Somers
14
Customer presentations
 Kees van Overveld
 Michiel Seerden
Lou Somers
15