Tag Archives: Enterprise architect

The Open Group Paris Event to Take Place in October 2016

The Open Group, the vendor-neutral IT consortium, is hosting its next global event in Paris, France, between October 24-27, 2016. The event, taking place at the Hyatt Regency Paris Étoile, will focus on e-Government, as well as how to address the dimensions of e-Society, e-Technology and e-Management.

Industry experts will look at issues surrounding business transformation, business analysis, information sharing, e-Health, privacy and cybersecurity. Sessions will examine the strategic execution and the application of emerging technologies and management techniques to e-Government. Presentations will also include the latest on the European Interoperability Reference Architecture (EIRA) and the Regulatory Impact of the General Data Protection Regulation (GDPR) on Personal Data Architecture.

The event features key industry speakers including:

  • Rob Akershoek, ‎Solution Architect (IT4IT), Shell
  • Robert Weisman, University of Ottawa
  • Roland Genson, Director, General Secretariat of the Council of the European Union
  • Olivier Flous, Vice President of Engineering, Thales Group

Full details on the agenda and speakers can be found here.

The focus of Monday’s keynote sessions will be Standardized Boundaryless Information Flow™ and how Enterprise Architecture can be used in e-Government. There will also be a significant emphasis on business transformation, with the Tuesday plenary and tracks looking at successful case studies, standards as enablers, and architecting the digital business.

Further topics to be covered at the event include:

  • IT4IT™ – managing the businesses of IT, vendor adoption of IT4IT™ and a CIO-level view of the standard
  • Open Platform 3.0™ – the customer experience and digital business, architecting Smart Cities and how to use IoT technologies
  • ArchiMate® – new features of ArchiMate® 3.0 and a look at open standards in practice
  • Open Business Architecture – examining the new Open Business Architecture standard and how to address enterprise transformation

Member meetings will take place throughout the course of the three-day event for ArchiMate®, Architecture, Healthcare, IT4IT™, Open Platform 3.0™, Open Trusted Technology and Security Forum members.

Registration for The Open Group Paris event is open now, is available to members and non-members, and can be found here.

@theopengroup #ogPARIS

 

makingstandardswork

Leave a comment

Filed under ArchiMate®, Boundaryless Information Flow™, digital strategy, Digital Transformation, e-Government, Enterprise Architecture, Healthcare, Interoperability, IoT, IT4IT, Open Platform 3.0, Security, Standards, The Open Group, The Open Group Paris 2016, Uncategorized

Digital Disruption for Enterprise Architecture

By Myles F. Suer, Chief Platform Evangelist, Informatica

Recently, I got to sit at the font of wisdom which is Jeanne Ross, and get her view into digital disruption and the role of Enterprise Architecture in enabling firms to respond. I am going to summarize her main points here which I hope will be as useful to you as it was for me.

Jeanne, Research Director and Principal Research Scientist, MIT Sloan School of Management, started her talk by saying that she has a passion for Enterprise Architecture. And she said for me and for you, as the digital economy has arrived, I have felt this was our moment. We were going to have integrated channels, seamless end-to-end transactions, real understanding of customer data, and real tight security. “And this of course means architecture”. And she in jest says that she was hoping that the whole world had come to this very same conclusion. Clearly, she said, it hasn’t happened yet but Jeanne importantly believes with the march to becoming digital, it will happen soon.

Success in the digital economy is not guaranteed

Jeanne says one thing is becoming increasingly clear–enterprises will not be successful if they are not architected to execute their firm’s business strategies. At the very same time, she has found with the companies (existing successful enterprises) that she talks to believe their success is not guaranteed in the digital economy. Given this, Jeanne decided to research what incumbent enterprises actually look like that have taken concrete steps to respond to the digital economy’s mandates. The 27 companies :

  • The challenges they are facing
  • The disruptions that they had identified
  • The strategies they were moving forward with
  • The changes that they had already put in place

She found that digital strategies were inspired by the capabilities of powerful readily available technologies including things like social, mobile, analytics, cloud, and internet of things. Digital strategies were forcing companies around a rallying point but surprisingly there was not much distinction behind the rallying point more than, “I want to be the Amazon or Uber of my industry”. But Jeanne claims this is okay because competitive advantage is not going to be about strategy but instead about execution. And being the best at execution is going to eventually take you in a different direction than other market participants.

Competitive advantage today requires executing on integrated capabilities

At this point, Jeanne stressed that there is no competitive advantage in a single capability. This is why Uber has so much competition. But for established companies, advantage will come from an integrated established set of capabilities. “Competitive advantage will come from taking capabilities that others may or may not have and integrating them in ways that make something extraordinarily powerful”. This in Jeanne’s mind is how established companies can best startups because as we know, startups “can only do one thing well”. Integrating business capabilities provides a whole value proposition that is hard for others to copy.

Jeanne says that there is one more thing that existing companies need to get good at. They need to become responsive. Startups are constantly monitoring and learning what to do next. Think about Christopher Columbus and what an established company and a startup would do. The startup would pivot and learn how to do something different. Established companies need to learn how to do this too.

Now as we move into the digital economy, there are two strategies possible. And established companies must choose one to lead with. They are customer engagement or digitized solutions. Customer engagement means that every day, you wake up trying to figure out what you can do next to make customers love you. The great example that Jeanne gave is Nordstrom. She said that Nordstrom a few years ago was clearly being disrupted. And Nordstrom responded by creating a personalized shopping experience. This was enabled by combining capabilities around a transparent shopping experience and transparent supply chain. This of course is layered on top with predictive analytics. This allows them to predict what a customer needs and to know how to get it to them regardless of channel.

The second strategy is digitized solutions. Here you figure out what customers need that they don’t know they need. GE is doing this today as an industrial company. They are moving the value from the physical asset to asset performance management.

Her parting remarks

If your company has not embraced either of these then it doesn’t get the digital economy. You need to pick one to execute now. Enterprise Architects have a major role to play here. In the past, architecture was largely a divide-and-conquer approach. Today it is about integration. Today architecture is about empowering and partnering. We need to architect for agility. This means flatter organizations. Today, we need to be able to use data for decisions. The jobs of architects are incredibly important. You see the change that is necessary and you are in a unique position to help get your company there.

By Myles F. Suer, Chief Platform Evangelist, Informatica

Myles Suer acts as a Chief Platform Evangelist at Informatica Corporation. In this role, Mr. Suer is focused upon solutions for key audiences including CIOs and Chief Enterprise Architects and the application of Informatica’s Platform to verticals like manufacturing. Much of Mr. Suer’s experience is as a BI practitioner. At HP and Peregrine, Mr. Suer led the product management team applying analytics and big data technology to the company’s IT management.

Mr. Suer has also been a thought leader for numerous industry standards including ITIL and COBIT. As part of this, Mr. Suer was a reviewer for the ITIL Version 3 standard. For COBIT, Mr. Suer has written extensive. Most recently, he published in COBIT Focus, “Using COBIT 5 to Deliver Information and Data Governance”. Prior to HP, Mr. Suer led new product initiatives at start-ups and large companies. This included doing a restart of a Complex Event Processing Company. Mr. Suer has also been a software industry analyst. Mr. Suer holds a Master of Science degree from UC Irvine and a 2nd Masters in Business Administration in Strategic Planning from the University of Southern California.

Twitter: @MylesSuer

Further Reading

Jeanne Ross of MIT/CISR talks on Digital Disruption

Should the CDO drive corporate Digital Disruption?

The Importance of data in Digital Disruption Via @ComputerWorld

What is the role of government in Digital Disruption?

Are you acting like a software company? Your business may depend upon it

Using data and IT to gain Competitive Advantage

Leadership in an age of  digital disruption

Business model change: how does digital disruption drive the need for it?

@theopengroup

 

Leave a comment

Filed under digital strategy, digital technologies, Digital Transformation, Uncategorized

From Solution to Enterprise Architecture with the ArchiMate® Language:  An Interview with Ryan Kennedy

By Iver Band, Enterprise Architect at Cambia Health Solutions and Vice Chair, The Open Group ArchiMate Forum

I recently sat down with my Cambia Health Solutions colleague Ryan Kennedy.  Ryan is an architect with whom I have worked over the last year and a half on a variety of projects that benefit Cambia’s Healthcare consumer and group customers.  After noticing how Ryan has used the ArchiMate® language to expand his personal contribution to the company, I decided to get his perspective on the language, including the new ArchiMate 3.0 standard.


Iver
: What is your professional background?

Ryan
: Prior to becoming an architect, I was a software development engineer for over a decade, designing and implementing solutions across a broad range of organizations, from stable enterprise to volatile startup.

Iver
: How did you encounter the ArchiMate language?

Ryan
: Part of the onboarding process for new architects at my company is a bootcamp-style introduction to the ArchiMate language and its practical application.

Iver
: What were your first impressions?

Ryan
:  My first impression of ArchiMate was that it is very easy to learn if you know Unified Modeling Language (UML).  My second thought was, “Wow, now I can design all the things!”  It is a quantum leap from a grammar that can describe software, to a palate capable of representing the remainder of the enterprise.

Iver
: How have you used the language since then?

Ryan
: I use ArchiMate almost daily, and I treasure the power it gives me to quickly and effectively communicate my solutions to all manner of stakeholders, from business owners to software developers.

Iver
: For what would you recommend the language?

Ryan
: For any aspect of the enterprise that needs design, description or analysis for a broad range of stakeholders.  This includes motivation, strategy, business process, applications, technology, implementation, and migration.

Iver
: What are you doing with the language now?

Ryan:
My current duties mostly revolve around design and estimation of new feature work for sizing, budgeting, and ultimately making implementation choices.  For a new capability, I usually start with the business concerns.  For more technical solutions, I may start at the application or technology layer.  Either way, the traceability of cost and value across layers is what I’m usually trying to communicate at this phase, along with risk analysis.Iver: What are your impressions of the ArchiMate 3.0 language?

Ryan
: Capabilities!  Making capabilities first-class citizens should help us improve our portfolio planning and valuation.  Also, groupings really mean something now which is cool.  If your organization is anything like mine, tagging is important for your data.  Groupings are a great way to tag your ArchiMate concepts.  Also, you may have the same actual concept represented as different ArchiMate concepts in different viewpoints.  Groupings can keep these things together as an abstract, layer-agnostic concept.  Further, you can then describe relationships between aspects of disparate concepts, which should allow a lot more freedom and nuance in your design.Iver: What additional uses of the language do you see based on the 3.0 version?

Ryan
: With the addition of the strategy and physical capabilities, the language is capable of modeling almost any aspect of business or technology.

Iver
: What are your tips for getting started with the language?

Ryan
: Flashcards!  There are a lot of concepts to memorize!  Other than that, my UML background was enough to become fluent in ArchiMate in a few weeks, and I’m fortunate to have expert peer reviews for continuous improvement. If you have no visual modeling background, a formal course is probably in order.
By Iver Band, EA, Cambia SolutionsRyan Kennedy (left) giving his impressions of the ArchiMate language to Iver Band at Cambia Health Solutions in
Portland, Oregon

Iver Band
 is an Enterprise Architect at Cambia Health Solutions, where he uses the ArchiMate language continuously to develop strategic architectures, guide solution development, and train other architects. Iver is also Vice Chair of The Open Group ArchiMate Forum, co-author of the ArchiMate certification exams, and a frequent writer and speaker on Enterprise and Solution Architecture.  Iver is TOGAF and ArchiMate Certified, a CISSP, and a Certified Information Professional.

@theopengroup  @ArchiMate_r  #ArchiMate

2 Comments

Filed under ArchiMate®, Enterprise Architecture, Enterprise Transformation, Standards, standards, The Open Group

Ensuring Successful Enterprise Architecture by Following Kotter’s Eight Stage Journey

By Stuart Macgregor, CEO, Real IRM Solutions and The Open Group South Africa

These industry insights look at John Kotter’s eight stages of change management, and explore his timeless blueprint for effective change leadership. These change management principles can gel with an enterprise architecture (EA) roadmap to achieve business transformation.

The company’s EA practice is viewed as the engine room that powers the move towards transformation, and not the end-goal in itself. However, Kotter’s eight stages have a huge role to play in the development of an EA practice.

Stage 1 – Establishing urgency

The journey begins with breaking new ground, jolting people out of their comfort zones, and forcing them to deal with often uncomfortable realities. Change, in general, is something people tend to resist – and one of the first tasks for change agents is to overcome the powerful forces of tradition.

This stage requires executives to arrive at a brutally honest assessment of the company as it currently stands. It means exposing issues that may hinder growth and adaption in the future. It involves assessing the market realities, confronting macro, global forces – and identifying all the possible crises, barriers, sources of resistance, as well as potential opportunities.

Most importantly, it requires leaders and change agents to start removing the sources of complacency within the company. In other words, they must refute the reasons that some use to believe change isn’t necessary, or that the cost of change will be too great.

Establishing (or reinvigorating) the company’s EA practice is vital in making a successful start on the change journey.

EA rises to the fore as the primary toolset that will enable lasting positive change. It guides the company from a state of fragmented applications, organisational structures and processes – and builds an integrated and optimised environment.

In short, EA fuses the business model imperatives and the IT portfolio.

Establishing a sense of urgency among key stakeholders (a process that is triggered by the company CEO) makes the formation of change leadership structures possible. From an architectural perspective, these are bodies like business architecture governance committees, architecture review boards, and IT steering committees.

Without adequate governance, enterprise architecture will remain a theoretical concept that will fail to deliver any transformational business benefits. This, in fact, moves the process neatly on to stage two…

Stage 2 – Creating the guiding coalition

Kotter shows that a strong, core team (the “guiding coalition”) lies at the heart of any good change strategy. From there, the message of change radiates outwards to stakeholders throughout the broader company and its extended ecosystem.

Importantly, this coalition must possess people with one or more of the following characteristics:

  • Position of power… from executives, to line managers, to others with an influential stature in the enterprise, it is essential to enlist the support of decision-makers at an early stage.
  • Expertise… team members with diverse skill sets and points of view, and experience in many of the key areas of the enterprise.
  • Credibility… those involved in the coalition need to have strong reputations and the ability to sway the mindsets of others that are hesitant to buy in to the change strategy.
  • Leadership… it is essential for the team to include proven leaders who are capable of the kind of visionary, strategic thinking that the coalition will demand.

The team is pulled together by mutual trust, a shared vision for the future, and a passion to achieve these common goals. While at this stage the end-state of business transformation may not be in view, there is a shared recognition that the company needs to change the way it operates.

From an EA perspective, this guiding coalition sets the tone where EA starts to be viewed as a business entity of sorts. In a fully functioning EA practice, the company manages its ‘stock in trade’ (the corporate intellectual capital), and assembles the various components into EA products and services that address specific stakeholder requirements.

By starting to run the EA practice as if it was like a business in itself, even at these early stages, the coalition sets out on the right path – one that will eventually see the company formalising and packaging intellectual capital, and turning it into a corporate asset.

The business model will work if the various stakeholders within the company receive more value than their perceived cost of contribution. For example, HR may benefit from having a clear map of everyone’s role profile; internal audit may value the accurate view of weaknesses in the company’s internal processes. Something of a virtuous feedback loop develops.

Stage 3 – Developing a vision and strategy

In Kotter’s third stage – “developing a vision and strategy” – the guiding coalition sets to work on crafting the vision of change and transformation.

This typically runs as an iterative, sometimes even messy, process. Many different perspectives from the various stakeholders are considered, as different role-players provide a number of alternative ways to approach problems and reach goals.

As Kotter reiterates, this is a stage that encompasses both the head and the heart. It is a dynamic process that sees the value of strong teamwork rising to the fore – as the guiding coalition eventually settles on a unified approach..

A shared vision

Because of this complexity, the coalition can take weeks, even many months, to achieve a coordinated strategy for the future. Once established, a key contribution of the enterprise architecture (EA) practice is reducing the time taken to produce deliverables – such as the business capability map, for example.

Developing the vision requires the coalition spearhead a number of initial EA work-streams.

To begin with, a set of initial readiness assessments need to be conducted. These provide a clear barometer of where the organisation currently stands, in terms of the maturity and health of its existing EA practice, or its ability to easily embed a new EA framework. The assessments play a vital role in informing the vision for the future state.

Creating a library of definitions is an important early stage activity that ensures all the key stakeholders start from a common understanding of what EA, and a number of other important concepts and terminologies, really means.

Each of these needs to be considered across three dimensions: EA domains, the EA continuum and the EA architecture practice:

  • EA domains consist of business architecture, information architecture, data architecture, applications architecture, and technology architecture.
  • The EA continuum considers reference models at a group/enterprise level, an individual business or divisional level, as well as at product application and product focus level.
  • The EA architecture practice spans the areas of EA products and services, EA people, EA content (models, principles, standards, inventory, etc), as well as processes and tools.

Guiding principles are formulated across these three dimensions and serve as input to EA vision and strategy.

So, what exactly does the vision need to look like? While there is no singular approach to this, Kotter outlines a number of important characteristics inherent in any good vision that a guiding coalition composes.

He says it must be imaginable, desirable, feasible, focused, and flexible. Finally, it must be simple to communicate (something I will look at more closely in my next Industry Insight).

A guiding coalition

As the vision starts to crystallise, the coalition segments it into different work-streams – and assigns champions to each of these. Having individuals accountable for every aspect of the vision creates a strong sense of ownership, and ensures essential aspects are never overlooked.

It is only by following this thorough approach to developing the vision that the company can address its core system challenges at a root cause level, and overcome the well-worn situation of endless ‘quick fixes’.

It must be imaginable, desirable, feasible, focused, and flexible.

Too often, budget and time constraints force companies to address only the surface symptoms – by implementing disjointed, piecemeal improvements that fail to address the underlying issues, and serve to undermine the company’s EA practice.

These kinds of vicious cycles start circling throughout the organisation. As its structures become increasingly dependent on ad hoc quick fixes, they are continually weakened. In today’s competitive market environments, this is something that businesses can ill afford to let happen.

But, by following the vigorous approach to strategy and vision creation, the guiding coalition ultimately arrives at a strategic plan that describes how the business will transition, what the end-state will look like, and where investments, energy and focus need to be directed.

As everyone buys into the vision, change agents foster a better understanding of the ‘customer’ (internal stakeholders within the enterprise), the ‘products’ (the capabilities made possible by the EA practice), and how these products will be structured and packaged to address particular business needs.

Stage 4 – Communicating the vision

From the outset, the guiding coalition is responsible for communicating the EA vision to a nucleus group of stakeholders. As the EA practice develops momentum, the communication emanates outwards, to an increasingly broad group of stakeholders within the business.

Clearly, in this phase, timing is everything.

Over time, the EA practice evolves from its fledgling state, to greater levels of maturity. As this happens, the nature of the messages will change.

John Kotter (who advises on the eight stages of change management) says the communication needs to contain the following characteristics:

  • Simplicity (eliminating jargon and verbosity)
  • Metaphor-rich (pictures are worth a thousand words)
  • Multiple forums (leadership sessions, team meetings, newsletters, Intranets, etc)
  • Repetition (to reinforce the key messages and ensure they ‘sink in’)
  • Leadership by example (conduct from leadership that aligns with the communications and messaging)
  • Explaining apparent inconsistencies (address everything that seems counterintuitive or illogical, to avoid the communication being undermined)
  • Two-way communication (involving a feedback loop wherever possible greatly increases engagement and empowerment levels)

Put simply, the goal of this phase is to ensure the right staff are provided with the right information, at the right time – and empowered to work constructively within the new EA framework.

The advantages of formalising corporate intellectual property and establishing an EA practice need to be clearly articulated – at both an individual level and a company-wide level. If the EA vision is not clearly understood, people will very quickly disengage. They will revert to old habits and frameworks of working, and the timelines for the EA practice to start delivering business value will increase.

Too often, the coalition becomes overly enamoured with EA as a discipline – too ‘inwardly-focused’ – and forgets about the importance of communicating regularly with key stakeholders, business owners, and decision-makers across the organisation.

In fact, there is a continuum, ranging on the one end from the purist that “sits in an Ivory Tower” and becomes too academic and removed from the business, to the other end of the spectrum, with an EA practice experienced in the realities of the company, knows its challenges (eg, political, technical, legacy-related), and takes a pragmatic approach to EA.

The latter is the approach most likely to succeed in generating a sustainable and value-adding EA practice.

Over time, the EA practice evolves from its fledgling state to greater levels of maturity.

Here I use the analogy of running the EA practice like a business in itself: through delivering value to stakeholders one builds a relationship where people willingly engage with the EA practice. In this ideal scenario, positive word of mouth is created – which becomes one of the most valuable forms of internal communication.

Another very impactful form of communicating the vision is when the coalition exemplifies the behaviour it is seeking to establish in others, and ‘leads by example’. By becoming a role model, the coalition is more likely to succeed in its quest to develop new ways of working within the broader company.

Stage 5 – Empowering action

But communication alone is not enough. Ensuring the broad-based empowerment of people involves doing the following:

  • Teams need to understand the vision for business transformation and the EA value proposition that will enable it. Individuals must internalise this, consider what it means to them, and truly buy into the vision. They, in turn, will become ‘marketers’ of the company’s EA practice – articulating the vision to other stakeholders.
  • Teams need to receive quality, comprehensive training on the EA disciplines and activities as they relate to the individual’s particular function within the company. They must be empowered with the architecture content that allows them to start harvesting information.
  • From there, teams need to populate all of this existing content (such as business strategies, IT strategies, existing applications portfolios, etc) into an integrated EA repository, fully embedded in the organisation.
  • An EA methodology – such as TOGAF – is customised and tailored to the company. This means aligning the EA process with the systems development life cycle, strategic planning, corporate governance, and business process improvement, for example.
  • Any barriers, at any stage, need to be swiftly removed, so individuals are unleashed to work and to add value within the new framework.

Stage 6 – Generating short-term wins

Quick wins, even on a small scale, become the catalyst to building momentum in enterprise architecture.

By this point in the process of business transformation, the company has established and communicated the vision for change, and then begun the process of empowering the right teams to start executing on that vision.

Now, as it starts to package some of the early-phase model content, it becomes crucial for the fledgling enterprise architecture (EA) practice to generate some quick wins. Demonstrating tangible business value, even on a small scale, helps to maintain the interest of key stakeholders, and ensures the momentum doesn’t start to wane.

In fact, a virtuous cycle should begin to emerge: as the EA practice develops the operational capability to satisfy some business needs, stakeholders begin to recognise the business value. This leads to positive word-of-mouth being spread throughout the company, which in turn stimulates increased levels of demand from various quarters.

Ultimately, this demand translates into increased willingness to invest in the EA journey. With greater levels of buy-in, the EA practice’s operational capabilities continue to expand, and the cycle continues.

Stage 7 – Success breeds success

Short-term wins become the catalyst to building momentum in EA. John Kotter says these early successes are vital for a number of reasons, including the following:

  • Providing evidence that sacrifices are worth it: many staff within the coalition and other areas of the business have invested great time and energy in getting to this point.
  • Reward change agents with a pat on the back: adding business value is the biggest recognition of success.
  • Help fine-tune vision and strategies: insights learned from practically applying EA can be fed back into the strategic thinking.
  • Undermine cynics and self-serving resisters: tangible EA successes start to erode the credibility of naysayers.
  • Keep bosses on board: maintaining the support of line managers, executives, and other senior stakeholders happens naturally
  • Build momentum: more and more people are drawn into the developing EA practice, as people want to associate with a ‘success story’.

It goes without saying that these short-term wins need to be built on a sustainable and professional EA practice. The foundations must be strong – so the content can be easily accessed, and re-used for further process improvement in other areas of the business.

As the demand for business transformation increases, the EA practice needs to manage expectations and delivery. The EA team cannot take on ‘too much’ in the early stages, and be seen as the team that slows things down, or hampers innovation and change.

Essentially, the value that stakeholders derive from EA needs to continually exceed their perceived cost of contribution.

As the practice reaches out into the broader company, new opportunities emerge for specialists to contribute their unique insights. To keep the right people on the team, the company also needs to attend to human capital issues, like:

  • Ensuring key EA staff members have professional development paths and the opportunities to further their formal qualifications.
  • Providing mentoring (from within the organisation, or by pulling in outside mentors).
  • Performance management processes that ensure staff are accurately rewarded for their performance.

With the right team in place, the lead architect’s focus can shift from the everyday EA operations to higher-value activities. These include continually engaging with executives from across the business – to extend the scope of the EA practice and ensure it remains relevant and value-adding.

The value that stakeholders derive from EA needs to continually exceed their perceived cost of contribution.

The lead architect and the team can concentrate on understanding the potentially disruptive “nexus of forces” (cloud, mobility, big data and social), conducting impact assessments, scenario planning, and implementing new strategies.

The architecture team is then operating on all three levels – strategic, tactical and operational; and facilitating learning across the enterprise.

In this way, the chief architect and his EA team start to position themselves as trusted advisors and business partners to the company – becoming a crucial leadership support function. Ultimately, the true measure of the EA team’s worth is the extent to which the company engages with it, and the extent to which business transformation has been realised.

Stage 8 – Making it stick

Shifting from a state of architecture execution to architecture leadership is the next step in the EA journey.

Kotter’s final stage guides an organisation on the optimum ways that change can be embedded, anchored and matured. From an Enterprise Architecture (EA) perspective, these phases relate to the ‘professionalising’ of the EA practice.

Earlier, we looked at generating tangible “early wins” in the EA practice, and how they can echo throughout the organisation, as positive word-of-mouth spreads. The next step is to build on this momentum and to establish EA across every layer of processes, people, content, and tools, and products/services.

So, what are the hallmarks of a mature-state EA practice?

  • Entrenching the ethos of “running the EA practice like a business”… The foundation of the ‘business model’ includes five process areas: managing the business, enhancing market reputation, winning better business, delivering valued solutions, and growing the EA capability. In this way, resource allocation remains tightly synced with business need.
  • Innovation… EA essentially manages intellectual capital as an asset, translating tacit individual knowledge into organisational assets, in the form of models – which fuels constant innovation. Ideas are crowd-sourced from employees and partner ecosystems, and then analysed and prioritised according to business impact.
  • Strategic planning is dynamic and living… As intellectual capital becomes formalised as a corporate asset, the company can perform strategic planning at a higher level. This enables it to respond with agility to any changes in the external environment, as well as evolving business models within the company walls.
  • Business processes and capabilities become optimised… integrated business processes are naturally (willingly) enforced across the business. Process owners and system custodians focus on the right business capabilities and continually optimise processes.
  • Investment… The organisation targets its technology investment on IT assets that support identified and measurable business objectives, all within the framework of EA.

These fundamentals represent a shift from a state of “EA execution” to what can be referred to as “architecture leadership”.

In this state of advanced EA maturity, EA should also be repositioned and de-coupled from the IT department. Ideally, EA practice leaders should be moved to the office of the CEO, reporting to a function such as transformation management.

One of the most important facets of successfully transitioning from isolated early wins to EA leadership, which is embedded throughout the company, is ensuring key people are retained. The departure of important individuals can have catastrophic consequences at this stage – meaning EA never becomes entrenched.

For this reason, successful business leaders place a high emphasis on training, mentoring and further developing the EA teams. As ambitions soar, and people develop a passion for EA, industry bodies like The Open Group provide a useful outlet for this energy.

By contributing to the industry standards that are developed by The Open Group, individuals enjoy a greater sense of purpose – a tangible feeling that they are working on ‘something bigger’. Added to this, new opportunities open up, to develop their careers and networks.

For the company, this represents something of a win-win situation. By retaining these key specialists, it ensures the EA programme does not suffer interruptions or collapses.

As the success of the EA practice continues and the solution base expands, a virtuous cycle develops momentum: more and more ‘customers’ within the company start benefiting from EA, and more and more people are willing to invest in it.

The change process speeds up and becomes smoother; the ambit of EA broadens, and starts to influence every aspect of the business – including things like strategy planning, risk management, business transformation, and even mergers and acquisitions.

The essence of EA – that of managing complexity and change – is never forgotten. This new world requires new ways of thinking to address challenges and grab opportunities. Simply put, firms that continue to perpetuate old practices, will be left in the dust.

I’ll leave you with one of the pioneers of EA, John Zachman, who succinctly describes this essential fact:

“Increasing flexibility and reducing time to market… will only happen with responsible and intellectual investment, in developing and maintaining Enterprise Architecture, to deliver quality information, to produce a quality enterprise.”

By Stuart Macgregor, CEO, Real IRMStuart Macgregor is the CEO, Real IRM Solutions and  The Open Group South Africa. Through his personal achievements, he has gained the reputation of an Enterprise Architecture and IT Governance specialist, both in South Africa and internationally.

 

Macgregor participated in the development of the Microsoft Enterprise Computing Roadmap in Seattle. He was then invited by John Zachman to Scottsdale, Arizona to present a paper on using the Zachman framework to implement ERP systems. In addition, Macgregor was selected as a member of both the SAP AG Global Customer Council for Knowledge Management, and of the panel that developed COBIT 3rd Edition Management Guidelines. He has also assisted a global Life Sciences manufacturer to define their IT Governance framework, a major financial institution to define their global, regional and local IT organizational designs and strategy. He was also selected as a core member of the team that developed the South African Breweries (SABMiller) plc global IT strategy.

Stuart, as the lead researcher, assisted the IT Governance Institute map CobiT 4.0 to TOGAF®. This mapping document was published by ISACA and The Open Group. He participated in the COBIT 5 development workshop held in London in 2010.

1 Comment

Filed under architecture, Business Transformation, EA, Enterprise Architecture, Enterprise Transformation, Standards, The Open Group, TOGAF®, Uncategorized

Inaugural User Group Meeting Draws Out New Ways of Seeing TOGAF®

By The Open Group

The Open Group hosted the first TOGAF® User Group meeting on January 25, 2016 in San Francisco. With over 50,000 certified users in more than 120 countries, the intent of the TOGAF User Group was to better serve and reach the entire TOGAF user community, allowing them to network with other users, interact with TOGAF subject matter experts, brainstorm solutions for challenging situations and build an active user community.

According to Terry Blevins, Fellow of The Open Group and consultant for Enterprise Wise, LLC, who facilitated the meeting, the goal for the inaugural event was to provide a venue were users could easily Share, get Enlightened and Express (SEE TOGAF) their needs as users. Blevins says those in attendance were engaged throughout the day and that users “found a useful balance between the three dimensions” of SEEing. In addition, the overall response to the event was positive, he says, with many attendees expressing a desire to hold additional events moving forward.

The User Group format consisted primarily of a full day of managed breakout sessions, each focused on trends that are affecting the use of Enterprise Architecture within organizations today. Facilitators led discussions with users on a variety of critical topics including:

  • TOGAF for Digital Transformation
  • TOGAF Business Scenarios
  • Security within TOGAF
  • The Role of People within TOGAF
  • TOGAF for eGovernment
  • TOGAF Hot Topics

During the session, TOGAF users provided significant viewpoints regarding potential enhancements that could be made to the standard throughout the day. Chief among them was the desire to have more concrete, practical use cases for TOGAF—particularly within specific industries. With many industries currently undergoing some radical shifts as they move toward greater digitalization, users are looking for increased guidance around how to use Architecture frameworks within industry verticals. Blevins states there was some expectation of this going into the User Meeting, but to have that validation directly from users was very important.

“The exciting thing was that we really thought that was going to happen—folks are asking for this and ready to use TOGAF across vertical industries,” he says.

Not only are users looking for more vertical industry examples, but they also expressed a need for additional horizontal use cases that can be used cross-functionally within organizations. Users would like to be able to use TOGAF, an Open Group standard, as a framework for making change within different departments and service parts of organizations such as HR, Finance or Operations. Current work in The Open Group IT4IT™ Forum is actually a perfect example of how the framework can be put to use across service functions, with the IT department leading the way in the form of the IT4IT Reference Architecture.

Guidance around how to do business or digital transformation was also mentioned as a potential enhancement. Blevins believes that with all the requests for templates, case studies and practical examples, there is an opportunity for developing a substantial series of “How to” articles and white papers that can be used in conjunction with TOGAF to provide users greater direction for specific use cases and examples.

“A lot of people really want to use TOGAF,” says Blevins. “They just need some help in applying it.”

Users also expressed a need for assistance in how to get buy-in for TOGAF and architecture from C-level executives within their organizations. This has long been a problem within the Architecture community and architects continue to struggle with how to better sell and market both themselves and what they can do.

Blevins says one suggestion that was made during the User Meeting was that Enterprise Architects stop trying to sell Architecture and instead focus on selling the outcomes or solutions they provide. It was suggested that perhaps architects spend too much time trying to sell their methods and frameworks and the “how” behind their work rather than just talking about solving the problem and how architecture will improve the business. Ultimately, the focus should be on that, not on how to apply Enterprise Architecture, he says.

Users in attendance were also struggling with how to integrate their Architecture efforts with Agile development trends and the need to bring increased innovation and speed to their projects. The need to develop more service- and customer-oriented delivery models to help transform businesses was also mentioned, as well as the need to include more guidance around Risk Management and Security within TOGAF.

The User Group meeting was very productive and provided excellent input on the standard. All feedback from the User Group is being delivered to The Open Group Architecture Forum for consideration in helping to enhance the standard and to provide feedback for TOGAF and trainers, as well to continue developing content that supports the standard and best practices for its use.

Please join us in London on April 27, 2016 for our upcoming TOGAF User Group meeting. The entire agenda for The Open Group London 2016 can be found here.

 

 

3 Comments

Filed under Digital Transformation, EA, Enterprise Architecture, IT4IT, Standards, The Open Group, The Open Group London 2016, TOGAF®, Uncategorized

The Open Group San Francisco 2016 Day One Highlights

By Loren K. Baynes, Director, Global Communications, The Open Group

On Monday, January 25, The Open Group kicked off its first event of 2016, focused on Enabling Boundaryless Information Flow™, at the Marriott Union Square in the city by the bay, San Francisco, California.

President and CEO Steve Nunn gave a warm welcome to over 250 attendees from 18 countries, including Botswana, China and The Netherlands. He introduced the morning’s plenary, which centered on Digital Business and the Customer Experience. This year also marks a major milestone for The Open Group, which is celebrating its 20th anniversary in 2016.

The Open Group Director of Interoperability Dr. Chris Harding kicked off the morning’s event speaking on “Doing Digital Business.”

Digital technology is transforming business today. As such, how Enterprise Architects can architect for and deliver better customer experience is a more critical factor for businesses today than ever before. For thousands of years, most business transactions happened face-to-face with human interaction at the heart of them. The Internet has changed that, largely taking humans out of the equation in favor of “intelligent” programs that provide customer service. As Enterprise Architects, the challenge now is to create corporate systems and personas that mimic human interaction to provide better service levels. To achieve that, Harding says, currently companies are looking at a number of improved models including providing microservices, Cloud architectures and data lakes.

To better enable the transformation toward digital customer experiences, The Open Group Open Platform 3.0™ Forum is currently working on an interoperability standard to support a variety of services that run on digital platforms. In addition, the Digital Business and Customer Experience Work Group—a joint work group of Open Platform 3.0 and the Architecture Forums—is currently working on customer-based architectures, as well as a whitepaper geared toward enabling better customer experiences for digital business.

In the second session of the morning, Mark Skilton of PA Consulting addressed the issue of “The Battle for Owning the Digital Spaces”. Skilton says that in this era of unprecedented digital information, we need to better understand all of that information in order to create business opportunities—however, much of that information is contained in the “gray” spaces in between interactions. Accessing that kind of data provides opportunities for businesses to get a better handle on how to provide digital experiences that will draw customers. It also requires “ecosystem” thinking where what is happening on both the micro and macro levels should be considered.

As such, companies must reconsider what it means to be an enterprise, platform or even a service. This requires a new way of looking at architectures that combines both physical and virtual environments to take advantage of those “gray” spaces in people’s lives. By interconnecting or “flattening” out people’s experiences, such as their work, living, commercial or social spaces, they will be allowed to take their digital experiences with them throughout their lives. To enable these things moving forward, architects will need to change their mindsets to think differently and consider experience more rather than just architectures. Behavior, interactivity, psychology, usability—the human factors—of advanced customer experience will need to be considered in the architecture development process more to create more connected spaces to meet people’s needs.

Trevor Cheung, Vice President Strategy & Architecture Practice for Huawei Global Services, spoke next on “Architecting for Customer Experience.” Cheung introduced the concept of the ROADS Experience, a principle for designing customer-driven architectures. According to Cheung, ROADS (Real-time, On-demand, All-online, DIY and Social) is critical for companies that want to become digital service providers. As organizations digitalize, they should think more holistically about customer experiences—including both internal (employees) and external audiences (customers, partners, etc.)—moving from an inside-out IT perspective to one that also considers outside-in constituencies.

For example, to provide omni-channel experiences, business architectures must focus on the values of stakeholders across the ecosystem—from buyers and their interests, to partners and suppliers or operations. By applying the ROADS principle, each stakeholder, or persona, can be considered along the way to develop an architecture blue print that covers all channels and experiences, mapping the needs back to the technologies needed to provide specific capabilities. Currently two whitepapers are being developed in the Digital Business and Customer Experience Work Group that explore these issues, including a new reference model for customer architectures.

In the last morning session Jeff Matthews, Director of Venture Strategy and Research, Space Frontier Foundation, presented “The Journey to Mars is Powered by Data: Enabling Boundaryless Information Flow™ within NASA.” Currently, NASA’s programs, particularly its endeavors to send people to Mars, are being enabled by complex Enterprise Architectures that govern each of the agency’s projects.

According to Matthews, nothing goes through NASA’s planning without touching Enterprise Architecture. Although the agency has a relatively mature architecture, they are continually working to breakdown silos within the agency to make their architectures more boundaryless.

Ideally, NASA believes, removing boundaries will give them better access to the data they need, allowing the agency to evolve to a more modular architecture. In addition, they are looking at a new decision-making operating model that will help them grapple with the need to buy technologies and setting up architectures now for programs that are being planned for 10-30 years in the future. To help them do this, Matthews encouraged audience members and vendors to reach out to him to talk about architectural strategies.

In addition to the event proceedings, The Open Group also hosted the inaugural meeting of the TOGAF® User Group on Monday. Aimed at bringing together TOGAF users and stakeholders in order to share information, best practices and learning, the day-long meeting featured topics relative to how to better use TOGAF in practicality. Attendees participated in a number of breakout sessions regarding the standard, intended to provide opportunities to share experiences and enlighten others on how to best use TOGAF as well as provide suggestions as to how the standard can be improved upon in the future.

Allen Brown, current interim CEO of the Association of Enterprise Architects (AEA), and former CEO of The Open Group, also introduced the AEA Open Badges Program for Professional Development. Much like badge programs for the Boy or Girl Scouts, the Open Badge program lets people demonstrate their professional achievements via digital badges that provide credentials for skills or achievements learned. Moving forward, the AEA will be providing digital badges, each of which will include embedded information showing the information learned to earn the badge. Attendees can earn badges for attending this conference. For more information, email OpenBadges@GlobalAEA.org.

Monday’s afternoon tracks were split into two tracks centered on Open Platform 3.0™ and Risk, Dependability and Trusted Technology. The Open Platform 3.0 track continued in the same vein as the morning’s sessions looking at how Enterprise Architectures must adapt to the changes due to digitalization and growing customer expectations. Accenture Enterprise Architect Syed Husain gave an insightful presentation on enabling contextual architectures and increased personalization using artificial intelligence. As both consumers and technology become increasingly sophisticated, demands for individualized preferences tailored to individuals are growing. Companies that want to keep up will need to take these demands into account as they evolve their infrastructures. In the Security track, sessions centered on privacy governance, best practices for adopting the Open FAIR Risk Management standard and dealing with cyber security risks as well as how to navigate the matrix of data classification to maximize data protection practices.

Concluding the day was an evening reception where event and TOGAF User Group attendees mixed, mingled and networked. The reception featured The Open Group Partner Pavilion, as well as short presentations from The Open Group Architecture, IT4IT™ and Open Platform 3.0 Forums.

@theopengroup #ogSFO

By Loren K. BaynesLoren K. Baynes, Director, Global Marketing Communications, joined The Open Group in 2013 and spearheads corporate marketing initiatives, primarily the website, blog, media relations and social media. Loren has over 20 years experience in brand marketing and public relations and, prior to The Open Group, was with The Walt Disney Company for over 10 years. Loren holds a Bachelor of Business Administration from Texas A&M University. She is based in the US.

Comments Off on The Open Group San Francisco 2016 Day One Highlights

Filed under Boundaryless Information Flow™, Cloud, EA, Enterprise Architecture, Internet of Things, Interoperability, IoT, Open Platform 3.0, Standards, Steve Nunn, The Open Group, The Open Group, The Open Group San Francisco 2016, The Open Group San Franscisco 2016, TOGAF®, Uncategorized

The Open Group Madrid Summit 2015 – An Interview with Steve Nunn

By The Open Group

The Open Group will be hosting its Spring 2015 summit in Madrid from April 20-23. Focused on Enabling Boundaryless Information Flow™, the summit will explore the increasing digitalization of business today and how Enterprise Architecture will be a critical factor in helping organizations to adapt to the changes that digitalization and rapidly evolving technologies are bringing.

In advance of the summit, we spoke to Steve Nunn, Vice President and COO of The Open Group and CEO of the Association of Enterprise Architects (AEA) about two speaking tracks he will be participating in at the event—a panel on the challenges facing young Enterprise Architects today, and a session addressing the need for Enterprise Architects to consider their personal brand when it comes to their career path.

Tell us about the panel you’ll be moderating at the Madrid Summit on EA Challenges.

The idea for the panel really came from the last meeting we had in San Diego. We had a panel of experienced Enterprise Architects, including John Zachman, giving their perspectives on the state of Enterprise Architecture and answering questions from the audience. It gave us the idea that, we’ve heard from the experienced architects, what if we also heard from younger folks in the industry, maybe those newer to the profession than the previous panel? We decided to put together a panel of young architects, ideally local to Madrid, to get what we hope will be a different set of perspectives on what they have to deal with on a day-to-day basis and what they see as the challenges for the profession, what’s working well and what’s working less well. In conjunction with the local Madrid chapter of the AEA, we put the panel together. I believe it’s a panel of four young architects, plus a gentleman named Juan Abel, who is the chair of the local chapter in Madrid, who helped put it together, with me moderating. The Madrid chapter of the AEA has been very helpful in putting together the summit in Madrid and with details on the ground, and we thank them for all their help.

We’ll be putting some questions together ahead of time, and there will be questions from the audience. We hope it will be a different set of perspectives from folks entering the profession and in a different geography as well, so there may be some things that are particular to practicing Enterprise Architecture in Spain which come out as well. It’s a long panel—over an hour—so, hopefully, we’ll be able to not just hit things at a cursory level, but get into more detail.

What are some of the challenges that younger Enterprise Architects are facing these days?

We’re hoping to learn what the challenges are for those individuals, and we’re also hoping to hear what they think is attracting people to the profession. That’s a part that I’m particularly interested in. In terms of what I think going in to the panel session, the thing I hear about the most from young architects in the profession is about the career path. What is the career path for Enterprise Architects? How do I get in? How do I justify the practice of Enterprise Architecture in my organization if it doesn’t exist already? And if it does exist, how do I get to be part of it?

In the case of those individuals coming out of university—what are the relevant qualifications and certifications that they might be looking at to give themselves the best shot at a career in Enterprise Architecture. I expect it will be a lot of discussion about getting into Enterprise Architecture and how do you best position yourself and equip yourself to be an Enterprise Architect.

Were there things that came out of the San Diego session that will be relevant to the Madrid panel?

There were certainly some things discussed about frameworks and the use of frameworks in Enterprise Architecture. Being an Open Group event, obviously a lot of it was around TOGAF®, an Open Group standard, and with John Zachman as part of it, naturally the Zachman Framework too. There was some discussion about looking into how the two can play more naturally together. There was less discussion about the career development aspect, by and large because, when these people started out in their careers, they weren’t Enterprise Architects because it wasn’t called that. They got into it along the way, rather than starting out with a goal to be an Enterprise Architect, so there wasn’t as much about the career aspect, but I do think that will be a big part of what will come out in Madrid.

I think where there are overlaps is the area around the value proposition for Enterprise Architecture inside an organization. That’s something that experienced architects and less experienced architects will face on a day-to-day basis in an organization that hasn’t yet bought into an Enterprise Architecture approach. The common theme is, how do you justify taking Enterprise Architecture inside an organization in a way that delivers value quick enough for people to see that something is happening? So that it’s not just a multi-year project that will eventually produce something that’s nicely tied up in a bow that may or may not do what they wanted because, chances are, the business need has moved on in that time anyway. It’s being able to show that Enterprise Architecture can deliver things in the short term as well as the long term. I think that’s something that’s common to architects at all stages of their careers.

You’re also doing a session on creating a personal brand in Madrid. Why is branding important for Enterprise Architects these days?

I have to say, it’s a lot of fun doing that presentation. It really is. Why is it important? I think at a time, not just for Enterprise Architects but for any of us, when our identities are out there so much now in social media—whatever it may be, Facebook, LinkedIn, other social media profiles— people get a perception of you, many times never having met you. It is important to control that perception. If you don’t do it, someone else may get a perception that you may or may not want from it. It’s really the idea of taking charge of your own brand and image and how you are perceived, what values you have, what you want to be known for, the type of organization you want to work in, the types of projects that you want to be involved in. Not all of those things happen at once, they don’t all land on a plate, but by taking more control of it in a planned way, there’s more chance of you realizing some of those goals than if you don’t. That’s really the essence of it.

The timing and particular relevance to Enterprise Architects is that, more and more, as organizations do see value in Enterprise Architecture, Enterprise Architects are getting a seat at the top table. They’re being listened to by senior management, and are sometimes playing an active role in strategy and important decisions being made in organizations. So, now more than ever, how Enterprise Architects are being perceived is important. They need to be seen to be the people that can bring together the business people and IT, who have the soft skills, being able to talk to and understand enough about different aspects of the business to get their job done. They don’t have to be experts in everything, of course, but they have to have a good enough understanding to have meaningful discussions with the people with whom they’re working. That’s why it’s crucial at this time that those who are Enterprise Architects, as we build the profession, are perceived in a positive way, and the value of that is highlighted and consistently delivered.

A lot of technologists don’t always feel comfortable with overtly marketing themselves—how do you help them get over the perception that having a personal brand is just “marketing speak?”

That’s something that we go through in the presentation. There are 11 steps that we recommend following. This goes back to an old Tom Peters article that was written years ago titled ‘The Brand Called You’ . Many of us aren’t comfortable doing this and it’s hard, but it is important to force yourself to go through this so your name and your work and what you stand for are what you want them to be.

Some of the suggestions are to think of the things that you’re good at and what your strengths are, and to test those out with people that you know and trust. You can have some fun with it along the way. Think about what those strengths are, and think about what it is that you offer that differentiates you.

A big part of the personal brand concept is to help individuals differentiate themselves from everyone else in the workplace, and that’s a message that seems to resonate very well. How do you stand out from lots of other people that claim to have the same skills and similar experience to yourself? Think of what those strengths are, pick a few things that you want to be known for. Maybe it’s that you never miss a deadline, you’re great at summarizing meetings or you’re a great facilitator—I’m not suggesting you focus on one—but what combination of things do you want to be known for? Once you know what that is—one of the examples I use is, if you want to be known for being punctual, which is an important thing, make sure you are—set the alarm earlier, make sure you show up for meetings on time, then that’s one of the things you’re known for. All these things help build the personal brand, and when people think of you, they think of how they can rely on you, and think of the attributes and experience that they can get from working with you.

That’s really what it comes down to—as human beings, we all prefer to work with people we can trust. Ideally people that we like, but certainly people that we can trust and rely on. You’re far more likely to get the right doors opening for you and more widely if you’ve built a brand that you maintain, and people you work with know what you stand for and know they can rely on you. It’s going to work in your favor and help you get the opportunities that you hope for in your career.

But there’s a big fun aspect to the presentation, as well. I start the presentation looking at branding and the types of brands that people know what they stand for. I think it has scope for workshop-type sessions, as well, where people follow some of the steps and start developing their personal brands. Feedback on this presentation has been very positive because it stands out as a non-technical presentation, and people can see that they can use it privately to further their careers, or to use it with their teams within their organizations. People really seem to resonate with it.

As CEO of the Association of Enterprise Architects, what are you seeing in terms of career opportunities available for architects right now?

We are seeing a lot of demand for Enterprise Architects all over the place, not just in the U.S., but globally. One of the things we have on the AEA website is a job board and career center, and we’ve been trying to increase the number of jobs posted there and make it a useful place for our members to go when they’re considering another position, and a good place for recruiters to promote their openings. We are growing that and it’s being populated more and more. Generally, I hear that there is a lot of demand for Enterprise Architects, and the demand outweighs the supply at the moment. It’s a good time to get into the profession. It’s a good time to be making the most of the demand that’s out there in the market right now. To back that up, the latest Foote Report showed that the OpenCA and TOGAF certifications were among the most valuable certifications in the IT industry. I think there is demand for certified architects and what we’re doing in the AEA is building the professional body to the point, ultimately, where people not only want to be AEA members, but effectively need to be AEA members in order to be taken seriously in Enterprise Architecture.

We’re also seeing an increasing number of inquiries from organizations that are recruiting Enterprise Architects to check that the applicant is indeed an AEA member. So clearly that tells us that people are putting it down on their resumes as something that differentiates them. It’s good that we get these inquiries, because it shows that there is perceived value in membership.

What’s new with the AEA? What’s happening within the organization right now?

Other things we have going on are a couple of webinar series running in parallel. One is a series of 13 webinars led by Jason Uppal of QRS Systems. He’s giving one a month for 13 months—we’ve done seven or eight already. The other is a series of 10 webinars given by Chris Armstrong of the Armstrong Process Group. What they have in common is that they are tutorials, they’re educational webinars and learning opportunities, and we’re seeing the number of attendees for those increasing. It’s a value of being an AEA member to be able to participate in these webinars. Our focus is on giving more value to the members, and those are a couple of examples of how we’re doing that.

The other thing that we have introduced is a series of blogs on ‘What Enterprise Architects Need to Know About…’ We’ve covered a couple of topics like Internet of Things and Big Data—we have more planned in that series. That’s an attempt to get people thinking about the changing environment in which we’re all operating now and the technologies coming down the pike at us, and what it means for Enterprise Architects. It’s not that architects have to be an expert in everything, but they do need to know about them because they will eventually change how organizations put together their architectures.

By The Open GroupSteve Nunn is the VP and Chief Operating Officer of The Open Group. Steve’s primary responsibility for The Open Group is to ensure the legal protection of its assets, particularly its intellectual property. This involves the development, maintenance and policing of the trademark portfolio of The Open Group, including the registered trade marks behind the Open Brand and, therefore, the various Open Group certification programs, including TOGAF®, Open CA, Open CITS, and UNIX® system certification. The licensing, protection and promotion of TOGAF also falls within his remit.

In addition, Steve is CEO of the Association of Enterprise Architects (AEA) and is focused on creating and developing the definitive professional association for enterprise architects around the globe. To achieve this, Steve is dedicated to advancing professional excellence amongst AEA’s 20,000+ members, whilst raising the status of the profession as a whole.

Steve is a lawyer by training and has an L.L.B. (Hons) in Law with French and retains a current legal practising certificate.

Join the conversation @theopengroup #ogchat #ogMAD

 

 

Comments Off on The Open Group Madrid Summit 2015 – An Interview with Steve Nunn

Filed under Boundaryless Information Flow™, Brand Marketing, Enterprise Architecture, Internet of Things, Open CA, Standards, TOGAF, TOGAF®, Uncategorized