Stand van zaken PMO
Download
Report
Transcript Stand van zaken PMO
Software / Web Engineering
Projects
2IPE0 (2IP35)
Spring 2015
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: 10 Ects 280 hours per person
Start: April 20, 2015
Deadline: June 19, 2015 ( 9 weeks after start ! )
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
al planning
week
17
18
kon.dag
19
20
4+5 mei
21
22
hemelvaart
23
24
25
pinksteren
26
27
tentamen tentamen
URD
SRD
ADD
Setup / Research
Sprint 1
20 Apr: kick of f
AT
Code
6 May: URD
deadline
Sprint 2
Sprint 3
18 May: intermediate
presentation
Sprint 4
Sprint 5
22 Jun: hand in
+ peer reviews
+ peer reviews
19 Jun: deadline
15 Jun: end presentation
Lou Somers
6
6 May: URD
deadline
20 Apr: kick of f
22 J
18 May: intermediate
presentation
+
+ peer reviews
Sprint planning
19 Jun: d
15 Jun: 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 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
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.
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.103, 3.104, 3.105, 5.123 (2 groups)
Network, (virtual) server
Lou Somers
12
Formal meetings
Weekly project meetings
Total team
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: May 18, 2015
URD, (part of) SRD, prototype
End presentation: June 15, 2015
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
Stef Schenkelaars
Remco Dijkman
Menno Veen / John Klompers
Tom Verhoeff
Simone Alers
Lou Somers
15