Oy Laatukonsultointi P. Kantelinen Ab

 # (#)

Project management - sources

see also Agile/Incremenal Software Development

Pasi K's favourites are marked with an asterisk (*)

• WWW pages - WWW-sivuja
• Movies - elokuvia
• Books, articles - Kirjoja, artikkeleita
• Finnsih books - Suomalaisia kirjoja



WWW pages - WWW-sivuja:

  1. 100 Lessons Learned for Project Managers, NASA Lessons Learned
  2. Software Productivity Center Inc.'s Software Development and Project Management Resources
  3. University of Southern California/Model-Based Architecting & Software Engineering home page
  4. DoD Software Program Managers Network
  5. Software Development magazines Project Management department
  6. Steve McConell Home Page
  7. Construx Software, good information on project management and effort etimation, see also * http://www.construx.com/survivalguide/
  8. StickyMinds.com (see => Project Management): resources about project management and other areas, too
  9. QSM articles about estimation and project management
  10. Project Management Forum
  11. Project Management Institute
  12. Projektiyhdistys ry
  13. retrospective.com - Kert "The Retrospective Man" Norman's home page
  14. Niwot Ridge resources - a good source of project management related resources
  15. The Standish Group, IT Project Management, reserach , etc., check CHAOS Chronicles
  16. Federation of European Software Metrics Associations
  17. Finnish Software Metrics Association
  18. Michael Greer's project management related links
  19. A ProjectConnetcions.com's site on project management knowledge, including people issues (templates, checklists, etc.)
  20. The Project Manager Home Page (discussion forums, templates, etc.)
  21. NASA Public Lessonse Learned System (PLLS) Database
  22. Practical Software & Systems Measurement - lots of good and practical ideas what to measure in software projects and how to do the measurement
  23. Project Smart home page - lots of project management resources
  24. SoftwareProjects.org - free project management course, discussion forums, etc.
  25. StarWright - project management resources
  26. Scott Berkun's web site - good project management essays and formus
  27. e-ProjectManagers.com - free project management templates, videos, etc.
  28. gantthead.com - free project management articles, templates, forums, etc.
  29. Agile Project Leadership Network
  30. James Chapman's free Excel templates for drawing Gantt charts
  31. The XP Game - an agile approach for planning projects
  32. Project Cartoon - the famous rope swing cartoon


Movies - Elokuvia

  1. ** Stanley Kubrik: The Paths of Glory, 1957, A warning example of how not to handle commitment in projects
  2. ** Akira Kurosawa: The Seven Samurais, 1954. Excellent analogy to project management, starting from customer problem definition up to glorious/bitter end.
  3. ** Edvin Laine: The Unknown Soldier, 1955, based on Vainö Linna's book The Unknown Soldier (book translated to more than 20 languages). Excellent analogy to leading a team.
  4. ** J. Cameron: Titanic, A cautionary case of a project with ambitous goals, blind reliance on new technology and at the same time neglecting risk management

Books, articles - Kirjoja, artikkeleita
  1. ** J. Rothman: Manage It! Your Guide to Modern, Pragmatic Project Management, The Pragmatic Programmers, June 2007
  2. ** S. Berkun: The Art of Project Management, O'Reilly, 2005 - covers areas which other PM books usually ignore -
  3. ** J. Highsmith: Agile Project Management : Creating Innovative Products, Addison-Wesley, 2004
  4. ** S. McConnell: "How to Defend an Unpopular Schedule", IEEE Software, pp. 118 - 119, May 1996
  5. ** F. O'Connell: How to Run Successful Projects in Web Time, Artech House Publishers, 2001
  6. ** J. Spolsky: "Painless Software Schedules", 29.3.2000,
    (check also other articles, interesting stuff ) , and interesting points about work space quality:
  7. ** W. Royce: Software Project Management. A Unified Framework, Addison Wesley, 1998
  8. ** R. Whitehead: Leading a Software Development Team: A Developer's Guide to Succesfully Leading People and Projects, Addison-Wesley, 2001
  9. * K. Beck, C. Andreas: Planning Extreme Programming, Addison-Wesley, 2004
  10. * B. Boehm, D. Port, M. Al-Said: "Avoiding the Software Model-Clash Spiderweb", IEEE Computer, pp. 120 - 122, November 2000
  11. * B. W. Boehm: "Theory-W Software Project Management: Principles and Examples", IEEE Transactions of Software Engineering, pp. 902 - 916, July 1989
  12. * Brown, W.J. et. al.: AntiPatterns in Project Management, John Wiley & Sons, 2000
  13. * W. Brown, et.al.: Anti Patterns. Refactoring Software Architecture and Project in Crisis, John Wiley, 1998
  14. * F. P. Brooks Jr.: The Mythical Man-Month, Addison-Wesley, 1995
  15. * E. Carmel: Global Software Teams. Collaborating Across Borders and Time Zones., Prentice Hall, 1999
  16. * A. Cockburn: "Selecting a Project's Methodology", IEEE Software, pp. 64 - 71, July/August 2000
  17. * T. DeMarco: Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency, Random House, 2001
  18. * T. DeMarco & T. Lister: Peopleware: Productive Projects and Teams, Dorset House, 1999
  19. * T. DeMarco: Controlling Software Projects, Yourdon Press, 1982
  20. * M. Haywood: Managing Virtual Teams: Practical Techniques For High-Technology Project Managers, Artech House, 1998
  21. * S.P. Keider: "Why Projects Fail", Datamation magazine, pp. 75 - 77, December 1974
  22. * N. L. Kerth: Project Retrospectives,a Handbook for Team Reviews, Dorset House, 2000
  23. * T. Kidder: "The Soul of a New Machine", Atlantic-Little Brown, 1981 or Back Bay Books (Little, Brown and Company), 2000
  24. * S. Maguire: Debugging the Development Process, Microsoft Press, 1994
  25. * S. McConnell: Rapid Development: Taming Wild Software Schedules, Microsoft Press, 1996
  26. * S. McConnell: Software Project Survival Guide, Microsoft Press, 1997
  27. * P. W. Metzger, John Boddie: Managing A Programming Project: Processes and People, Prentice Hall, 1995
  28. * K. P. Madhavi, A.L. Jacob:"Evolutionary Prototype Model for Web Projects", Software Quality Professional, pp. 26 - 32, September, 2001
  29. * E. Miranda: "Planning and Executing Time-Bound Projects", IEEE Computer, pp. 73 - 79, March 2002
  30. * N. Poter, M. Sakry: "We Must Overcommit—We Must Win Business", pp. 4 - 14, Software Quality Professional, March 2005
  31. * S. Rakitin:”Creating Accurate Estimates and Realistic Schedules”, Software Quality Professional, pp. 30 - 36, March 2002
  32. * John. S. Reel: "Critical Success Factors in Software Projects", IEEE Software, pp. 18 - 23, May/June 1999
  33. * L. Rising, N.S. Janoff: "The Scrum Software Development Process for Small Teams", IEEE Software, pp. 26 - 32, July/August 2000
  34. * L. Suardi: ”How to Manage Your Software Product Life Cycle with MAUI”, Communications of the ACM, pp. 89 - 94, March 2004
  35. * C. Wallin, F. Ekdahl, S. Larsson: "Integrating Business and Software Development Models", IEEE Software, pp. 28 - 33, November/December 2002
  36. * E. Yourdon: Death March: The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects, Prentice Hall, 2003
  37. Project Analyzer, Software Program Managers Network, April 2000 (www.spmn.com/products_guidebooks.html)
  38. Little Book of Bad Excuces, Software Program Managers Network, June 1998 (www.spmn.com/products_guidebooks.html)
  39. Communications of the ACM magazine's theme issue on Orchestrating Project Organization and Management, October 1993
  40. IEEE Software magazine's theme issue on The Business of Software, November/December 2002
  41. IEEE Software magazine's theme issue on Small Software Projects, September/October 2000
  42. IEEE Computer magazine's theme issue on Object-Oriented Project Management, September 1996
  43. ISO 10006 Quality management -- Guidelines to quality in project management, ISO Internationall Standardization Organization, suomenkielinen versio SFS:ltä
  44. T. Abdel-Hamid & S. E. Madnick: Software Project Dynamics, An Integrated Approach, Prentice-Hall, 1991
  45. K. Aguanno, ed.: Managing Agile Projects, Multi-Media Publications, 2007
  46. I. Alexander, S. Robertson "Understanding Project Sociology by Modeling Stakeholders", IEEE Software, pp. 23 - 27, January/February 2004
  47. S. W. Ambler: "Agile Project Management Tips", Ambysoft, 20.2.2006
  48. S. W. Ambler: "Agile Requirements Change Management", Ambysoft, 19.8.2006
  49. D.J. Anderson: Agile Management for Software Engineering, Prentice Hall, 2003
  50. J. Andrea: "The Case of The Missing Fingerprint: Solve The Mystery of Successful End-of-Project Retrospectives", Better Software, pp. 30 - 36, February 2007
  51. M. Aoyama: "Web-Based Agile Software Development", IEEE Software November/December 1998
  52. M. Aoyama: "Concurrent Development Process Model", IEEE Software, July 1993
  53. J. Appelo: Progress in Three Dimensions, Software Quality Professional, pp. 20 - 26, June 2008
  54. S. Augustine: Managing Agile Projects, Prentice Hall, 2005
  55. C. M. Baca: Project Management for Mere Mortals, Addison Wesley, 2008
  56. D.Banerjee: "Software Process Improvement in a Research Institute: Driven with Project Management Process", Software Quality Professional, pp. 15 - 25, March 2005
  57. E. M. Bennatan: Catastrophe Disentanglement : Getting Software Projects Back on Track, Addison-Wesley, 2006
  58. E.M. Bennatan: "Catastrophe Disentanglement: Getting Software Projects Back on Track", CrossTalk, October 2004
  59. E. M. Bennatan: On Time, Within Budget: Software Projects Management Practices and Techniques, John WIley & Sons, 2000
  60. S. Berkun: "Happy project status meetings", scottberkun.com PM Clinic, week 30, 2005
  61. A. Birk, T. Dinsoyr, T. Stålhane: "Postmortem: Never Leave a Project without It", IEEE Software, pp. 43 - 45, May/June 2002
  62. K. Bittner, I. Spence: Managing Iterative Software Development Projects, Addison Wesley, 2006
  63. B. Boehm: "Project Termination Doesn't Equal Project Failure", IEEE Computer, September 2000
  64. B. W. Boehm & P.N. Papaccio: "Understanding and Controlling Software Costs", IEEE Transactions of Software Engineering, October 1988
  65. M. Boyd: "A Study of Schedule Slips in a Large Firm", Software Quality Professional, June 2000
  66. S. Brady & T.DeMarco: "Management Aided Software-Engineering", IEEE Software, pp. 25 - 32, November 1994
  67. M. Cantor: Software Leadership: A Guide to Succesful Software, Addison-Wesley, 2002
  68. F. Charles: "Overtime Under Control" (a good article about handling requests to work overtime), Better Software, pp. 14 - 15, October 2006
  69. M. Cohn: Agile Estimating and Planning, Prentice Hall PTR, 2005
  70. B. Collier, T. DeMarco, P. Feary: "A Defined Process For Project Postmortem Review", IEEE Software, pp. 65 - 72, July 1996
  71. A.D. Carlton, R.E. Park & W.B. Goehart: Software Measurement for DoD Systems: Recommendations for Initial Core Measures, CMU/SEI-92-TR-19
  72. M. Ceschi, A. Sillitti, G. Succi, S. De Panfilis: "Project Management in Plan-Based and Agile Companies", IEEE Software, pp. 21-27, May/June 2005
  73. A. Davis: "Trial by Firing: Saga of a Rookie Manager", IEEE Software, pp. 109 - 110, September 1994
  74. B. De Baar: Surprise! Now You’re a Software Project Manager, Multi-Media Publications, 2006
  75. D. DeCarlo: "Why Traditional Project Planning Often Fails", gantthead.com, September 4, 2007
  76. T. DeMarco, P. Hruschka, T. Lister, S. McMenamin, J. Robertson, S. Robertson: Adrenaline Junkies and Template Zombies: Understanding Patterns of Project Behavior, Dorset House, 2008
  77. M. Denne, J. Cleland-Huang: "The Incremental Funding Method: Data-Driven Software Development", IEEE Software, pp. 39 - 47, May/June 2004
  78. E. Derby: Eight Reasons Retrospectives Fail (And What You Can Do About Them), StickyMinds, 19.5.2008
  79. E. Derby: "Looking Back, Moving Forward Retrospectives Help Teams Inspect and Adapt", StickyMinds.com, September 19, 2007
  80. E. Derby, D. Larsen: Agile Retrospectives. Making Good Teams Great, Pragmatic Programmers, 2006
  81. R. Dixon: Open Source Software Law, Artech House, 2004
  82. P. Donzelli: "A Decision Support System for Software Project Management", IEEE Software, pp. 67-75, July/August 2006
  83. P. Ensworth: The Accidental Project Manager: Surviving the Transition from Techie to Manager, John Wiley and Sons, 2001
  84. K. Ewusi-Mensah: Software Development Failures: Anatomy of Abandoned Projects, The MIT Press, 2003, free online book for ACM members
  85. R. E. Fairley, M.J. Willshire: "Why the Vasa Sank: 10 Problems and Some Antidotes for Software Projects", IEEE Software, pp. 18 - 25, March/April 2003
  86. R. I. Faulconbridge, M. J. Ryan: Managing Complex Technical Projects: A Systems Engineering Approach, Artech House, 2003, free online book for ACM members
  87. A. Friedlein: Web Project Management, Morgan Kaufmann Publisher, 2001
  88. R. T. Futrell, D.F. Shafer, L.I. Shafer: Quality Software Project Management, Prentice Hall, 2002
  89. R. Galen: Software Endgames: Eliminating Defects, Controlling Change, and the Countdown to On-Time Delivery, Dorset House, 2005
  90. T. Gilb: Evolutionary Project Management: Controlling Complexity, Communicating Clearly, Challenging Creativity, Addison Wesley 2003
  91. F.P. Ginac: Creating High Performance Software Development Teams, Prentice Hall, 2000
  92. R.L. Glass: Computing Calamities: Lessons Learned from Products, Projects, and Companies That Failed, Prentice Hall, 1999
  93. R.L. Glass: "Short-Term and Long-Term Remedies for Runaway Projects", Communications of the ACM, pp. 13 - 15, July 1998
  94. R. L. Glass: Software Runaways - Lessons Learned from Massive Software Failure, Prentice Hall, 1998
  95. W.B. Goethert, E.K. Bailey & M.B. Busby: Software Effort & Schedule Measurement: A Framework for Counting Staff-Hours and Reporting Schedule Information, CMU/SEI-92-TR-21
  96. A Guide to the Project Management Body of Knowledge (PMBOK® Guide), Project Management Instinute
  97. D. Haith: "The Agile retrospective. A Healthy Pit Stop for High Performing Teams", iterations, Number Six, Volume Two, Issue Three, July 2007
  98. P. Hall:"Exploring Project Priorities", StickyLetter, February 7, 2007
  99. J. Hallows: Information Systems Project Management, AMACOM 1998, free online book for ACM members
  100. K. T. Hansen: "Project Visualization for Software", IEEE Software, pp. 84-92, July/August 2006
  101. J. Henry: Software Project Management: A Real-World Guide to Success, Addison-Wesley, 2004
  102. W.S. Humphrey: Winning with Software (An Executive Strategy), Addison-Wesley, 2002
  103. W.S. Humphrey: Managing the Software Process, Addison-Wesley, 1989
  104. C. Iacovou, A.S. Dexter: "Surviving IT Project Cancellations", Communications of the ACM, pp. 83 - 86, April 2005
  105. P. Jalote: Software Project Management in Practice, Addison-Wesley, 2002
  106. P. Jalote: CMM in Practice: Processes for Executing Software Projects at Infosys, Addisson-Wesley (www.awl.com), 2000
  107. B. Jiang: "Key Elements of a Successful Project Manager", Project Management, pp. 14 - 19, Vol. 8, No. 1, 2002
  108. C. Jones: "Patterns of large software systems: Failure and success", IEEE Computer, March 1995
  109. C. Jones: Patterns of Software System Failure and Success, International Thomson, 1996
  110. M. Jørgensen, G.J. Carelius: ”An Empirical Study of Software Project Bidding”, IEEE Transactions on Softwrae Engineering, pp. 953 - 969, December 2004
  111. N. Karten: Managing Expectations. Working with People Who Want More, Better, Faster, Sonner, NOW!, Dorset House, 1994
  112. M. Keill, D. Robey: "Blowing the Whistle on Troubled Software Projects", Communiations of the ACM, pp. 87 - 93, April 2001
  113. C. Keith: "Get in the Game. Agile Lessons from Video Game Developers.", Better Software, pp. 24 - 27, November 2006
  114. K. Kelly: Out of Control: The Rise of Neo-Biological Civilization, Addison-Wesley, 1994, available online
  115. R. B. Kelsey: Chaos and Complexity in Software, Challening the Industry and the New Science, Nova Science Publishers, 1999
  116. R.M. Kesner: The Hands-On Project Office: Guaranteeing ROI and On-Time Delivery, Auerbach Publications, 2003, free online book for ACM members
  117. M. Kozak-Holland: Avoiding Project Disaster: Titanic Lessons for IT Executives, Multi-Media Publications, 2006
  118. M. Kozak-Holland: Titanic Lessons for IT Projects, Multi-Media Publications, 2004
  119. P. A. Laplante, ed.: Keys to Successful Software Development: Selected Readings, IEEE Computer Society, 1999
  120. S. Lazenby: Test-Drive Project Management, Glenayre Technologies, May 19, 2004
  121. D.R. Lindstrom: "Five Ways to Destroy a Development Project", IEEE Software, pp. 55 - 58, September 1993
  122. T. Little: "Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty", IEEE Software, pp. 48-54, May/June 2006
  123. A. Longman, J. Mullins: The Rational Project Manager:. A Thinking Team’s Guide to Getting Work Done, John Wiley & Sons, 2005
  124. T. Mackinnon: "Retrospective agility – have you learned anything?", ObjectiveView Issue #8, Ratio Group, pp. 10 - 17, 2006
  125. R. Mascitelli: Building a Project-Driven Enterprise: How to Slash Waste and Boost Profits Through Lean Project Management, Technology Perspectives, 2002
  126. S. McConnell: Professional Software Development: Shorter Schedules, Higher Quality Products, More Successful Projects, Enhanced Careers, Addison-Wesley, 2003
  127. S. McConnell: "Achieving Leaner Software", IEEE Software, November/December 1997
  128. P.A. McQuaid: "Rapid Application Development: Project Management Issues to Consider", Software Quality Professional, June 2001
  129. U. Merz: "Your Authentic Swing" (articel about coaching in projects), Software Development, pp. 53 - 55, August 2002
  130. P.W. Metzger: Managing a Programming Project, Prentice-Hall, 1981
  131. E. Miranda: Running Successful Hi-Tech Project Office, Artech House, 2003
  132. J. Mudhol: Round Table on Project Management, Dorset House, 2001
  133. T. Mochal, J. Mochal: Lessons in Project Management, Apress, 2003
  134. K. Moløkken-Østvold:, M. Jørgensen "A Comparison of Software Project Overruns - Flexible versus Sequential Development Models", IEEE Transactions on Software Engineering, pp. 754 - 766, September 2005
  135. P. Nesi: "Managing OO Projects Better", IEEE Software, July/August 1998
  136. F. O'Connell: How to Run Successful Projects III: The Silver Bullet, Addison Wesley, 2002
  137. F. O'Connell: How to Run Successful High-Tech Project-Based Organizations, Artech House Publishers, 1999
  138. D.S. Olson, C.L. Stimmel: Manager Pool: Patterns for Radical Leadership, Addison-Wesley, 2002
  139. M.A. Ould: Strategies For Software Engineering: The management of Risk and Quality, John Wiley & Sons, 1990
  140. E. Oz: "When Professional Standards are Lax. The CONFIRM Failure and its Lessons.", Communications of the ACM, October 1994
  141. L. J. Peter: Getting Results from Software Development Teams, Microsoft Press, 2008
  142. D. Phillips: Software Project Manager's Handbook. Principles that Work at Work., IEEE Computer Society, 200
  143. M. Pittman: "Lessons Learned in Managing Object-Oriented Development", IEEE Software January 1993
  144. M. Poppencieck: "Wicked Problems", Software Development, pp. 72 - 75, May 2002
  145. C. Pritchard: The Project Management Communications Toolkit, Artech House, 2004
  146. N. Potter, M. Sakry: "We Must Overcommit - We Must Win Business", Software Quality Professional, pp. 4 - 14, March 2005
  147. Practical Software Measurement: A Foundation for Objective Project Management, Practical Software & Systems Measurement , DoD and US army sponsored group
  148. A. Pukinskis: "Better Agile Retrospectives", theagileblog, Nov 16, 2005
  149. L.H. Putnam, W. Myers: Controlling Software Development. Executive Briefing, IEEE Computer Society Press, 1996
  150. L.H. Putnam, W. Myers: Measures for Excellence. Reliable Software on Time, within Budget, Yourdon Press, 1992
  151. P. F. Rad: The Advanced Project Management Office, Aurebach, 2002
  152. J.B. Rainsberger: "Personal Planning",IEEE Software, pp. 16-17, January/February 2007
  153. J.J. Rakos: Software Project Management for Small to Medium Sized Projects, Prentice-Hall, 1990
  154. F. Redmill: Software Projects. Evolutionary vs. Big-Bang, John Wiley, 1997
  155. N. Reizer, Nancy Wang: Juggling Concurrent Releases. Dividing your attention between past, present, and future, (topic: how to manage testing projects) Sticky Letter. 2.2.2005
  156. D. J. Reifer: Tutorial: Software Management, IEEE Computer Society Press
  157. J. Richardson, W. Gwaltney: Ship it! A Practical Guide to Successful Software Projects, The Pragmatic Programmers, June 2005
  158. H. Rittel, M. Webber: Wicked Problems, Righteous Solutions, Prentice Hall, 1990
  159. S. Robertson, J. Robertson: Requirements-Led Project Management : Discovering David's Slingshot, Addison-Wesley, 2004
  160. J. Rothman: "Are We There Yet? Creating Project Dashboard to Display Project Progress", Better Software, pp. 22 - 28, January 2006
  161. J. Rothman: "Beyond Tool Use" (the article is about hiring for a project), Software Development, pp. 49 - 51, October 2002
  162. J. Rothman: "No More Meeting Mutinies", Software Development, pp. 59 - 60, March 2002
  163. J. Sandred: Managing Open Source Projects, Wiley, 2001
  164. P. Schulte: Complex IT Project Management, Aurebach 2003
  165. S. Sinofsky: "What do managers do and how big should my team be?", Micorsoft TechTalk, 24.9.2004
  166. K. Schneider, J-P von Hunnius: "Experience in Implementing a Learning Organization", Software, pp. 46 - 49, May/June 2002
  167. K. Schwaber: Agile Project Management with Scrum, Microsoft Press 2004
  168. J.F. Smart: "Test-based Project Progress Reporting", StickyMinds, 5.4.2006
  169. P. G. Smith: Flexible Product Development: Building Agility for Changing Markets, Jossey-Bass, 2007, for more info
  170. P.G. Smith & D.G. Reinersten: Developing Products in Half the Time, VanNostrand Reinhard
  171. R.B Smith: "Red Flags, Blue Lessons" (weak signals of project problems), Software Development, pp. 50 - 52, May 2005
  172. J. M. Smith: Troubled IT Projects: Prevention and Turnarounds, Institution of Electrical Engineers, 2001, free online book for ACM members
  173. J. Spolsky: "Still gambling on project scheduling? Learn how you can beat the odds.", Better Software, pp. 22 - 26, March 2007
  174. J. Spolsky: "Bionic Office", 24.9.2003 (an interesting example of software developers' office), http://www.joelonsoftware.com/articles/BionicOffice.html
  175. R. van Solingen, E. Berghout, F. van Latum: "Interrupts: Just a Minute Never Is", IEEE Software, pp. 97 - 103, September/October 1998
  176. A. Stellman, J. Greene: "Quick-Kill Project Management", Dr. Dobb's Journal, pp. 44 - 48, August 2006
  177. G. Stepanek: "Why Software is Different", The Code Project/Book chapters, 8 Feb 2006
  178. G. Stepanek: Software Project Secrets: Why Software Projects Fail, Apress, 2005
  179. R. D. Stutzke: Estimating Software-Intensive Systems : Projects, Products, and Processes, Addison-Wesley Professional (SEI Series in Software Engineering, book’s companion web site), 2005
  180. E. Sullivan: Under Pressure and On Time, Microsoft Press 2001 (good info about hiring and project organization, chapters 1 - 3)
  181. J. Tabaka: "How Knowledge-Creating Teams Use Physical Space", (a good article about software developers' office arrangements), Better Software, pp. 23 - 29, October 2006
  182. J. Tabaka: Collaboration Explained: Facilitation Skills for Software Project Leaders, Addison Wesley Professional, 2006
  183. K. Tate: Unsustainable Software Development and its Causes, Addison Wesley Professional, 2005
  184. K. Tate: Sustainable Software Development: An Agile Perspective, Addison Wesley Professional, 2005
  185. S.D. Teasley, et.al.: "Rapid Software Development through Team Collocation", IEEE Transactions on Software Engineering, pp. 671 - 683, July 2002
  186. R. H. Thayer: Tutorial: Software Engineering Project Management, IEEE Computer Society Press, 1997
  187. R. Thomsett: Radical Project Management, Prentice Hall PTR, 2002
  188. K. Thompson: "People Projects: Psychometric Profiling", CrossTalk, April 2003
  189. P.C. Tinnirello, ed.: New Directions in Project Management, Auerbach Publications, 2001
  190. P.C. Tinnirello, ed.: Best Practices Series: Project Management., Auerbach, 2000
  191. S. Tokey: Return on Software, Addison-Wesley, 2005
  192. F. Tsui: Managing Software Projects, Jones and Barlett Publishers, 2004
  193. W. C. Wake, Some Patterns for Iteration Retrospectives, Sep, 2005
  194. D. Wallace, I. Raggett, J. Aufgang: Extreme Programming for Web Projects, Addison Wesley, 2003
  195. E. van Waning: Software Lifecycle Management and Christopher Columbus Predictability in software development, QSM, 2005
  196. M. Watson: Managing Smaller Projects: A Practical Approach, Multi-Media Publications, 2006
  197. K.I. Watson: “COCOMO as a Schedule Prognosis and Validation tool: Case Study”, Software Quality Journal, December 1992
  198. D. R. Webb, D. Tuma: "Personal Earned Value: Why Projects Using the Team Software Process Consistently Meet Schedule Commitments", Digital CrossTalk, March 2005
  199. T. Wells: Dynamic Software Development: Managing Projects in Flux,  Auerbach, 2002
  200. N. Whitten: Managing Software Development Projects, John Wiley & Sons, 1995
  201. KE. Wiegers: " ...2...1... Liftoff!", Better Software, pp. 47 - 48, November 2007
  202. K E. Wiegers: Practical Project Initiation: A Handbook with Tools (Pro - Best Practices), Microsoft Press, 2007
  203. K. Wiegers: "Are We There Yet?" (article about release criteria), Software Development, pp. 26 - 29, June 2005
  204. R. K. Wysocki: Adaptive Project Framework: A Common Sense Approach to Managing Complex Projects, EII Publications, 2006
  205. R. K. Wysocki, R. McGary: Effective Project Management: Traditional, Adaptive, Extreme, Wiley, 2006
  206. R.K. Wysocki: Project Management Process Improvement, Artech House, 2004
  207. R. K. Wysocki: "Adaptive Project Framework: A Common Sense Approach to Managing Complex Projects", gantthead.com, June 30, 2003
  208. S. Woodward: "Evolutionary Project Management", IEEE Computer, pp. 49 - 57, October 1999
  209. R.K Wysocki, R. Beck: Effective Project Management. How to Plan, Manage, and Deliver Project on Time and Within Budget, John Wiley & Sons, 1995
  210. D. Youli: Making Software Development Visible. Effective Project Control, Wiley, 1990
  211. E. Yourdon: Managing High-Intensity Internet Projects, Prentice Hall, 2002
  212. G. P. Zachary: Showstopper. The Breakneck Race to Create Windows NT and the Next Generation at Microsoft, Free Press, 1994
  213. Developing Object-Oriented Software. An Experience-Based Approach, (by team members of IBM Object-Oriented Technology Center), Prentice Hall, ISBN 0-13-737248-5, 1997)


Finnish books - Suomenkielisiä kirjoja kirjoja
  1. S. Berkun: Projektinhallinnan taito, Readme.fi, 2005
  2. P. Forselius, M. Karvinen, M. Kosonen: TiVi-projektien johtaminen, Talentum, 2005
  3. L. Forsman: Atk-projektin läpivienti, Suomen Atk-kustannus Oy
  4. S. Kettunen: Onnistu projektissa, WSOY Yritysjulkaisut, 2003
  5. O. Lind: Näin tehdään onnistunut projekti, Ruotukka Oy, 2001, http://www.mediamikkeli.fi/ollilind/
  6. S. McConnell: Ohjelmistoprojektin selviytymisopas, Suomen atk-kustannus, 1997
  7. P. Mäkelä, H. Stenlund: Projektijohtaminen: Toiminnanohjaus verkostotaloudessa, 1995
  8. H. Niemi: Tietojärjestelmäprojekti: Tietojärjestelmän kehittämisen suunnittelu ja ohjaus, Valtion painatuskeskus, 1993
  9. R. Pelin: Projektinhallinnan käsikirja, Projektinjohtaminen Oy Risto Pelin, 2008
  10. K. Ruuska: Pidä projekti hallinnassa, Talentum Oy, 2005
  11. M. Sell: Projektin ohjaus, Suomen atk-kustannus, 1975
  12. P. Silfverberg: Ideasta projektiksi: projektisuunnittelun käsikirja, Edita, 1996
  13. P. Virkki & A. Somermeri: Projektityö - kehittämisen moottori, Painatuskeskus Oy, 1992
  14. P. Virtanen: Projektityö, WSOY Yritysjulkaisut, 2000