Home

Our Services

Assessments

Consulting

Training

Quality Assurance

Our Way of Working

FAQ

Articles

Web-based Services

About Us

Contact

Google
Web Q-Success.com

 

Q-Success
Software Quality Management Consulting

English
Deutsch

Software Process Improvement Bibliography by Q-Success

Back to category overview

Our book recommendations on Software Process Improvement

Introduction to the Personal Software Process(sm)
Watts S. Humphrey, 1996

Look up this book at
Amazon.com
Amazon.ca
Amazon.co.uk
Amazon.de
Amazon.fr

The Personal Software Process (PSP) is process improvement at a personal level, i.e. a technique for the individual software developer to improve his/her way of working. An interesting concept, great success stories featured, though most of the time quite difficult to implement. If you are looking for something beyond the organization-wide process for improvement, read this.

Introduction to the Team Software Process(sm)
Watts S. Humphrey, Marc Lovelace, 1999

Look up this book at
Amazon.com
Amazon.ca
Amazon.co.uk
Amazon.de
Amazon.fr

One point often criticized in CMM, is that it does not sufficiently address soft-issues in software development. Humphrey always recognized that the process is only one of the important aspects, and concentrated in the last years solely on the issues arising when working in a team. He reports extremely positive results with the methods described in the Team Software Process.

Peopleware: Productive Projects and Teams
Tom DeMarco, Timothy R. Lister, 2000

Look up this book at
Amazon.com
Amazon.ca
Amazon.co.uk
Amazon.de
Amazon.fr

If you consistently fail to hammer the right processes into your staff's heads, perhaps you should try a slightly different approach when dealing with people. It's a safe bet, that you won't be disappointed by these two great authors.

Why Does Software Cost So Much? And Other Puzzles of the Information Age
Tom DeMarco, 1995

Look up this book at
Amazon.com
Amazon.ca
Amazon.co.uk
Amazon.de
Amazon.fr

A book you can easily read in-between all the heavy, classical ones. It is entertaining and one of those books the software engineers want their senior managers to read. The better ones even do.