What is the role of architecture board in agile way of working?
Shweta MishraProduct Owner| T MobilePrague, 10, Czechia
Hello All,
Could you please help me understand how do you work the architecture board?
What is the influence in agile way of working?
Is there a need of the architecture board?
Are they verify all the solutions provided by internal developers/solution architects?
By doing this , are we adding additional process of solution approval by architect board , then implementation?
Have a great day!
Thanks
Shweta Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Agile was born in 1990 totally outside the software world. It was created and defined inside the USA DoD/NSF Agility Forum at Leihigh University. It was created trying to find an alternative to Lean. Because of that Lean and Agile are totally different things. With that said if you take a look to the definition you will find that Agile is a matter of enterprise architecture. Then architecture board is key to implement Agile and achieve the porpuse of implement it: agility. Software and Technology are enablers of Agile to gain into agility then architecture team must help on that. For example, to create architecture to gain into agility some organizations define an strategy based on migrate to cloud all the application layer inside the enterprise architecture. Just to comment, I am leading the implementation of Agile in my actual work place and we are in the last step working with the fine tunning which is about this. Saving Changes...
Architecture (as an activity) is a core element of solution delivery and rather than solely having it as an external contributor to the team, it should be embedded within the team. The team will likely still liaise with an external architecture group (e.g. Enterprise Architecture) to confirm that the solution they are architecting aligns with enterprise standards and to benefit from any reusable assets or roadmaps which that group "owns".
If you review the Disciplined Agile content on architecture, it'll show how the dynamic can work well.
Kiron Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Piggybacking on Kiron's reply, you may want to consider taking the free PMI course, PMI Citizen Developer™ Business Architect: CDBA Introduction.
There is sufficient overlap with Agile and CD architecture to give you a good basis of how you should approach it. Saving Changes...
Think of it more of a community of practice than a governing body. They establish the best practices and review new architectural approaches when necessary.
The architect is embedded with the team, and the team establishes their own WoW. If the team is comfortable with the approach, then they don't need to consult with an outside board. If they need help, then that is their pool of external consultants to help guide their approach. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Sweta,
you may look at https://en.wikipedia.org/wiki/The_Open_Gro...cture_Framework to get an overview of the role of architecture for business success. There are enterprise wide considerations like business, data and technical architectures (which might be comprised to form an architecture board) as well as application specific architecture (which also will have enterprise wide aspects). While the latter can be embedded into one project or one team, the other three domains have to look at the enterprise as a whole, and even beyond if you have partnership networks.
In my projects, we had project specific architects who made sure that project external standards are upheld (or extended as appropriate). Looking at the whole and the parts of it has to be balanced. Architects ensure the consistency and stability of the enterprise as a system. They reduce complexity.
I am sure somebody tries to label architecture with agile to sell their products. Saving Changes...
John AogonProject Manager| IBM UgandaKampala, Uganda
In my work experience on IT projects, Architecture team is required to assess how the new solution/change fits into existing enterprise ecosystem, they examine the current architecture and evaluate business impact that different technical options have and recommend optimal solution based on technical feasibility, effort required and business value. However, the level of involvement of Architecture team depends on the size of the project. Their levels of involvement is defined in the project governance processes Saving Changes...
