Skip to Main Content
Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise
book

Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise

by Scott W. Ambler, Mark Lines
May 2012
Intermediate to advanced content levelIntermediate to advanced
544 pages
15h
English
IBM Press
Content preview from Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise

Chapter 9. Identifying an Initial Technical Strategy

The most effective way to deal with technical debt is to avoid it in the first place.

Early in a Disciplined Agile Delivery (DAD) project you need to have at least a general idea of how you’re going to build the system, or in some cases several good options to proceed. Is it a mainframe COBOL application, a .Net application, enterprise Java, something else, or combinations thereof? During the Inception phase the key developers on the team, ideally everyone on the team at that point, identify one or more potential architectural strategies that supports the stakeholder goals for the solution. Despite what some core agilists suggest, surveys show that most teams spend some time modeling their ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Start your free trial

You might also like

Managing Software Requirements the Agile Way

Managing Software Requirements the Agile Way

Fred Heath

Publisher Resources

ISBN: 9780132810098Purchase book