Improving Enterprise Architecture skills for the Omaha area professionals.
I found a Enterprise Architecture group on https://www.meetup.com I have been wanting to improve my skills, but also get a better understanding what others in the community see in terms of Enterprise Architecture.
The meeting was at Mutual Omaha. I have driven by the building for years, but never physically been in the building.
I was given a tour of the area under the doom. There are four restaurants and lots of opening seating.
On the tour there was a area that is marked as collaboration area of the future. It was interesting to see how it was laid out.
We made our way to one of the conference rooms to start the meeting.
The start of the discussion was a eye opener. It was the difference of Enterprise Architecture vs Software Architecture. I cam to the group looking at the approach of Software, but thinking about how the Enterprise ties to the business was more compelling to me.
Different Discussion Points
Enterprise Architecture is about solution at a larger scale. Architect your enterprise to meet the business.
Disciplined Agile 2.0 YouTube video
•Disciplined Agile Delivery Framework
Togaf Architect: First time ever hearing of this solution.
Challenge of recreating or how do I get something for Free. Who pays for it? How do you get businesses to build application where technology is talked in terms of business.
•Value of EA gives guidance to let teams provide value.
•How do you engage different technology teams?
•Mutual of Omaha uses three week sprints?
•Following standards vs guidance.
•Complete visibility in the work
•Business team hearing what there systems does.
•Talking to Business Owner about the features of what a system does not the application.
◦Business Capability model.
◦Why do we teach people to talk features applications or technology?
◦Capabilities of the system for the business
• Should enterprise architects give solution to software teams.
◦Does this that impedes business from success.
◦Are you meeting business objectives?
◦Support Delivery teams
◦Finding individual success on teams and how can others use it.
◦Be the team people wants to call.
◦Negations of technical dependencies.