十大軟體開發注定失敗的警訊

http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=a76eab63-70f0-48b4-8b75-66c366a651cd

十大軟體開發注定失敗的警訊

1. Trying to do too much in the first version. See Raymond's point above.
第一個版本就做太多功能

2. Taking a major dependency on unproven technology.
太依賴於未經證實的技術

3. Competing with an existing internal project that was either a cash cow or had backers that are highly placed in the corporate hierarchy.
與內部競爭的project, 要有強力的backer或你身處在當紅的部門!

4. The team is understaffed. If you have less people than can handle the amount of work you have to do then the right thing to do is to scale back the project. Practically every other choice leads to failure.
團隊人員不足.

5. Complexity is one of the goals of the project because "complex problems require complex solutions".
複雜性是project成功的目標之一, 因為複雜的問題需要複雜的解法!

6. Schedule Chicken
開發人員因為無法承受時程的壓力，而做出一些敷衍、耍小手段等扭曲的行為，好讓自己的工作看起來已經達到預定進度了。

7. Scope Creep
不斷變動需要實作的範圍

8. Second System Syndrome
第二版並不是要更強大, 更厲害

9. No Entrance Strategy. When a project can't articulate how it goes from a demo or prototype to being in the hands of end users, there's a problem. This is particularly relevant in the "Web 2,0" world where many startups only strategy for success is getting a mention on TechCrunch and the fact that their service has "viral" features.
缺乏進場策略

10. Tackling a problem you don't know how to solve. It's pretty amazing how often I've seen this occur.
解決一個你不知道如何解決的問題