The Architect Grinch was in an office located on top of a company called “Who Inc.”. The Architect Grinch hated software releases because they disrupted the beautiful architecture he created, while technologies used by development teams were never aligned with standards he defined. With agile developments, things got even worse as the pace of developments increased considerably. Things got so bad the Architect Grinch no longer wanted to speak with the development teams! Little by little, the Architect Grinch isolated himself from the rest of the company and stopped providing business strategic directions to the development teams.
On Christmas Eve, he became fed up with the new developments of a major release coming out on Christmas. He was bored by the joy of the developers and all the decorations they prepared to celebrate the new release. He could no longer stand all this happiness and team sprit while he was alone in his office. The Architect Grinch made the decision to steal the new release with the intention of undermining the good spirit of the dev teams.
To get the new release, he had to break into the company’s datacenter where the release was safely stored. The Architect Grinch disguised himself as Santa Claus to make sure no one could recognize him. At the entrance of the datacenter, he pretended he was an engineer from a computer vendor and had to bring back one server in his workshop to fix it. He said he had to put on a Santa costume because his company asked him to do so to cheer up customers for Christmas. Once inside the datacenter, he immediately took the server that stored the new release. When going back to his office, he also got into the developers’ office and stole all the decorations.
The next day, the Architect Grinch waited to hear a sad cry from the developers. However, the developers were joyously singing and celebrating Christmas. The Architect Grinch went down to the developer office and asked what was happening. One developer replied that if the release was not ready for today, there would be new sprints that would improve the software anyway. The developer then said, “We will need you to help us understand whether the developments are going in the right direction and aligns with what the business team desires.”
The Architect Grinch began to understand that the true meaning of agile developments depended on the collaborative work and good spirits of the development teams. He then started to understand that it was not him against the developer teams, but rather the developers and him working together for the good of Who Inc. Working alongside with the dev teams, he could bring the strategic vision of the company to the dev teams and share his knowledge. By doing so, developments would be even more productive and efficient, silos that could exist across dev teams would be broken down more easily.
In the end, the Architect Grinch brought back the server to the datacenter and participated in the holiday feast. He was even given the opportunity to show the new IT architecture supporting the business strategy of the company.
Since then, the Architect Grinch has been working daily with the development teams. He even takes part in agile ceremonies like sprint planning and daily stand-ups. He makes sure to share his knowledge across the development teams by providing business goals and the IT strategic plan to the teams, as well as impact analysis and architecture requirements. He has also nominated an enterprise architecture leader in each development team, bringing the architecture practice outside of its ivory tower, as it was perceived by the organization in the past. Working closely with the development teams, he could continuously correct the architecture based on the development teams’ feedback and produce a “just-in-time” architecture as developments advance.
To thank the dev teams, the Architect Grinch wrote a white paper on “Business-IT alignment in the digital era” and gave it to them with a happy holiday message. Fortunately, he also gave us one copy that we would like to share with you!