• Risk Management • Change Control • Configuration Management
Principle of Project Management, Fal 2
l 2008 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
Principle of Project Management, Fal 3
l 2008 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 Principle of Project Management, Fal 4 l 2008 Project Risk • Characterized by: – Uncertainty (0 < probability < 1) – An associated loss (money, life, reputation, etc) – Manageable – some action can control it • Risk Exposure – Product of probability and potential loss • Problem – A risk that has materialized Principle of Project Management, Fal 5 l 2008 Types of Risks • Schedule Risks • Schedule compression (customer, marketing, etc.) • Cost Risks • Unreasonable budgets • Requirements Risks • Incorrect • Incomplete • Unclear or inconsistent • Volatile
Principle of Project Management, Fal 6
l 2008 Types of Risks • Quality Risks • Operational Risks • Most of the “Classic Mistakes” – Classic mistakes are made more often
Principle of Project Management, Fal 7
l 2008 Types of Risks Known risks - Unclear requirements - Inexperienced team 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 Principle of Project Management, Fal 8 l 2008 Principle of Project Management, Fal 9 l 2008 Principle of Project Management, Fal 10 l 2008 Principle of Project Management, Fal 11 l 2008 Principle of Project Management, Fal 12 l 2008 Principle of Project Management, Fal 13 l 2008 Principle of Project Management, Fal 14 l 2008 Principle of Project Management, Fal 15 l 2008 Principle of Project Management, Fal 16 l 2008 Principle of Project Management, Fal 17 l 2008 Principle of Project Management, Fal 18 l 2008 Principle of Project Management, Fal 19 l 2008 Principle of Project Management, Fal 20 l 2008 Principle of Project Management, Fal 21 l 2008 Principle of Project Management, Fal 22 l 2008 Principle of Project Management, Fal 23 l 2008 Principle of Project Management, Fal 24 l 2008 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 Principle of Project Management, Fal 25 l 2008 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 Principle of Project Management, Fal 26 l 2008 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%)
l 2008 Principle of Project Management, Fal 29 l 2008 Principle of Project Management, Fal 30 l 2008 Principle of Project Management, Fal 31 l 2008 Principle of Project Management, Fal 32 l 2008 Principle of Project Management, Fal 33 l 2008 Principle of Project Management, Fal 34 l 2008 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
Principle of Project Management, Fal 35
l 2008 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.
Principle of Project Management, Fal 36
l 2008 SCM • Software Configuration Management • Formal engineering discipline • Methods and tools to identify & manage software throughout its use
Principle of Project Management, Fal 37
l 2008 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
Principle of Project Management, Fal 38
l 2008 Maintenance • SCM is very important during all phases starting with Requirements • Continues to be important during Maintenance
Principle of Project Management, Fal 39
l 2008 Homework • Reading “Project Human Resource Management” • Earned Value URL: See class web site • Top 10 Risk List for your project