Resources - Books

Introduction to Disciplined Agile Delivery describes how the team develops the first release of a mission-critical application while working in a legacy enterprise environment. It describes their experiences from beginning-to-end, starting with their initial team initiation efforts through construction and finally to deploying the solution into production. It also describes how the team stays together for future releases, overviewing their process improvement efforts from their Scrum-based beginnings through to a lean continuous delivery approach that fits in with their organization's evolving DevOps strategy.

 

MORE on this Book

Buy this Book - Amazon U.S.

Buy this Book - Amazon Canada

Buy this Book - Amazon U.K.

Disciplined Agile Delivery:

A Practitioner's Guide to Agile Software Delivery in the Enterprise

by Scott W. Ambler and Mark Lines

In writing the book on DAD, Scott and Mark focused on a describing a pragmatic approach to being agile.  An alternative approach could have been to describe “how to do agile” planning, modeling, requirements, etc. which could have come off as dogmatic and prescriptive.  Or they could have shown all the agile practices described elsewhere, and said “you choose”.  Other methods that have tried to provide guidance to every possible situation have in the past proven to be overwhelming and difficult to adapt.

MORE on this Book

Buy this Book - Amazon U.S.

Buy this Book - Amazon Canada

Buy this Book - Amazon U.K.

The Enterprise Unified Process:

Extending the Rational Unified Process

by Scott W. Ambler, John Nalbone, and Michael Vizdos

Whereas the RUP defines a software development lifecycle, the EUP extends it to cover the entire information technology (IT) lifecycle. The EUP extends the RUP to include the operation and support of a system after it is in production and its eventual retirement. Furthermore, because all but the smallest organizations have more than one system, the EUP also handles cross-system enterprise issues such as portfolio management, enterprise architecture, and strategic reuse. Although the RUP defines a very good software development lifecycle, it is only a start: you need the EUP to address the entire IT lifecycle and to provide a mechanism for true IT governance of RUP projects.

Buy this Book - Amazon U.S.

Buy this Book - Amazon Canada

Buy this Book - Amazon U.K.

A database refactoring is a small change to your database schema which improves its design without changing its semantics (e.g. you don't add anything nor do you break anything).  The process of database refactoring is the evolutionary improvement of your database schema so as to improve your ability to support the new needs of your customers, support evolutionary software development, and to fix existing legacy database design problems.

 

 

Buy this Book - Amazon U.S.

Buy this Book - Amazon Canada

Buy this Book - Amazon U.K.

Refactoring Databases:

Evolutionary Database Design

by Scott W. Ambler & Pramod J. Sadalage

© 2015 Scott Ambler + Associates