Principle of Project Management, Fall 20081 Software Project Management Session 7: Risk and Change Management... Principle of Project Management, Fall 20083 Risk Management • Problems th
Trang 1Principle of Project Management, Fall 2008
1
Software Project Management
Session 7: Risk and Change Management
Trang 2Principle of Project Management, Fall 2008
Trang 3Principle of Project Management, Fall 2008
3
Risk Management
• Problems that haven’t happened yet
• Why is it hard?
• Some are wary of bearing bad news
– No one wants to be the messenger
– Or seen as “a worrier”
• You need to define a strategy early in your project
Trang 4Principle of Project Management, Fall 2008
4
Risk Management
• Definition of Risk: An uncertain event or
condition that, if it occurs, has a positive or negative effect on a project objective.
• Identification, Analysis, Control
• Goal: avoid a crisis
• Thayer: Risk Mgmt vs Project Mgt.
– For a specific vs all projects
– Proactive vs reactive
Trang 5Principle of Project Management, Fall 2008
Trang 6Principle of Project Management, Fall 2008
Trang 7Principle of Project Management, Fall 2008
7
Types of Risks
• Quality Risks
• Operational Risks
• Most of the “Classic Mistakes”
– Classic mistakes are made more often
Trang 8Principle of Project Management, Fall 2008
Unknown risks: Foreseen based on experience
- Difficult communication with customer
- Fluctuation within team
Unknowable risks: Cannot be foreseen
- Half of the team gets fish poisoning at first social event
- Earthquake wipes out production plant
Trang 9Principle of Project
Management, Fall 2008
9
Trang 10Principle of Project
Management, Fall 2008
10
Trang 11Principle of Project
Management, Fall 2008
11
Trang 12Principle of Project
Management, Fall 2008
12
Trang 13Principle of Project
Management, Fall 2008
13
Trang 14Principle of Project
Management, Fall 2008
14
Trang 15Principle of Project
Management, Fall 2008
15
Trang 16Principle of Project
Management, Fall 2008
16
Trang 17Principle of Project
Management, Fall 2008
17
Trang 18Principle of Project
Management, Fall 2008
18
Trang 19Principle of Project
Management, Fall 2008
19
Trang 20Principle of Project
Management, Fall 2008
20
Trang 21Principle of Project
Management, Fall 2008
21
Trang 22Principle of Project
Management, Fall 2008
22
Trang 23Principle of Project
Management, Fall 2008
23
Trang 24Principle of Project
Management, Fall 2008
24
Trang 25Principle of Project Management, Fall 2008
25
Miniature Milestones
• A risk-reduction technique
• Use of small goals within project schedule
– One of McConnell’s Best Practices (Ch 27)
• Fine-grained approach to plan & track
• Reduces risk of undetected project slippage
• Pros
– Enhances status visibility
– Good for project recovery
• Cons
– Increase project tracking effort
Trang 26Principle of Project Management, Fall 2008
26
Miniature Milestones
• Can be used throughout the development cycle
• Works with will hard-to-manage project activities
or methods
– Such as with evolutionary prototyping
• Reduces unpleasant surprises
• Success factors
– Overcoming resistance from those managed
– Staying true to ‘miniature’ nature
• Can improve motivation through achievements
Trang 27Principle of Project Management, Fall 2008
27
Miniature Milestones
• Requires a detailed schedule
• Have early milestones
• McConnell says 1-2 days
– Longer is still good (1-2 weeks)
• Encourages iterative development
• Use binary milestones
– Done or not done (100%)
Trang 28CM Tool
Trang 29Principle of Project
Management, Fall 2008
29
Trang 30Principle of Project
Management, Fall 2008
30
Trang 31Principle of Project
Management, Fall 2008
31
Trang 32Principle of Project
Management, Fall 2008
32
Trang 33Principle of Project
Management, Fall 2008
33
Trang 34Principle of Project
Management, Fall 2008
34
Trang 35Principle of Project Management, Fall 2008
35
Configuration Control
• A management support function
• Includes
• Program code changes
• Requirements and design changes
• Version release changes
• Essential for developed items
• Code, documentation, etc.
• Example
• The case of the code that used to work
– But didn’t in time for the demo
Trang 36Principle of Project Management, Fall 2008
36
Configuration Control Terminology
• Software Configuration Control Item (SCCI)
• a.k.a Source Item (SI)
• Anything suitable for configuration control
• Source code, documents, diagrams, etc.
• Change Control: process of controlling changes
• Proposal, evaluation, approval, scheduling, implementation, tracking
• Version Control: controlling software version releases
• Recording and saving releases
• Documenting release differences
• Configuration Control: process of evaluating, approving and disapproving, and managing changes to SCCIs
Trang 37Principle of Project Management, Fall 2008
37
SCM
• Software Configuration Management
• Formal engineering discipline
• Methods and tools to identify & manage software throughout its use
Trang 38Principle of Project Management, Fall 2008
38
Configuration Control Needs
– Establish clearly defined mgmt Authority – Setup control standards, procedures and
guidelines
• All team members must be aware of these
– Requires appropriate tools and infrastructure – Configuration Management Plan must be produced during planning phase
• Often part of Software Development Plan
Trang 39Principle of Project Management, Fall 2008
Trang 40Principle of Project Management, Fall 2008
40
Homework
• Reading “Project Human Resource
Management”
• Earned Value URL: See class web site
• Top 10 Risk List for your project
Trang 41Principle of Project
Management, Fall 2008
41
Questions?