Stand van zaken PMO
Download
Report
Transcript Stand van zaken PMO
Software Engineering Projects
2IP35
Fall 2012
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 3, 2012
Deadline: October 27, 2012
Lou Somers
3
Organization
Senior
management
Advisor
Project team
Project
manager
Software
librarian
Team leader
Team leader
Team leader
Quality
engineer
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
planning
week
36
37
38
39
40
41
42
43
44
45
tentamen tentamen
URD
SRD
ADD
Setup / Research
Code
Sprint 1
3 sep: kick off
Sprint 2
17 sep: URD
deadline
AT
Sprint 3
Sprint 4
1 oct: intermediate
presentation
+ peer review s
Sprint 5
29 oct: hand in
+ peer review s
27 oct: deadline
22 oct: end presentation
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).
Lou Somers
6
Sprint planning
21 may: intermediate presentation
23 april: kick off
25 june: han
22 june: deadline
18 june: end presenta
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
Devils triangle
Time
We have
Money
Lou Somers
Fixed budget
Fixed time
Quality
10
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
11
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 17, 2012
URD, (part of) SRD, prototype
End presentation: October 22, 2012
Lou Somers
Project overview, product demo
12
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
13