This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
The Practitioner's Cycles, Part 1: Actual World Problems
March/April 2010 (vol. 25 no. 2)
pp. 4-9
Steven V. Deal, Deal Corp.
Robert R. Hoffman, Institute for Human and Machine Cognition

This essay focuses on the forces and constraints of procurement versus the goals of human centering, especially the creation of intelligent technologies that are usable, useful, and understandable. The procurement process tends to de-emphasize these goals and focus on adherence to rules and regulations. As a result, software system development processes are misaligned with the challenges faced by development teams. This misalignment between "actual world problems" and normative documentation repeatedly results in failed systems. A real-life practitioner's account illustrates this point by describing how a group of individuals, acting on their own initiative and at their own risk, short-circuited the rules and constraints of the procurement process to turn a procurement process failure into a success.

1. D. Graham-Rowe, "Fifty Years of DARPA: Hits, Misses and Ones to Watch," NewScientist,15 May 2008; www.newscientist.com/articledn13907-fifty-years-of-darpa-hits-misses-and-ones-to-watch.html .
2. R.R. Hoffman and W.C. Elm, "HCC Implications for the Procurement Process," IEEE Intelligent Systems, vol. 21, no. 1, 2006, pp. 74–81.
3. R.R. Hoffman, K.N. Neville, and J. Fowlkes, "Using Cognitive Task Analysis to Explore Issues in the Procurement of Intelligent Decision Support Systems," Cognition, Technology & Work, vol. 11, no. 1, 2009, pp. 57–70.
4. K. Neville et al., "The Procurement Woes Revisited," IEEE Intelligent Systems, vol. 23, no. 1, 2008, pp. 72–75.
5. "Failure Causes: Statistics," IT Cortex; www.it-cortex.comStat_Failure_Cause.htm.
6. "Herding Cats: Ideas, Comments and Resources about Project Management from Field Experience and Materials from www.niwotridge.com," 2007; http://herdingcats.typepad.com/my_weblog/ 2007/122007-books.html.
7. W. Zachary et al., "Human Total Cost of Ownership: The Penny Foolish Principle at Work," IEEE Intelligent Systems, vol. 22, no. 2, 2007, pp. 88–92.
8. Defense Acquisitions: Assessments of Selected Weapons Programs, Report to Congressional Committees, GAO-08-467SP, Government Accountability Office, 2008; www.gao.gov/new.itemsd08467sp.pdf.
9. S.I. Erwin, "Army's Vice Chief: 'We Have to Speed up How We Procure Things,'" National Defense, Oct. 2009, pp. 22–23; www.nationaldefensemagazine.org/archive/ 2009/October/PagesArmy%E2%80%99sViceChief% .
10. R.R. Hoffman and D.D. Woods, "Studying Cognitive Systems in Context," Human Factors, vol. 42, no. 1, 2000, pp. 1–7.
11. Software and Systems Text Track, solicitation no. Reference-Number-BAA-06-13-IFKA-PART-2, Air Force Materiel Command, Dept. of the Air Force, AFRL: Rome Research Site, 2009; https://www.fbo.govindex?s=opportunity&mode=form&id=355fbd80a0d621c61d5fe6f93cb13cca&tab=core&_cview=1 .
12. "Crusader," GlobalSecurity.org; www.globalsecurity.org/military/systems/ groundcrusader.htm.
13. Experimentation and Rapid Prototyping in Support of Counterterrorism, Committee on Experimentation and Rapid Prototyping in Support of Counterterrorism, National Research Council, 2009.
14. K. Osborn, "Bolton: U.S. Army Should Keep Pursuing Rapid Acquisitions," Defense News,14 Jan. 2008; www.mail-archive.com/osint@yahoogroups.com msg52830.html.
15. Defense Programs: Opportunities to Reform Key Business Practices, GAO/NSlAD-97-99R, Nat'l Security and Int'l Affairs Division, General Accounting Office, 1997; http://archive.gao.gov/paprpdf1158389.pdf .
16. H. Sapolsky, "Let's Skip Acquisition Reform This Time," Defense News,8 Feb. 2009; www.defensenews.comstory.php?i=3938405.
17. "UK: Acquisitions—Fewer Buyers but Failure Rate Steady," Management Today,1 Mar. 1993; www.managementtoday.co.uk/search/article/ 409368uk-acquisitions-fewer-buyers-failure-rate-steady .
18. R. Frese and V. Sauter, "Project Success and Failure: What Is Success, What Is Failure, and How Can You Improve Your Odds for Success?" white paper, College of Business Administration, University of Missouri–St. Louis, 2003; www.umsl.edu/~sauterv/analysis/6840_f03_papers frese.
19. Knowledge@Wharton, "Gadgets at Work: The Blurring Boundary between Consumer and Corporate Technologies," Technology First, Jan. 2009; www.technologyfirst.org/magazine-articles/ 45-january-2009325-g.
20. J.R. Lindsay, "War upon the Map: The Politics of Military User Innovation," doctoral dissertation, Dept. of Political Science, Massachusetts Inst. of Technology, 2006; www.mit.edu/~lindsayj/ProjectsWarUponTheMap%20v30.pdf .

Index Terms:
artificial intelligence, human-centered computing, software system development process, procurement, practitioner, actual world problem
Citation:
Steven V. Deal, Robert R. Hoffman, "The Practitioner's Cycles, Part 1: Actual World Problems," IEEE Intelligent Systems, vol. 25, no. 2, pp. 4-9, March-April 2010, doi:10.1109/MIS.2010.54
Usage of this product signifies your acceptance of the Terms of Use.