Architects and designers

Why do you need an architect or designer on your software project?

Writing reusable code is the heart of the DRY principle. However it is important to reuse the correct code.

A picture, as they say

plug animation

Technical Debt and Dependency hell can quickly create big issues and slow a project to a crawl. This can be avoided if a great architect and design steps are involved before the project starts. Often refactoring code will be required to make modules or functions loosely coupled and less dependent on each other.

Even within a Scrum and Agile framework, it is better to have a clear view of the end result and understand how the new 'thing', will interface with the existing 'stuff'.