Sessions at Software Architect 2011 about Agile on Thursday 20th October

Most of the time when people talk about agile software development, they talk about project and planning practices but never mention actual development, as if development were an afterthought when writing software. This talk drills into the real details of how to do agile development. I discuss best practices like continuous integration, pair programming, how developers should interact with story cards, how to handle enterprise concerns like integration with other software packages, and a slew of other topics related to agile software development.

This session examines the principles and practices underpinning rapid software development models (RAD, Agile, Lean & Iterative etc.) and considers the implications, enhancements and options for Technical Architects in their role to design (and deliver) software architectures & solutions to meet the ever-increasing challenges of modern day functionality and “ilities”. In doing so, this session examines the business case for rapid development approaches, the business case for quality and the “ilities” as well as size, scope & complexity of a project. In addition, this session covers various pros and cons for rapid development and the role of the Technical Architect. This session is targeted at developers and architects of all levels.

This talk focuses on the architectural and developmental differences between the old-style BDUF (Big Design Up Front) versus the modern iterative approach to database design.
Databases have been a part of the computing landscape since the beginning, and database administrators have been around almost as long. Their background and culture can be an impedance mismatch with modern Agile processes and practices. But it doesn’t have to be. This session explains the problems and solutions from both a process as well as practices standpoint, through a combination of presentation and demonstration.