| 2009 | ||
|---|---|---|
| 20 | Capers Jones: Positive and Negative Innovations in Software Engineering. IJSSCI 1(2): 20-30 (2009) | |
| 2003 | ||
| 19 | Capers Jones: Variations in Software Development Practices . IEEE Software 20(6): 22-27 (2003) | |
| 1999 | ||
| 18 | Capers Jones: The year 2000 software problem: Quantifying the cost and addressing the consequences. AI Soc. 13(4): 452-458 (1999) | |
| 17 | Capers Jones: The Euro, Y2K, and the US Software Labor Shortage. IEEE Software 16(3): 55-61 (1999) | |
| 1996 | ||
| 16 | Capers Jones: The Economics of Software Process Improvement. IEEE Computer 29(1): 95-97 (1996) | |
| 15 | Capers Jones: Software Change Management. IEEE Computer 29(2): 80-82 (1996) | |
| 14 | Capers Jones: Activity-based Software Costing. IEEE Computer 29(5): 103-104 (1996) | |
| 13 | Capers Jones: Our Worst Current Development Practices. IEEE Software 13(2): 102-104 (1996) | |
| 1995 | ||
| 12 | Capers Jones: How Office Space Affects Programming Productivity. IEEE Computer 28(1): 76-77 (1995) | |
| 11 | Capers Jones: Software Benchmarking. IEEE Computer 28(10): 102-103 (1995) | |
| 10 | Capers Jones: Backfiring: Converting Lines of Code to Function Points. IEEE Computer 28(11): 87-88 (1995) | |
| 9 | Capers Jones: How Software Personnel Learn New Skills. IEEE Computer 28(12): 88-89 (1995) | |
| 8 | Capers Jones: Determining Software Schedules. IEEE Computer 28(2): 73-75 (1995) | |
| 7 | Capers Jones: Patterns of Large Software Systems: Failure and Success. IEEE Computer 28(3): 86-87 (1995) | |
| 6 | Capers Jones: Gaps in Programming Educations. IEEE Computer 28(4): 70-71 (1995) | |
| 5 | Capers Jones: Legal Status of Software Engineering. IEEE Computer 28(5): 98-99 (1995) | |
| 4 | Capers Jones: Why Is Technology Transfer so Hard? IEEE Computer 28(6): 86-87 (1995) | |
| 3 | Capers Jones: What Goes Into An Information Warehouse? IEEE Computer 28(8): 84-85 (1995) | |
| 2 | Capers Jones: End-User Programming. IEEE Computer 28(9): 68-70 (1995) | |
| 1994 | ||
| 1 | Capers Jones: Globalization of Software Supply and Demand. IEEE Software 11(6): 17-24 (1994) | |