|
|
|
- [[Japanese]]
|
|
|
|
* Part I Utilizing human resources
|
|
|
|
* [[Chapter 1 Trouble somewhere today]]
|
|
|
|
* [[Chapter 2 Cheeseburger production and sales manual]]
|
|
|
|
* [[Chapter 3 Vienna is waiting for you]]
|
|
|
|
* [[Chapter 4 Quality first...if time permits]]
|
|
|
|
* [[Chapter 5 Revision of Parkinson's Law]]
|
|
|
|
* [[Chapter 6 Does cancer work well? "Laetrail"]]
|
|
|
|
- Japanese
|
|
|
|
* Part I Utilizing human resources
|
|
|
|
* Chapter 1 Trouble somewhere today
|
|
|
|
* Chapter 2 Cheeseburger production and sales manual
|
|
|
|
* Chapter 3 Vienna is waiting for you
|
|
|
|
* Chapter 4 Quality first...if time permits
|
|
|
|
* Chapter 5 Revision of Parkinson's Law
|
|
|
|
* Chapter 6 Does cancer work well? "Laetrail"
|
|
|
|
|
|
|
|
## Chapter 4 Quality first...if time permits (pp.21-26)
|
|
|
|
|
|
|
|
- Pride and Quality
|
|
|
|
- Programmer self-esteem is tied to product quality (**quality** not **quantity**)
|
|
|
|
- The lowest level that satisfies a programmer's self-esteem = the highest level ever reached, much higher than the market is willing to pay
|
|
|
|
- It's true that there are users in the market who don't care about poor quality, but they are a hindrance to meeting programmers' quality standards.
|
|
|
|
- If you cater to users who don't care about low quality, you will lose users who don't buy low quality products, and your market penetration will decrease.
|
|
|
|
- Programmer self-esteem is tied to product quality (**quality** not **quantity**)
|
|
|
|
- The lowest level that satisfies a programmer's self-esteem = the highest level ever reached, much higher than the market is willing to pay
|
|
|
|
- It's true that there are users in the market who don't care about poor quality, but they are a hindrance to meeting programmers' quality standards.
|
|
|
|
- If you cater to users who don't care about low quality, you will lose users who don't buy low quality products, and your market penetration will decrease.
|
|
|
|
|
|
|
|
> Letting the buyer decide the quality standard, not the developer, is called "**escape from the quality first principle**". ... In the long run, matching quality to the market will increase costs.
|
|
|
|
|
| ... | ... | @@ -28,15 +28,18 @@ The idea that price and quality are in a trade-off relationship does not exist i |
|
|
|
On the contrary, it is widely accepted that higher quality leads to lower costs.
|
|
|
|
```
|
|
|
|
|
|
|
|
[^1]\[Tajima and Matsubara 1984\] p.40
|
|
|
|
[^1][Tajima and Matsubara 1984] p.40
|
|
|
|
|
|
|
|
```
|
|
|
|
Quality is free. But only for those willing to pay for quality.
|
|
|
|
```
|
|
|
|
|
|
|
|
[^2]\[Crosby 1979\]
|
|
|
|
[^2][Crosby 1979]
|
|
|
|
|
|
|
|
- Recognize that Hewlett-Packard engineers are owed a culture of delivering quality far above the market
|
|
|
|
- At Hitachi Software Engineering (currently Hitachi Solutions) and some Fujitsu departments, project teams have the authority to refuse product shipments to protect quality.
|
|
|
|
|
|
|
|
→ **Not allowing the customer to take the initiative on quality in a good way is essential for maintaining quality and increasing productivity** |
|
|
\ No newline at end of file |
|
|
|
→ **Not allowing the customer to take the initiative on quality in a good way is essential for maintaining quality and increasing productivity**
|
|
|
|
|
|
|
|
[^1]: Tajima and Matsubara, 1984.：Tajima, D., and T. Matsubara. "Inside the Japanese Software Industry." Computer, Vol.17(March 1984).
|
|
|
|
[^2]: Crosby, 1979.：Crosby, Philip B. Quality Is Free: The Art of Making Quality Certain, New York: Harper & Row, 1970. 邦訳 小林宏治監訳、『クオリティ・マネジメント――よい品質をタダで手にいれる法』、日本能率協会、1980年 |
|
|
\ No newline at end of file |
