Abstract: With Scrum and other forms of agile software development we focus on incrementally evolving architecture one sprint or iteration at a time and avoid the potential waste of big design up front. What’s this really mean? We’ll talk about pragmatically doing just enough just in time while delivering a potentially shippable increment of working software every sprint.
So where and when do we plan, and how much? What about the big picture? How does our architecture fit within the enterprise? How does it facilitate our business objectives? How do we manage risk? And, what about all the details? What tools are we using, what standards are we adhering to, how are we managing maintainability and all the other NFR’s? Is everything integrating together nicely? And, what is role of the solution/enterprise architect in an agile world?
This session is all about helping you understand architecture in the world of today’s agile software development.
Learning Outcomes: - Emergent Architecture is an important part of agile development
- Deliver business value each Sprint
- Big design up front is waste, do just enough just in time
- Delay requirements until last responsible moment
- Architects are active members of the development teams
- Work in slices rather than layers
- Choose popular principles, patterns, practices
- Know when you are done
- It takes smart developers to write software
Attachments:
