Does horse riding have anything to do with Enterprise Architecture?
Yes, and I will explain why. For me, to manage risk when doing changes and prepare for new opportunities are the main reason for doing EA. The same goes with horses.
In during pre-production and production, there is a lot of scheduling and re-rescheduling of when to do what, where and with whom. This would be perfect if we could have a software program to handle this in a better way, on an iPad or a laptop on set when shooting the film.
A year ago, I talked to some people in a web-project that was run in an agile fashion. One of my questions was how they managed requirements related to the upcoming GDPR regulations. The answer was that we put them in the backlog. Formally correct from an agile perspective, I don’t think it’s the right approach for regulatory requirements.
View the discussions with Greger Wikstrand, Claudio Reyes, Christina Lundström, Mark Battersby, Jesper Kråkhede and Casimir Artmann where they discuss lack of DPO’s and the skills that are needed in the role.
Adding features afterwards is not always that easy, neither with cars or software.
If you follow the agile manifesto, you should make things simple.