September 3, 2015 Leave a comment
An enterprise architecture is a disciplined approach envision to take business from current stage to next stage. It boils down to making sure an organisation’s systems harmoniously work together to meet the business objectives and different views. It is a process of developing capabilities, defining principles and frameworks which helps during implementation.
It is often observed, architecture has slowed down the process of development teams, because they carry bigger picture and had a long-term vision. On the other hand, engineering team have evolved, and they’ve evolve a lot more quickly than architectures. This is because challenges and lessons learned from past deliveries have forced them to evolve and act on business changing needs. I’ll skip other software development cycles for the sake to keep this short. In recent years, agile has improvised the way the software has been delivered – by keeping it simple to deliver what is asked to, deliver in chunks rather than big-bang, deliver what it is required against what was required, easily mitigate the risks, early assessment, dealing with changing requirements. This has helped development to pace up with business, yet with quality delivery.
It is necessary to understand that the starting point when architecture starts to meet business expectations, may have changed at the time they finished. The similar approach to deliver has to be taken by architecture. Today’s architecture cannot deliver business vision based on discussion held few years back. EA should visualise how the process of delivering the facilities to engineer team should streamline and address the ever changing needs and re-evaluate the decisions as requirements change. Although, we are talking about the vision and delivery of vision, the key aspect is how EA can improve their deliverables and keep with the pace of business needs, w/o compromising their goals, principles, guidelines, and meeting common issues. It’s time to transition ourselves naturally and have more engagement with the projects. This will bring more agility in the process.
It seems Agile methodology of delivery projects can help EA to assess the key goals and drivers from time to time. It is tricky how the integration will help so that EA should not over-engineer and delivering what business is looking for and changing their approach based on change requirements. It is important to understand how Agile team will cope up such deliverables when it is not a monolithic project delivery. It’s time to look beyond the horizon and accept the key challenge of ever changing and define the strategy to mitigate this risk. This could reassess the designs from time to time, follow best practices, introduce iterations within the architecture delivery phases, bringing more agility, introduce or co-work with agile model driven development focusing on model, vision, and feedback.