This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Mike Cottmeyer was recently a guest on the Agile to Agility podcast with Miljan Bajic where he discussed Transformation, BusinessArchitecture, and Scaling. And I want to go to a topic, I haven’t discussed this with anybody on the podcast, I’ve done businessarchitecture. Listen now. Agile to Agility Website.
Composability is really a nice way of saying the ability for something to change to meet the business needs of the day. We’ve taken all of the pieces that the intelligent enterprise is made up of , like finance, procurement, HR, manufacturing, and operations. What did we all do as technologists?
Teams don’t own the risk around finance, technology, brand, and so on, so how can we reasonably expect the Teams to make it all come together? We must clearly define and fund for business outcomes at the capability level so that investments are tied to tangible improvements. Antiquated Technology & BusinessArchitecture.
Organization Knowledge Organization knowledge is useful when considering the management structure and businessarchitecture of the enterprise while designing strategy. We also offer IIBA Certification courses and Domain Certification Courses in Banking, Payments, Trade Finance, Insurance, and US Healthcare.
In order to understand the overarching concepts that govern the structure, benefits and value of the situation and how it related to a change or need; it is essential to have the requisite business knowledge; and the competencies underlying it are: Business Acumen. Organization Knowledge.
But also our businessarchitecture approaches and how we shape the right technology and structures behind the business strategies that we’re defining and working with our clients on. Tom Carpenter: Simon? Simon Blosse: Hi everyone. I’m Simon Blosse. I’m a principal consultant here. So, yeah, I like that. .
Businessarchitecture is an essential input for modernizing the technology portfolio. Yet, business executives often mistake and perceive modernization as a purely technical issue and misunderstand the need of their involvement through a businessarchitecture lens and perspective.
We organize all of the trending information in your field so you don't have to. Join 57,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content