103 Rules for Leading Engineers
You do not need to be the smartest person in the room.
Software engineering judgement: architecture, code, testing, releases, reliability, incidents, security, developer tools and AI-assisted work.
Get it finished. Not just nearly finished.
Purchase links will be added when this title is available.
103 Rules / Leadership Series / 05Plenty of projects reach 'nearly finished' on time. The expensive part is the distance from there to the first ordinary day when the people receiving the result can use it without ringing anyone who built it, which is where the budget, the patience and the original date tend to run out.
103 Rules for Project Leaders is for anyone accountable for getting a defined piece of work delivered, whatever their job title. In short, practical chapters it follows a project from start to finish: the problem behind the request, a scope that survives its first workshop, estimates that don't harden into promises by accident, steering groups that decide things, status reports a sponsor can act on, suppliers, late projects, and the handover that turns a launch into a result.
People accountable for a defined project outcome.