Source : Click Here
This article highlights the best practices to be incorporated in an organization to bring in Agile processes to make Enterprise Architecture function effectively.There seems to be a correlation of successes for enterprise architecture when teams work collaboratively to understand what the architectural vision is and can help actively build it.The key best practice is for the architect to focus on architectural principles and make sure everyone in the team understands it.People then tend to see value in the EA architecture and are able to communicate as well as provide feedback on it.
Another important aspect than just not focusing on communicating is to work towards building an agile process environment.The architects get involved with the team and also attend scrum meetings to give direction and more knowledge on artifacts .This gives the development team the opportunity to address things that are not in accordance with the architectural principles.This also gives a strong focus on architectural requirements and non-functional requirements.
I believe this holds good in lot of cases.In organizations, I have worked previously it is seen that Agile processes are well in place and followed.However this works for project levels or one higher level.They do not work in collaboration and I would say no one thinks or is aware of how it matches with the high level architecture picture.I think these steps might help bring us one step closer to realize the key aspects of minute changes made in the work cycle.
This article highlights the best practices to be incorporated in an organization to bring in Agile processes to make Enterprise Architecture function effectively.There seems to be a correlation of successes for enterprise architecture when teams work collaboratively to understand what the architectural vision is and can help actively build it.The key best practice is for the architect to focus on architectural principles and make sure everyone in the team understands it.People then tend to see value in the EA architecture and are able to communicate as well as provide feedback on it.
Another important aspect than just not focusing on communicating is to work towards building an agile process environment.The architects get involved with the team and also attend scrum meetings to give direction and more knowledge on artifacts .This gives the development team the opportunity to address things that are not in accordance with the architectural principles.This also gives a strong focus on architectural requirements and non-functional requirements.
I believe this holds good in lot of cases.In organizations, I have worked previously it is seen that Agile processes are well in place and followed.However this works for project levels or one higher level.They do not work in collaboration and I would say no one thinks or is aware of how it matches with the high level architecture picture.I think these steps might help bring us one step closer to realize the key aspects of minute changes made in the work cycle.
Interesting article. I still am not sure what to make of Agile. I was always a fan of prototyping when I was a developer and rapid application development has been around for a long time. Saying that models are not needed is a bit overkill, they're still needed but as the article states they can't take weeks to develop. Developing principles are very important but you do still need to limit development platforms. The industry is not moving that quickly unless you are always trying to be on the bleeding edge, which there are less organizations in that boat than those working with proven technology.
ReplyDeleteYou shouldn't have to sacrifice your enterprise planning for a development methodology, I find it funny that evangelists of a particular methodology always seem to think that the rest of the organization needs to change rather than the methodology itself. I believe there is always room for some give and take on both sides.