Agile architects should code, yes they should produce code as any other development team member. Agile architects should serve their organization, not vendors so they must create solutions that could easily change frameworks, libraries, products whenever they think necessary. They must care about their organization proffit not vendors. If you think your software products can switch web-frameworks, databases, storage formats, libraries and frameworks in a controlled and verifiable way, then your company is in the right track. If not, I can help your teams to do just that.
Want to know more? Check out how this service is usually delivered, problems it helps you to solve, and benefits gained.
This service helps you solve or alleviate the following situations
- There is no common understanding of your solutions internal structure and developers tend to put any code anywhere.
- Your software products do not scale well with business needs. They are built to rigid and is difficult to accommodate novel requirements.
- Your software assets are two tightly coupled with packages and products from vendors, increasing your the risk of unexpected changes on the business model, deprecation, or abandoned products.
Benefits to your organization
- Be able to respond to changes on business needs over a long period of time.
- Reduce vendors related risk.
How this service is usually delivered
- By teaching your teams agile architecture principles.
- By clearly defining who is responsible for the the architecture in an agile team.
- By conducting architectural audits, alone and with your teams.
- By helping teams in creating solutions using agile architectural principles when they face a new project.
Interested? Request a quote or let me contact you to better understand your needs.