Software architecture and the balance with agility

The agile and software craftsmanship movements are helping to push up the quality of the software systems that we build. Together they are helping us to deliver better software that better meets the needs of the business while carefully managing time and budgetary constraints. But there's still more we can do because even a small amount of software architecture can help prevent many of the problems that projects face, particularly if the team seems to be more chaotic than they are self-organising. Successful software projects aren't just about good code and sometimes you need to step away from the IDE for a few moments to see the bigger picture. This session is about that bigger picture and is a practical, pragmatic and lightweight introduction to software architecture that is aimed at developers. You'll learn:

  • The essence of software architecture.
  • Why the software architecture role should include coding, coaching and collaboration.
  • The things that you *really* need to think about before coding.
  • How to visualise your software architecture using simple NoUML sketches.
  • A lightweight approach to documenting your software.
  • Why there is *no* conflict between agile and architecture.
  • What "just enough" up front design means.
  • How to identify risks with risk-storming.

Other formats

PDF


    of 104