This newest book from Watts Humphrey is a hands-on introduction to basic disciplines of software engineering. Designed as a workbook companion to any introductory programming or software-engineering text, Humphrey provides here the practical means to integrate his highly regarded Personal Software Process (PSP) into college and university curricula. The book may also be adapted for use in industrial training or for self-improvement by practicing software engineers.
Applying the book's exercises to their course assignments, students learn both to manage their time effectively and to monitor the quality of their work, good practices they will need to be successful in their future careers. The book is supported by its own electronic supplement, which includes spreadsheets for data entry and analysis. A complete instructor's package is also available.
By mastering PSP techniques early in their studies, students can avoid--or overcome--the popular "hacker" ethic that leads to so many bad habits. Employers will appreciate new hires prepared to do competent professional work without, as now is common, expensive retraining and years of experience.
This is a great process for engineers to polish their estimation skills. IF they do what is recommended it will hone the ability to estimate work better and better as time goes on. I have seen reviews saying this is only for waterfall and that is nonsense. We have been an actual agile team on and off SAFe projects but always agile and we do a great job of actually being right within about 10% when we give an estimate.
Given how utterly crap filled the estimates we get from vendors and subcontractors with 'oodles' of experience are they could benefit from some of the basics taught here.
If you are too good to learn or never have to mentor junior folks than go buy a dilbert book. If you have need to be able to both depend on and have dependable estimates look into this book. It's not the only way of course but it is laid out so simply that it's hard to screw up. And yes, you will be doing record keeping as you progress.
Rather than being a general introduction to PSP, this book is apparently intended to introduce it to first-year university students - something I wish I'd known before I bought the book.
To be honest, either the author is expecting some particularly dim students, or he's aiming a bit younger than CS101 - some of the book felt like it was lecturing high school students. As a result, for anyone with much professional experience, the book is annoying and patronising and focuses rather heavily on stating the obvious.
PSP itself, based on this description, seems to have as its key attribute the layering of large amounts of individual record-keeping on top of a waterfall methodology. As such, it feels leaden, process-heavy and hopelessly out of date - providing a classic example of why a more modern Agile view is so appealing. in comparison to the sessile model portrayed here.
A great book designed to teach the undisciplined software writers of the world why it is important to manage the development cycle. It provides some decent but outdated tools for managing the process (most programmers would use online systems instead of paper based reporting for example.)
It still provides great information and is very short.
Watts Humphrey has taken the CMM and made it effective on the personal level. This is about being more productive and seeing metrics to show how to be more productive. If used, this technique will definitely make an impact.