program selection system

The phrase clean code encapsulates a philosophy of coding and specific principles that improve code quality and extensibility. These principles include the importance of code that clearly expresses its intent and the effective use of encapsulation and abstractions to isolate details appropriately. What about at the architecture level? Can systems be clean?

Have you ever been told “Agile works great for UI, but just doesn’t work for large scale systems architecture”? In this experience report, I will review a real world project to redesign a successful large scale ecommerce system that became plagued with growing pains. After the team initially ran to the comfort of a long term waterfall project, cost overruns and escalating problems necessitated a new approach. Enter in Scrum and a focus on iterations and frequent customer feedback, and a once failed project turned into a blazing success.

Our organization just ended a successful pilot project using agile methods. As a result management has decided to introduce agile across IT. There are still questions about adopting agile across the organization:

• Who will ensure we have the “right” architecture for our future needs?
• Who is responsible for software quality reuse?
• Does agile work large-scale projects
• Who will focus on the big picture?

This talk will present patterns and methods about how an agile organization manages architecture concerns.