Books

Here are the last  books I wrote, or co-wrote.

• Managing technical debt — Reducing friction in software development, with Robert Nord and Ipek Ozkaya (from the SEI), Pearson Education (2019).

As software systems mature, earlier design or code decisions made in the context of budget or schedule constraints increasingly impede evolution and innovation. This phenomenon is called technical debt, and practical solutions exist. In Managing Technical Debt, three leading experts introduce integrated, empirically developed principles and practices that any software professional can use to gain control of technical debt in any software system.

• Discover how technical debt damages manageability, quality, productivity, and morale–and what you can do about it
• Clarify root causes of debt, including the linked roles of business goals, source code, architecture, testing, and infrastructure
• Identify technical debt items, and analyze their costs so you can prioritize action
• Choose the right solution for each technical debt item: eliminate, reduce, or mitigate
• Integrate software engineering practices that minimize new debt

And much older

• The Rational Unified Process Made Easy: A Practitioner’s Guide to the RUP with Per Kroll, Addison-Wesley Pearson Education (2003).

The Rational Unified Process (RUP) is a software engineering process developed and marketed by Rational Software Corporation. The RUP comprises a host of software development best practices collected from a number of contributors, over many years, and across a wide variety of situations. The RUP is popular because it provides a disciplined approach to assigning and managing tasks and responsibility to ensure success in a software project. In this new book, the industry’s leading RUP experts borrow from their significant experience and insider knowledge to teach you how to apply the RUP and succeed with it. The reader will discover what works, and what doesn’t, as well as specific advice on how and when to apply the RUP. Overall, the reader will gain knowledge of how the RUP impacts their job, and how this process can benefit their organization.

This is more or less the last thing I did with Rational Software before its acquisition by IBM, and my departure.

Also in the

• The Rational Unified Process: An Introduction (3rd Edition), Addison-Wesley Pearson Education (2003)

The original RUP book, still going strong, actually.  A much decried piece by many agilistas, who consider this as the typical example of what not to do (but then, they usually have not read the book!). Available in 11 languages (see some pointers below).

Also a .

• Software Engineering Processes: with the UPEDU, with P. Robillard and P. d’Astous (2002)

A very simple version of RUP, intended for education purposes, witten mostly by Pierre Robillard, prof at the Ecole Polytechnique, part of the Université de Montréal.

In Japanese, translated by Taku Fujii:

• Rational Unified Process–An Introduction (3rd edition),
• The Rational Unified Process Made Easy: A Practitioner’s Guide to the RUP