Software Project Managment Reading List

SOFTWARE PROJECT MANAGEMENT

Reading List for PhD Exams

The software project management exam will cover the following major topics. For each of these areas the reading list includes both books and journal papers. The books are intended to provide overall exposure to the topic, whilst the journal readings describe both seminal and current research findings.

A. Project Management

1. The Project Manager's Guide to Software Engineering's Best Practices, Mark J. Christensen,Richard H. Thayer, IEEE Computer Society Press, 2002.

2. Object Solutions : Managing the Object-Oriented Project (Addison-Wesley Object Technology Series), Grady Booch / Paperback / Published 1995

3. Software Project Management : A Unified Framework (The Addison-Wesley Object Technology Series) Walker Royce / Hardcover / Published 1998

4. Peopleware : Productive Projects and Teams, 2nd Ed. Tom Demarco, Timothy Lister / Paperback / Published 1999

5. Henderson-Sellers, Brian. OO project management: the need for process, IEEE Software. Vol. 14, July/Aug. 1997, p. 96-7.

6. Jones, Capers. Patterns of large software systems: failure and success, Computer. v. 28, Mar. 1995, p. 86-7.

7. Constantine, Larry L. Lockwood, Lucy, A. D., Orchestrating Project Organization and Management. Communications of the ACM. v. 36, Oct. 1993, p. 30-123.

8. DeMarco, Tom. Miller, Ann. Managing large software projects, IEEE Software. v. 13, July 1996, p. 24-117.

9. Jones, Capers, Software management: the weakest link in the software engineering chain, Computer. v. 27, May 1994, p. 10-11.

10. Constantine, Larry L., Work organization: paradigms for project management and organization, Communications of the ACM. v. 36, Oct. 1993, p. 34-43.

B. Risk Management

1. Practical Risk Assessment for Project Management (Wiley Series in Software Engineering Practice), Stephen Grey / Paperback / Published 1995

2. Practical Software Metrics for Project Management and Process Improvement, Robert B. Grady / Hardcover / Published 1992

3. Keil, Mark. Cule, Paul E. Lyytinen, Kalle, A Framework for Identifying Software Project Risks, Communications of the ACM. Vol. 41 No. 11, Nov. 1998, p. 76-83.

4. Boehm, Barry W. DeMarco, Tom, Software Risk Management, IEEE Software. Vol. 14, May/June 1997, p. 17-89.

5. Weller, Edward F. Using metrics to manage software projects, Computer. v. 27, Sep. 1994, p. 27-33.

6. Fairley, Richard. Risk management for software projects, IEEE Software. v. 11, May 1994, p. 57-67.

7. Boehm, Barry W. Software risk management: principles and Practices, IEEE Software. v. 8, Jan. 1991, p. 32-41.

8. Yourdon, Ed. Making death march projects pay off (except from Death march). Datamation. v. 43, Apr. 1997, p. 116-18.

C. Software Development Processes

1. Handbook of Systems Development : 1999, Paul C. Tinnirello(Editor) / Hardcover / Published 1998

2. eXtreme Programming: Embraced, Kent, Addison-Wesley Pub Co; ISBN: 0201616416; 1st edition (October 5, 1999)

3. Jones, Capers. Our worst current development practices, IEEE Software. Vol. 13, Mar. 1996, p. 102-4.

4. Phan, Dien D. George, Joey F. Vogel, Douglas R. Managing software quality in a very large development project, Information Management. Vol. 29, Nov. 1995, p. 277-83.

5. Yourdon, Edward. When good enough software is best, IEEE Software. v. 12, May 1995, p. 79-81.

6. Boehm, Barry. Anchoring the software process, IEEE Software. v. 13, July 1996, p. 73-82.