This book: Provides a foundation for enterprise agility, value streams, and a disciplined approach to DevOps; Is a pragmatic application of agile, lean, and traditional techniques for your enterprise-class environment; Overviews a strategy for teams to evolve a fit-for-purpose, flexible WoW that still supports a consistent governance strategy for leadership; and Makes a perfect study guide for Disciplined Agile certification.

Part of a new four-volume series presenting best practices using UP to develop object-oriented, component-based software, this book examines the second UP phase--elaboration--focusing on defining, validating, and baselining the architecture for a system. Illustrations throughout.

The Unified Process is a development methodology that is geared to the creation of object-oriented component-based software. It is a process that has been developed and promoted by Rational Software, Inc. and the developers of the Unified Modelling Language (UML). The books of this four-volume series are designed to address each of the four phases of the UP process; inception, elaboration, construction, and transition. Each volume will present a collection of best practices that can be used as guidelines in the implementation of the respective phase of development. Editor Scott Ambler has compiled a collection of articles from Software Development magazine that will present the wisdom of industry luminaries such as Steve McConnell, Peter Coad, Larry Constantine, Karl Wiegers, Capers Jones, Martin Fowler, Clemens Szyperski, Meilir Page-Jones, Tom McCabe, Edward Yourdon and many others. This volume, concentrating on the construction phase, will focus on the design and implementation of new systems in an iterative and incremental manner.

Is the Unified Process the be all and end all standard for developing object-oriented component-based software? Scott Ambler doesn't think so. This book is one in a four-volume series that presents a critical review of the Unified Process -- designed to p

Is the Unified Process the be all and end all standard for developing object-oriented component-based software? This book is the second in a four volume series that presents a critical review of the Unified Process. The authors present a survey of the alt