R

1
RD System Development Management 1

• 2008

2
Lectures

• 8 lectures of 2 hour
• 1 by Mario van Vliet
• 1 by a guest
• 2 hour written examination
• no books or documentation
• based on
• Software Engineering A practitioners Approach
  European Adaptation, sixth edition , Roger S.
  Pressman
• sheets of the presentations
• extra treated concepts and theories

3
GIP-House

• practical work of RD SDM1
• management of the software house and its project
• serious participation needed
• pass or fail
• prerequisite for written examination
• students with sufficient experience in project
  management can be exempted
• provide copies of grade lists
• own description of followed courses and project
  and your management role in it

4
Aim

• SDM1 has the aim that the student, at the end of
  the course, has all the professional skills of an
  IT project leader.
• SDM1 resembles the phase in an IT career in which
  the project leader takes responsibility for the
  management of a software development project.
• Within SDM1/GiP-House the student aims at two
  goals
• realizing their own personal development goals,
  and
• delivering a high quality system.
• In this structure the focus is very much on
  teamwork in order to realize the required
  deliverables.

5
Scope

• Within SDM1we address the project management
  aspects of the whole life cycle of a system
  development project
• from definition study through system design,
  system development and system implementation all
  the way to the maintenance of a system in an
  operational environment.
• Within GIP-House the student can perform the
  following roles Project manager, Quality
  manager, Contract Owner, Public Relations
  Manager, Director.

6
Course Subjects

• Project management
• Project planning
• Business Planning, Technical Planning
• Rolls of
• Project manager, Quality manager, Contract
  Owner,Public Relations Manager, Director
• Planning methods
• PERT, CPM, Work Breakdown structure, Gantt-charts
• Quality Management
• Risk Management (gastcollege)
• Metrics
• Component Based Development

7
Project management

• What is project management?
• What makes management of software development so
  special?
• Which roles are there?
• Which steps do you have to take?
• What is a project?
• Chapter 1 and 21 of book

8
What is project management
..it involves the planning, monitoring and
control of the people, process and events that
occur as software evolves from a preliminary
concept to an operational implementation.
(Dilbert) .. The role of the manager is to
plan, organize, staff, direct and control. He or
she deals with ideas, things and people.
(Tomayko and Hallman, 1989) Care that every
stakeholder stays happy
9
North Sea Project Cost History
10,0
8,0
4,0
Final or forecast cost/estimate
2,0
1,0
0,8
0,6
0,5
71 72 73 74 75 76 77 78 79
80 81 82 83 84 85 86 87
89 90
Year of appropriation estimate
10
Challenges
(Van Genuchten 1991)
11
Reasons for cost/delay overrun

• (Van Genuchten 1991)
• Human capacity
• Not available due to
• overruns in previous or other projects, needed
  for unplanned activities.
• Human related
• too little experience with e.g. development
  environment
• more inexperienced then experienced people, wrong
  mix
• Input-requirements related
• requirements too late, too little quality
• specifications for COTS or other hardware too
  late, too little quality
• changing requirements during the project.

12
further

• Product (technology) related
• changing interfaces with environment
• software complexity underestimated
• more problems with performance of memory
  limitations
• more software failures (bugs) than planned
• product wrongly designed, redesign is needed
• Organization related
• less continuity in project team members
• more interruptions than pland
• more influence/interruption of quality assurance
  activities
• bureaucracy.
• Tools related
• Development or test tools too late or not
  adequate
• Needed releases too late or with too many errors

13
of reasons of overruns
14
Implementation benchmarks
Obstacles until go-live
Obstacles after go-live
Change Management
Change Management
Internal Staff Adequancy
Training
Project Team
Internal Staff Adequancy
Training
Prioritization/Resource Allocation
Prioritization/Resource Alllocation
Top Management Support
Project Team
Consultants
Discipline
People 51
Ownership (of Benefits and Other)
People 62
Ownership(of Benefits and Other)
Discipline
Ongoing Support
Program Management
Process Reenigineering
Stage/Transition
Stage/Transition
Business Performance
Process 16
Benefit Realization
Process 19
Process Reengineering
Software Functionality
Software Functionality
Application Portfolio Management
Enhancements/Upgrades
Enhancements/Upgrades
Data
Application Portfolio Management
Technology 12
Technology 19
Reporting
Reporting
0
2
4
6
8
10
12
14
16
0
2
4
6
8
10
12
14
16
of Mentions
of Mentions
15
Cost overrun in real project
16
specific to software project management?

• Software is a creative product based on human
  ideas, concepts and models it has no natural
  limits
• Software develops during the process
• Software engineering is relative young measuring
  is difficult
• Developed software needs acceptance by users in
  their environments
• User requirements change during the development
• Fixing the design is a balancing act between
  user acceptance and project control possibilities
• Design is based on concepts and ideas, not on
  fixed or well known building blocks
• It is difficult to detect bugs during the
  development process
• Communication and interaction with legacy systems
  and COTS increases.

17
People, Process Technology in Software
engineering
18
Which roles in project management ?

• (depending on phase and size/complexity of a
  project)
• Sponsor
• Project manager
• Technical project leader
• Integration manager
• Quality assurance manager (intern vs extern)
• Risk manager
• Test coordinator
• Team leader
• Software engineer
• Business analyst
• Technical specialists
• Communication/PR manager

19
Project roles
Steering Committee
Project Sponsor
Project Steering Committee
Project Manager(s)
Technical Project Leader
Functional/Process Groups (User Focal Points)
Analysts
Designers
Programmers
..
User Group 1
User Group 2
User Group n
20
Example
21
Example, people, fases, time
Design
Implementation
Definition
Construction
22
Which plans ?

• Business planning
• Goals and vision
• Requirements Analysis
• Project plan
• Technical Planning
• Program Master plan
• Management plan
• Development plan
• Configuration Management plan
• Quality Assurance plan
• Maintenance plan

• Test plan
• Integration plan
• Documentation plan
• Transition plan
• Firmware development plan

23
End remarks

• Project management has to do with human factors
• People, process en technology influence the
  success
• Project trackingtracing is important
• Project management is not a science, it is based
  on experience
• There are different
• methods to plan and manage
• ways to organize projects
• ways to guard the quality of projects
• These are topics treated in SDM1