| 2007 |
|---|
| 11 | EE | Peter Hodgkins,
Luke Hohmann:
Agile Program Management: Lessons Learned from the VeriSign Managed Security Services Team.
AGILE 2007: 194-199 |
| 2004 |
|---|
| 10 | EE | Philipp K. Janert,
Shantha Mohan,
Robert C. Larrabee,
Stephen P. Berczuk,
Brad Appleton,
Fergus O'Connell,
Luke Hohmann:
Bookshelf.
IEEE Software 21(1): 104-106 (2004) |
| 2003 |
|---|
| 9 | EE | Luke Hohmann:
The Difference between Marketecture and Tarchitecture.
IEEE Software 20(4): 51-53 (2003) |
| 8 | EE | Luke Hohmann:
Usability: Happier Users Mean Greater Profits.
IS Management 20(4): 66-76 (2003) |
| 1999 |
|---|
| 7 | EE | Luke Hohmann:
Manager - Coaching the Rookie Manager.
IEEE Software 16(1): (1999) |
| 1998 |
|---|
| 6 | EE | Steven Fraser,
Maggie Davis,
Martin L. Griss,
Luke Hohmann,
Ian Hopper,
Rebecca Joos,
Bill Opdyke:
Software Reuse: Nemesis or Nirvana? (Panel).
OOPSLA 1998: 417-420 |
| 1997 |
|---|
| 5 | | James Coplien,
Luke Hohmann,
Norman L. Kerth,
John Rae-Grant,
Eileen Strider:
Changing the Engine of the Car? While Driving 60 Miles an Hour! (Panel).
OOPSLA 1997: 158-161 |
| 4 | | Luke Hohmann:
In Methods We Trust?
IEEE Computer 30(10): 119-121 (1997) |
| 1996 |
|---|
| 3 | | Paul S. R. Chisholm,
Larry L. Constantine,
Ward Cunningham,
Luke Hohmann,
Norman L. Kerth:
Soft Issues in Software Development (Panel Session).
OOPSLA 1996: 232-234 |
| 2 | | Luke Hohmann:
The First Step in Training: Analysis and Design of Implementation Language?
JOOP 9(6): 61-63 (1996) |
| 1992 |
|---|
| 1 | | Luke Hohmann,
Mark Guzdial,
Elliot Soloway:
SODA: A Computer Aided Design Environment for the Doing and Learning of Software Design.
ICCAL 1992: 307-319 |
