| 2009 |
|---|
| 31 | EE | Phillip G. Armour:
The business of software: The ontology of paper.
Commun. ACM 52(1): 23-24 (2009) |
| 2008 |
|---|
| 30 | EE | Phillip G. Armour:
Digging CACM.
Commun. ACM 51(1): 13-15 (2008) |
| 29 | EE | Phillip G. Armour:
The inaccurate conception.
Commun. ACM 51(3): 13-16 (2008) |
| 2007 |
|---|
| 28 | EE | Phillip G. Armour:
Agile ... and offshore.
Commun. ACM 50(1): 13-16 (2007) |
| 27 | EE | Phillip G. Armour:
Mortality play.
Commun. ACM 50(3): 15-18 (2007) |
| 26 | EE | Phillip G. Armour:
Twenty percent.
Commun. ACM 50(6): 21-23 (2007) |
| 25 | EE | Phillip G. Armour:
The conservation of uncertainty.
Commun. ACM 50(9): 25-28 (2007) |
| 2006 |
|---|
| 24 | EE | Phillip G. Armour:
Counting boulders and measuring mountains.
Commun. ACM 49(1): 17-20 (2006) |
| 23 | EE | Phillip G. Armour:
The operational executive sponsor.
Commun. ACM 49(3): 15-18 (2006) |
| 22 | EE | Phillip G. Armour:
The learning edge.
Commun. ACM 49(6): 19-22 (2006) |
| 21 | EE | Phillip G. Armour:
Software: hard data.
Commun. ACM 49(9): 15-17 (2006) |
| 2005 |
|---|
| 20 | EE | Phillip G. Armour:
The unconscious art of software testing.
Commun. ACM 48(1): 15-18 (2005) |
| 19 | EE | Phillip G. Armour:
Project portfolios: organizational management of risk.
Commun. ACM 48(3): 17-20 (2005) |
| 18 | EE | Phillip G. Armour:
Sarbanes-Oxley and software projects.
Commun. ACM 48(6): 15-17 (2005) |
| 17 | EE | Phillip G. Armour:
To plan, two plans.
Commun. ACM 48(9): 15-19 (2005) |
| 2004 |
|---|
| 16 | EE | Phillip G. Armour:
When executives code.
Commun. ACM 47(1): 19-22 (2004) |
| 15 | EE | Phillip G. Armour:
Not-defect: the mature discipline of testing.
Commun. ACM 47(10): 15-18 (2004) |
| 14 | EE | Phillip G. Armour:
Beware of counting LOC.
Commun. ACM 47(3): 21-24 (2004) |
| 13 | EE | Phillip G. Armour:
Real work, necessary friction, optional chaos.
Commun. ACM 47(6): 15-18 (2004) |
| 2003 |
|---|
| 12 | EE | Phillip G. Armour:
The reorg cycle.
Commun. ACM 46(2): 19-22 (2003) |
| 11 | EE | Phillip G. Armour:
In the zone: the need for flexible roles.
Commun. ACM 46(5): 15-19 (2003) |
| 10 | EE | Phillip G. Armour:
Closing the learning application gap.
Commun. ACM 46(9): 27-31 (2003) |
| 2002 |
|---|
| 9 | EE | Phillip G. Armour:
The spiritual life of projects.
Commun. ACM 45(1): 11-14 (2002) |
| 8 | EE | Phillip G. Armour:
Ten unmyths of project estimation.
Commun. ACM 45(11): 15-18 (2002) |
| 7 | EE | Phillip G. Armour:
The organism and the mechanism of projects.
Commun. ACM 45(5): 17-20 (2002) |
| 2001 |
|---|
| 6 | EE | Phillip G. Armour:
The laws of software process.
Commun. ACM 44(1): 1517 (2001) |
| 5 | | Phillip G. Armour:
Zeppelins and jet planes: a metaphor for modern software projects.
Commun. ACM 44(10): 13-15 (2001) |
| 4 | EE | Phillip G. Armour:
Software as Currency.
Commun. ACM 44(3): 13-14 (2001) |
| 3 | EE | Phillip G. Armour:
Matching process to types of teams.
Commun. ACM 44(7): 21-23 (2001) |
| 2000 |
|---|
| 2 | EE | Phillip G. Armour:
The five orders of ignorance.
Commun. ACM 43(10): 17-20 (2000) |
| 1 | EE | Phillip G. Armour:
The case for a new business model.
Commun. ACM 43(8): 19-22 (2000) |
