Man and Project Management

Peopleware - Productive Projects and Teams, by Tom DeMarco and Timothy Lister, Dorset House 1987. This exceptional book explains how to get the best (or the worst!) from the people who are your key development resource, with good practices for building and managing productive teams. If s very readable. DeMarco & Lister also do occasional public courses based on the same material, which I can wholeheartedly recommend.

Debugging the Development Process, by Steve Maguire, Microsoft Press 1994. Following on from Writing Solid Code, this looks at a range of management issues in typical software development processes, and presents advice based on practical experience at Microsoft.

The Mythical Man-Month, by Frederick P. Brooks, J., Addison-Wesley 1975 & 1995. This is the classic text on software project management. The technology is rather out of date now, but the ideas on team structure are still fine, and if s still one of the best basic texts on the importance of a well-structured design.

AntiPatterns, by William J Brown, Raphael C. Malveau, Hays W. "Skip" McCormick III and Thomas J Mowbray, Wiley 1998. Antipatterns are the opposite of patterns - common ways in which things can go wrong. This often-amusing book identifies a number of common AntiPatterns in development processes, architecture and management, and offers some suggestions on how they can be addressed. If you think you're failing, and you're not sure why, this is a good place to start.

The Politics of Projects, by Robert Block, Ashgate Publishing Group 1983. Explains the political and "people" problems which cause developments to fail, and how to read the politics of a management situation and exploit it to maximise your chances of success.

Principles of Software Engineering Management, by Tom Gilb, Addison-Wesley 1988. A great book full of ideas, in particular how to structure a development into phases and what to deliver when. Very good on risk management, project structure and estimating. The terminology and details of some methods are a bit clumsy, particularly in the latter part of the book, so it does need to be "interpreted" to fit in with your own development methods.

Controlling Software Projects, by Tom DeMarco, Prentice Hall 1982. This book concentrates on methods of measuring and estimating software development. If you want to get really good at estimating in an organisation that will do a number of similar developments, then this book is essential.

Making it Happen, by John Harvey-Jones, Fontana 1988. Not really about software, but an excellent text on the problems of man management from someone who's proven he knows how to do it properly!

Make It So, by Wess Roberts Ph.D. and Bill Ross, Pocket Books 1995. Put into the words of Captain Jean-Luc Picard, and illustrated with incidents from episodes of Star

Trek - the Next Generation, this is a series of essays on common management issues and how to tackle them. It s amusing, especially if you're a Trekkie, but the management advice is sound and valuable.

Wicked Problems, Righteous Solutions, by Peter DeGrace and Leslie Hulet Stahl, Prentice Hall 1990. This book looks at various project structures and development methods, and explains their strengths and weaknesses. In particular it looks at those classes of problem which will not be satisfactorily analysed by traditional methods, and proposes alternative ways to their resolution.

Decline and Fall of the American Programmer, by Edward Yourdon, Prentice Hall 1993. A book which tries to explain why the typical programmer (and project) is not adopting those methods which would make life easier, and what the results may be. It includes a clear explanation of steps the author believes must be taken by software producers to remain competitive.

Rise & Resurrection of the American Programmer, by Edward Yourdon, Prentice Hall 1996. A follow-up to the previous book, this is more up-beat. It describes how the software development business continued to thrive through the 1990s, and the practices that enabled it to do so.

Death March, by Edward Yourdon, Prentice Hall 1997. Some software projects, usually larger ones, become "mission impossible" projects, and seem doomed to failure even despite enormous efforts from all involved. Yourdon describes this phenomenon, and then offers some practical advice on how to avoid or address it.

Software Project Management - A Practitioner's Approach, by E. M. Benettan, McGraw Hill 1992. An excellent book with a similar scope to this one, although the style is quite different being targeted at more senior managers. If s very good on formal and "public domain" standards, and on structured methods of estimation, but is not so strong on things like design and testing, being a bit prescriptive rather than explaining why some approaches are advised.

The Secrets of Consulting - A Guide to Giving & Getting Advice Successfully, by Gerald M. Weinberg, Dorset House 1985. Not only for consultants, this is full of excellent advice for anyone who wants to identify problems, propose solutions or make changes in any sort of business.

Software Project Survival Guide, by Steve McConnell, Microsoft 1998. This is a very helpful book with a similar scope to this one, providing practical advice for each stage in software development.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment