Please enable JavaScript.
Coggle requires JavaScript to display documents.
CHƯƠNG 4: WHY IS SOFTWARE PROCESS IMPROVEMENT IMPORTANT? (2/BENEFIT SPI 2,…
CHƯƠNG 4: WHY IS SOFTWARE PROCESS IMPROVEMENT IMPORTANT?
THE CHANGE DRIVER :check: IMPORTANT
The change drivers help an organization
understand and define an organizational response to the critical question of "Why change?"
Change drivers
Reduced profits
Declining market share
Increasing personal turnover
New tech
MOTIVATION FOR PROCESS CHANGES.
Technology change
A lot of
significant problems
(organization
pains), which impact operations and/or
business results.
Change
in organization’s Strategic
Objectives
Benefits
of well-established process
improvement program
4/TECHNOLOGY CHANGE CYCLE.
Information Security
Web 2.0
SMAC :check:
big data Analytics
Mobility
Cloud computing
Social media
Technology and Personnel Turnover :check: IMPORTANT
Employee turnover (working in IT industry) is 5 to 7 percent a year
What does this mean to an
organization
How do you deal with about issues? That’s why Process improvement is important. We need to improve process, measure and control it effectively
Technology turnover is about 12-18 months
1/BENEFIT SPI 1
Productivity improvements of 10% - 50%
Improved ability to plan and control
projects, reduced project delays
Quality improvements: significantly decreased
error rates and field problems, resulting in
reduced rewor
Cycle time reductions of 20% -50%
Cost savings average 5:1 ROI
2/BENEFIT SPI 2
Fewer overtime hours
More stable work environment
Improved working conditions
Improved quality of work life
Improved employee morale
Reduced employee turnover
Improved management of project risk
Improved customer satisfaction
Better company image
2/Strategic Objectives
Company image
Reliable, cost-effective, value-adding
supplier
Innovative, highly competent
Preferred employer
Revenue growth/profit growth
Market share/time to market
3/Organization pains
Schedules and budgets are routinely
exceeded
Personnel turnover
Inability to predict schedule, cost,
design/code readiness
High incidence of software defects
No objective basis for judging product
quality
Low productivity
KPI
Questions
Đặt công hỏi trong trường hợp ngược lại nếu không cải thiện hài lòng KH thì sẽ ra sao? Từ đó đưa risks tương ứng vs Budget Risk (Bỏ chi phí hỗ trợ nhân viên "mitigate" và ngăn chặn các risk). Đồng thời, từ risk đưa ra xác suất xảy ra lỗi
Metrics
CP RISK khắc phục nó X Xác suất xảy ra=
RISK BUDGET
Goals
Công ty đưa ra mục tiêu cải thiện về sự hài lòng khách hàng. 1/
