10 Keys to Successful Software ProjectsAn Executive Guide(ppt)
10 Keys to Successful Software ProjectsAn Executive Guide(ppt)详细内容
10 Keys to Successful Software ProjectsAn Executive Guide(ppt)
10 Keys to Successful Software Projects An Executive Guide
© 2000-2001 Construx Software Builders, Inc. All Rights Reserved. www.construx.com
The First Project: Example of Failure
The First Project: Giga-Corp’s Graph-It Project*
Bid:
$400K
5 months
100% of required functionality
Result:
$1.5M
14 months
25% of required functionality
Effective Cost Overrun: 1400%
Effective Schedule Overrun: 1000%
Background
State of the Art vs. State of the Practice
“The gap between the best software engineering practice and the average practice is very wide–perhaps wider than in any other engineering discipline.”
– Fred Brooks
What are the General Keys to Success?
Q: What are the most exciting/promising software engineering ideas or techniques on the horizon? A: I don’t think that the most promising ideas are on the horizon. They are already here and have been here for years but are not being used properly. — David L. Parnas
What is Parnas Talking About?
Project planning and management practices
Automated estimation tools (1973)
Evolutionary delivery (1988)
Measurement (1977)
Productivity environments (1984)
Risk management planning (1981)
Requirements engineering practices
Change board (1979)
Throwaway user interface prototyping (1975)
JAD sessions (1985)
Requirements scrubbing (1989)
Productivity Varies Significantly
10:1 variations in productivity between different companies working in the same industries
Productivity is a learned characteristic and can be changed
Typical Project Outcomes
Most Common Sources of Cancellations and Overruns
1. Ill-defined or changing requirements
2. Poor project planning/management
3. Uncontrolled quality problems
4. Unrealistic expectations/inaccurate estimates
5. Naive adoption of new technology
Project Success
Success = Planning * Execution
Planning
Key #1 Clear Vision
Clear Vision
Project teams work toward the goals you set for them
Too many goals = no goals
Good vision statement describes what to leave out—prioritizes
Product vision affects achievement of business goals
Example:
What kind of Rapid Development do you want?
Speed oriented
Schedule-risk oriented
Visibility oriented
Without clear vision you can end up with a project outcome completely counter to your goals
Speed-Oriented Practices-- Better Best Case ...
…Worse Worst Case
Sometimes it’s Justified ...
… Sometimes it’s Not
Risk-Reduction is Sometimes a Better Alternative
Key #2 Stable, Complete, Written Requirements
Requirements
Requirements change is the most common software project risk
Comprehensive, 100% stable requirements are usually not possible, but...
Most requirements changes arise from requirements that were incompletely defined in the first place, not “changing markets” or other similar reasons
Techniques for Defining Stable Requirements
Requirements workshop
User interface prototyping
User interview
Use cases
User manual as spec
Usability studies
Incremental delivery
Requirements reviews/inspections
Key #3 Detailed User Interface Prototypes
User Interface Prototypes
Addresses the most common project risk–changing requirements
Involves users with a “hot” medium
Correlated with lower costs, shorter schedules, and higher user satisfaction
Significant skill required to develop prototypes successfully
Key #4 Effective Project Management
Project Management
Poor planning/management is the second most common project risk
Project planning/management is a high leverage area
Some people don’t appreciate the leverage of project management—they’ve never seen good project management!
Project Manager Responsibilities
Where do most project managers come from?
What are they trained to do?
Good software management require significant software-specific expertise
Scope estimation
Cost, effort & schedule computation
Lifecycle selection
QA planning
Key #5 Accurate Estimates
Need for Accurate Estimates
Unrealistic/unjustified expectations are a major cause of project problems
State of the art is dramatically better than the state of the practice
For example, the average project overruns its planned schedule by more than 100% (and many projects are much worse)
Typical Estimation Accuracy and Improved Estimation
Improved Estimation
Effect of Estimation Accuracy
Accurate Estimation
Estimation is a specialized technical skill
Treat estimation as a mini-project
Plan to re-estimate periodically
Execution
Key #6 Two-Phase Budgeting
Estimate Refinement
Two-Phase Estimation and Budgeting
Benefits
Delays commitment until time when a commitment can be meaningful
Forces activities that should occur upstream actually to occur upstream
Requirements, technical planning, quality planning, etc.
Helps set realistic expectations for all project stakeholders
Improves coordination with non-software groups
Improves execution by putting plans on more informed basis
Key #7 A Focus on Quality
Defect Costs Increase the Longer Defects Stay in Process
Fix More Defects Earlier!
Why Focus on Quality?
For most projects, unplanned defect correction work is the largest cost driver (40-80% of total)
Can focus on quality for sake of economics (as above)
Can focus on quality for sake of quality (not needed nearly as often)
Quality must be planned into the project; it can’t just be tacked onto the end
Fixing Upstream Defects Upstream is High Leverage
Key #8 Technology Expertise
Technology Expertise
Many projects suffer because of poor adoption of new technology
“New technology” = high risk
Expertise in technology matters; software engineering technique matters much more
Key #9 Active Risk Management
Software is Risky Business
KPMG Study:
55% of runaway projects did no risk management
38% did some, but half of those didn’t use their risk findings after the project was underway
7% didn’t know whether they did risk management
Total: About 80% of runaway projects did no meaningful risk management
Role of Risk Management
About as many projects fail as are delivered on time
More than 50% of projects show their problems during initial development
About 25% show their problems during initial planning
Active risk management keeps small problems from turning into big, project-killing problems
Relationship to Business Risk Taking
Perception is that high energy companies take risks
Reality is that most companies are beset by risks from all sides—they aren’t choosing which risks they take
Key to success: Manage non-strategic risks so that you can take strategic risks
Example of Managing Risks
Key #10 Remember, Software Is Created By Humans
Human Factors
Take care of your people
Staffing
Training
Motivation/morale
Work environment
The Second Project: Example of Success
The Second Project: ATAMS Project
Best Estimate:
$10 million
2 years
100% of required functionality
Result:
$2 million
1 year
“10 times as many functions as originally specified”
Key to Success: “Techniques that were shown years ago to produce better software faster yet are still rarely used.”
Key Elements of ATAMS Success
Intact development team
Active user involvement; UI prototyping
Reuse of components wherever possible
Extensive design reviews, code reviews, defect tracking
“Native” risk management
Active management to keep project team on track
The Point
Ineffective organizations often fail, even on low-risk projects
Effective organizations often succeed, even on high-risk projects
The fancy stuff is not what makes the difference--proven practices
Success = Planning * Execution
It depends on how carefully projects are planned and how deliberately they are executed--and that’s just about the whole story!
Contact Information
10 Keys to Successful Software ProjectsAn Executive Guide(ppt)
10 Keys to Successful Software Projects An Executive Guide
© 2000-2001 Construx Software Builders, Inc. All Rights Reserved. www.construx.com
The First Project: Example of Failure
The First Project: Giga-Corp’s Graph-It Project*
Bid:
$400K
5 months
100% of required functionality
Result:
$1.5M
14 months
25% of required functionality
Effective Cost Overrun: 1400%
Effective Schedule Overrun: 1000%
Background
State of the Art vs. State of the Practice
“The gap between the best software engineering practice and the average practice is very wide–perhaps wider than in any other engineering discipline.”
– Fred Brooks
What are the General Keys to Success?
Q: What are the most exciting/promising software engineering ideas or techniques on the horizon? A: I don’t think that the most promising ideas are on the horizon. They are already here and have been here for years but are not being used properly. — David L. Parnas
What is Parnas Talking About?
Project planning and management practices
Automated estimation tools (1973)
Evolutionary delivery (1988)
Measurement (1977)
Productivity environments (1984)
Risk management planning (1981)
Requirements engineering practices
Change board (1979)
Throwaway user interface prototyping (1975)
JAD sessions (1985)
Requirements scrubbing (1989)
Productivity Varies Significantly
10:1 variations in productivity between different companies working in the same industries
Productivity is a learned characteristic and can be changed
Typical Project Outcomes
Most Common Sources of Cancellations and Overruns
1. Ill-defined or changing requirements
2. Poor project planning/management
3. Uncontrolled quality problems
4. Unrealistic expectations/inaccurate estimates
5. Naive adoption of new technology
Project Success
Success = Planning * Execution
Planning
Key #1 Clear Vision
Clear Vision
Project teams work toward the goals you set for them
Too many goals = no goals
Good vision statement describes what to leave out—prioritizes
Product vision affects achievement of business goals
Example:
What kind of Rapid Development do you want?
Speed oriented
Schedule-risk oriented
Visibility oriented
Without clear vision you can end up with a project outcome completely counter to your goals
Speed-Oriented Practices-- Better Best Case ...
…Worse Worst Case
Sometimes it’s Justified ...
… Sometimes it’s Not
Risk-Reduction is Sometimes a Better Alternative
Key #2 Stable, Complete, Written Requirements
Requirements
Requirements change is the most common software project risk
Comprehensive, 100% stable requirements are usually not possible, but...
Most requirements changes arise from requirements that were incompletely defined in the first place, not “changing markets” or other similar reasons
Techniques for Defining Stable Requirements
Requirements workshop
User interface prototyping
User interview
Use cases
User manual as spec
Usability studies
Incremental delivery
Requirements reviews/inspections
Key #3 Detailed User Interface Prototypes
User Interface Prototypes
Addresses the most common project risk–changing requirements
Involves users with a “hot” medium
Correlated with lower costs, shorter schedules, and higher user satisfaction
Significant skill required to develop prototypes successfully
Key #4 Effective Project Management
Project Management
Poor planning/management is the second most common project risk
Project planning/management is a high leverage area
Some people don’t appreciate the leverage of project management—they’ve never seen good project management!
Project Manager Responsibilities
Where do most project managers come from?
What are they trained to do?
Good software management require significant software-specific expertise
Scope estimation
Cost, effort & schedule computation
Lifecycle selection
QA planning
Key #5 Accurate Estimates
Need for Accurate Estimates
Unrealistic/unjustified expectations are a major cause of project problems
State of the art is dramatically better than the state of the practice
For example, the average project overruns its planned schedule by more than 100% (and many projects are much worse)
Typical Estimation Accuracy and Improved Estimation
Improved Estimation
Effect of Estimation Accuracy
Accurate Estimation
Estimation is a specialized technical skill
Treat estimation as a mini-project
Plan to re-estimate periodically
Execution
Key #6 Two-Phase Budgeting
Estimate Refinement
Two-Phase Estimation and Budgeting
Benefits
Delays commitment until time when a commitment can be meaningful
Forces activities that should occur upstream actually to occur upstream
Requirements, technical planning, quality planning, etc.
Helps set realistic expectations for all project stakeholders
Improves coordination with non-software groups
Improves execution by putting plans on more informed basis
Key #7 A Focus on Quality
Defect Costs Increase the Longer Defects Stay in Process
Fix More Defects Earlier!
Why Focus on Quality?
For most projects, unplanned defect correction work is the largest cost driver (40-80% of total)
Can focus on quality for sake of economics (as above)
Can focus on quality for sake of quality (not needed nearly as often)
Quality must be planned into the project; it can’t just be tacked onto the end
Fixing Upstream Defects Upstream is High Leverage
Key #8 Technology Expertise
Technology Expertise
Many projects suffer because of poor adoption of new technology
“New technology” = high risk
Expertise in technology matters; software engineering technique matters much more
Key #9 Active Risk Management
Software is Risky Business
KPMG Study:
55% of runaway projects did no risk management
38% did some, but half of those didn’t use their risk findings after the project was underway
7% didn’t know whether they did risk management
Total: About 80% of runaway projects did no meaningful risk management
Role of Risk Management
About as many projects fail as are delivered on time
More than 50% of projects show their problems during initial development
About 25% show their problems during initial planning
Active risk management keeps small problems from turning into big, project-killing problems
Relationship to Business Risk Taking
Perception is that high energy companies take risks
Reality is that most companies are beset by risks from all sides—they aren’t choosing which risks they take
Key to success: Manage non-strategic risks so that you can take strategic risks
Example of Managing Risks
Key #10 Remember, Software Is Created By Humans
Human Factors
Take care of your people
Staffing
Training
Motivation/morale
Work environment
The Second Project: Example of Success
The Second Project: ATAMS Project
Best Estimate:
$10 million
2 years
100% of required functionality
Result:
$2 million
1 year
“10 times as many functions as originally specified”
Key to Success: “Techniques that were shown years ago to produce better software faster yet are still rarely used.”
Key Elements of ATAMS Success
Intact development team
Active user involvement; UI prototyping
Reuse of components wherever possible
Extensive design reviews, code reviews, defect tracking
“Native” risk management
Active management to keep project team on track
The Point
Ineffective organizations often fail, even on low-risk projects
Effective organizations often succeed, even on high-risk projects
The fancy stuff is not what makes the difference--proven practices
Success = Planning * Execution
It depends on how carefully projects are planned and how deliberately they are executed--and that’s just about the whole story!
Contact Information
10 Keys to Successful Software ProjectsAn Executive Guide(ppt)
[下载声明]
1.本站的所有资料均为资料作者提供和网友推荐收集整理而来,仅供学习和研究交流使用。如有侵犯到您版权的,请来电指出,本站将立即改正。电话:010-82593357。
2、访问管理资源网的用户必须明白,本站对提供下载的学习资料等不拥有任何权利,版权归该下载资源的合法拥有者所有。
3、本站保证站内提供的所有可下载资源都是按“原样”提供,本站未做过任何改动;但本网站不保证本站提供的下载资源的准确性、安全性和完整性;同时本网站也不承担用户因使用这些下载资源对自己和他人造成任何形式的损失或伤害。
4、未经本网站的明确许可,任何人不得大量链接本站下载资源;不得复制或仿造本网站。本网站对其自行开发的或和他人共同开发的所有内容、技术手段和服务拥有全部知识产权,任何人不得侵害或破坏,也不得擅自使用。
我要上传资料,请点我!
管理工具分类
ISO认证 课程讲义 管理表格 合同大全 法规条例 营销资料 方案报告 说明标准 管理战略 商业计划书 市场分析 战略经营 策划方案 培训讲义 企业上市 采购物流 电子商务 质量管理 企业名录 生产管理 金融知识 电子书 客户管理 企业文化 报告论文 项目管理 财务资料 固定资产 人力资源 管理制度 工作分析 绩效考核资料 面试招聘 人才测评 岗位管理 职业规划 KPI绩效指标 劳资关系 薪酬激励 人力资源案例 人事表格 考勤管理 人事制度 薪资表格 薪资制度 招聘面试表格 岗位分析 员工管理 薪酬管理 绩效管理 入职指引 薪酬设计 绩效管理 绩效管理培训 绩效管理方案 平衡计分卡 绩效评估 绩效考核表格 人力资源规划 安全管理制度 经营管理制度 组织机构管理 办公总务管理 财务管理制度 质量管理制度 会计管理制度 代理连锁制度 销售管理制度 仓库管理制度 CI管理制度 广告策划制度 工程管理制度 采购管理制度 生产管理制度 进出口制度 考勤管理制度 人事管理制度 员工福利制度 咨询诊断制度 信息管理制度 员工培训制度 办公室制度 人力资源管理 企业培训 绩效考核 其它
精品推荐
- 1C语言难点及分析 407
- 2暗促-酒店玫瑰静悄悄地开 705
- 3终端陈列十五大原则 769
- 4****主营业务发展战略设计 678
- 5中小企业物流发展的对策 755
- 6主顾开拓 809
- 7主动推进的客户服务 615
- 8专业媒体策划与购买 677
- 9中远电视广告CF 789
下载排行
- 1社会保障基础知识(ppt) 16695
- 2安全生产事故案例分析(ppt 16695
- 3行政专员岗位职责 16695
- 4品管部岗位职责与任职要求 16695
- 5员工守则 16695
- 6软件验收报告 16695
- 7问卷调查表(范例) 16695
- 8工资发放明细表 16695
- 9文件签收单 16695


