"EA and Business Agility are oxymoron"
"Enterprise Architecture makes the SDLC process heavy and dense"
"Enterprise Architecture works only for the companies that run on waterfall SDLC model"
Aligning Zachman with Scrum
In order to align and rhyme with the Agile theme, I have re-ordered the classification names (Zachman does NOT tie the user to itself rigidly) in the revised model.
In the revised Zachman picture below, the original Enterprise names have been revised in an attempt to help align the model closely with geographically and physically spread modern enterprises.
- 'Event' here indicates the trigger or alarm condition for the the business flow or process to begin.
- 'Capability' reflects upon the business rules and principles encompassing the asset or action to be taken
- 'Function' could be auto or manual or a combination to define course of action.
- 'Asset' could be an object, piece of information, ER et al. It could be anything that business considers as an asset.
- 'Location' could be on cloud or on-premise or hybrid, location of the asset on which the action is to be taken.
- 'Reason' should be included for tracking purposes so that we could establish why a change was made or suggested.
From here, we could dwell a level deeper and see how the revised Zachman could be plugged into the scrum SDLC for defining each user story. The section highlighted in Yellow above is representing a scrum user story at operational level, capturing the details in a pre-defined template/format. When this revised Zachman model is plugged into the Agile [REF-2] SDLC, organization could benefit immediately/earliest in shape of -
- primarily, every user story would not have a story/theme
- it would be able to provide consistency in capturing requirements in the right details for all the projects,
- it would also be able to provide just the right amounts of details at the front end of the process,
- it would enable the solution and technical engineers to work in close collaboration with the business analysts during the conceptualization phase,
- this approach might also help in reducing the backlogs between sprints.
- finally, this is extensible solution and can easily be modified to align with any change(s) in business and/or EA guidelines.
On the flip side - Agile being an umbrella for multiple known methodologies, i.e. Scrum, Kanban, Scrumban etc, I believe it could be moulded to meet the organization requirements and just like we saw how Zachman framework could be custom-built to suit to the organizational expectations and culture.
Here we have covered just the user-story aspect of the agile process (aligned with Zachman model), and in the next part of this blog series I am going to showcase how one could make the overall SDLC process iterative and align TOGAF with Agile SDLC, at EPICS and Sprint level.
Disclaimer - Please note, there are many more EA models/frameworks and the value chain could also be represented potentially in dozens of different ways. That being said, Agile and EA could be aligned in multiple different ways - owing to flexibility offered by both, as long as the using organization knows what it's looking for.
REF-1: The Zachman Model
REF-2: Agile Principles