Software development is usually a linear activity, even when you use an iterative process, and the steps from one phase to the next take place in a logical and linear fashion. The management of the development process, however, is rarely linear. You will find yourself jumping from one problem domain to the next, where the methods to reach one solution don’t often help you in another. The best you can do is bring all your intelligence to bear on the challenge of the moment, knowing your goal is to lead others out of chaos and into clarity. You might call this “living on the edge of chaos,” and perhaps this describes some of your days at the helm.


Software Development Software Engineering Quality Software Development Methodology Agile Method 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    I also thought that if I entitled this chapter “Miscellaneous Topics” it would generate little reader interest.Google Scholar
  2. 2.
    See Chapter 4 where this was discussed.Google Scholar
  3. 3.
    See http://www.eroom.com, http://www.fox.se/eng1ish/starteam/starteam_version_control.htm and other offerings by IBM and Symantec.Google Scholar
  4. 4.
    They would never use the term “rich user interface.” They think this simply means expensive.Google Scholar
  5. 5.
    Vegemite is a vegetable paste commonly put on toast. It’s somewhat equivalent to peanut butter but not nearly as tasty.Google Scholar
  6. 6.
    Dene Bettmeng, reporting in Network World Fusion (http: // www. nwfusion. com/careers/2001/0402man. html) on international relations.Google Scholar
  7. 7.
    The first practical microprocessor was developed in 1971.Google Scholar
  8. 8.
    See Glass, Software Runaways,op. cit.Google Scholar
  9. 9.
    See IEEE Standard Computer Dictionary (Institute of Electrical and Electronics Engineers, 1990).Google Scholar
  10. 10.
    Humphrey, op. cit., p. ix.Google Scholar
  11. 11.
    See Glass, Software Runaways, op. cit., p.56 (Section 2.1.4).Google Scholar
  12. 12.
    Mine, of course, is one of them.Google Scholar
  13. 13.
    Solutions Development Discipline Workbook (Redmond, WA: Microsoft Corporation, 1996), pp. 1–17.Google Scholar
  14. 14.
    A prime example, and probably the origin of many of their ideas, is Jim McCarthy’s Dynamics of Software Development (Microsoft Press, 1995).Google Scholar
  15. 15.
    The purported origin of the term “bug” was an insect preventing a relay from working in an ancient (pre-1950) computer.Google Scholar
  16. 16.
    Kent Beck, Extreme Programming Explained (Reading, MA: Addison-Wesley, 2000), p. xvi.Google Scholar
  17. 17.
    See the Feedback section of the magazine Software Development,November 2001.Google Scholar
  18. 18.
    Visithttp://www.AgileAlliance.org.Google Scholar
  19. 19.
    See Alistair Cockburn, Agile Software Development (NewYork: Addison-Wesley, 2002 ), Appendix A.Google Scholar
  20. 20.
    This term is from Jim Highsmith’s book of the same name. See the Bibliography.Google Scholar
  21. 21.
    Cockburn, op. cit., p. 5.Google Scholar
  22. 22.
    See Cockburn, op. cit., for many examples, and http: //www. adaptivesd. corn for a related online exploration.Google Scholar
  23. 23.
    You didn’t think I would leave out a reference to Star Trek: The Next Generation,did you?Google Scholar
  24. 24.
    Remember that in 1990, there was no Windows, and the graphical Internet wasn’t a reality.Google Scholar
  25. 25.
    Electronic Business, October 15, 1990, p. 147.Google Scholar
  26. 26.
    McBreen, op. cit., p.xv.Google Scholar
  27. 27.
    This was the approach recommended by Leonardo that I discussed in Chapter 6.Google Scholar
  28. 28.
    I’m borrowing heavily here from David Coursey, the AnchorDesk editor at http: //www. zdnet. com, from an article he wrote on October 12, 2001.Google Scholar
  29. 29.
    I’m quoting from the version of this classic edited by James Clavell. Sun Tzu, The Art of War ( NewYork: Dell Publishing, 1983 ), p. 37.Google Scholar
  30. 30.
    I recommend TechRepublic (http: //www.techrepublic. corn) as a starting point for good summaries of relevant topics.Google Scholar
  31. 31.
    The dot-corns were/are famous for this lack of profit. This might not apply to Amazon.com for now, as it hasn’t for several years, but time will tell. I’ll be sorry to see them go if they fail, and I’ll be surprised that all the hundreds of dollars I’ve sent them over the years didn’t make a difference!Google Scholar
  32. 32.
    I talked about this in Chapter 1 (in the “Motivating with Money” section) and Chapter 3 (in the “Promotions and Raises” section) but it’s worth repeating here.Google Scholar
  33. 33.
    Sometimes legal concerns will prevent you from doing this. Check with your boss about company policies in this area.Google Scholar
  34. 34.
    See Chapter 8 where I discussed Andy Grove’s constructive use of the word “paranoia.”Google Scholar

Copyright information

© J. Hank Rainwater 2002

Authors and Affiliations

  • J. Hank Rainwater

There are no affiliations available

Personalised recommendations