Design after Agile: How to Succeed By Trying Less

Joe Lane edited this page Sep 7, 2018 · 2 revisions

Abstract

The agile movement is an important and welcome corrective to Big Design Up Front models like the waterfall model. But the manifesto does not even mention the words "architecture" or "design", and people often fill this void with heroic and costly effort.

Without design, agile methods will flounder when they encounter novel problems. This talk will augment agility with some principles for designing systems. Along the way you will see

  • how to make "working design" a valuable deliverable
  • the tools of the trade (hint: not code!)
  • processes that you can employ to improve your skills
  • stories from real projects: good, bad, and ugly
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.