by Mike Vincent

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.

————————————————————————————————————————————————————————————————

Mike Vincent is a veteran software entrepreneur based in Orange County, California and Kona, Hawaii. He currently provides clients throughout North America with application lifecycle management training, Scrum coaching, and enterprise/solution architecture consultation primarily focusing on Microsoft technologies. He has been in the software business for over 30 years in addition to marketing management and construction management positions. Actively involved in the user group community since the early 90’s, Mike is a frequent presenter at developer events including Microsoft TechEd and PDC. He is a Visual Studio Application Lifecycle Management MVP, Professional Scrum Master, Scrum Product Owner, Scrum Developer and Scaled Professional Scrum Trainer.