Tweets from Open Group conference, Austin

A selection of Tweets from various folks – with an especial thank-you to @systemsflow and @theopengroup – from the Open Group conference, Austin, Texas, 18-20 July 2011, via the Twitter hashtag #ogaus. (Selected in the sense that most of the Tweets I’ve included are on business-architecture and enterprise-architecture – I haven’t included much on Cloud, IT-security or other strictly IT-oriented themes.)

Various breaks added to split the overall Twitter-stream into (I hope) more meaningful clusters; I’ve also added comments in various places in italics preceded by a ‘>’ marker, >like this.

There’s quite a lot of it, so take a wander after the ‘Read more…’ break.

  • systemsflow: All about business architecture day 1 at #ogaus
  • systemsflow: Business Architecture: can’t every business be boiled down to one use case name: Make Money? Drill down from there >no, it can’t: this is exactly what not to do for #entarch / #bizarch…
  • systemsflow: RT @systemsflow Can’t every business be boiled down to one use case: Make Money? Drill down from there // forgot govmn’t: Win Mission >’make money’ / ‘win mission’ etc are subsidiary #entarch aims for specific stakeholders: understand whole-enterprise first!
  • tetradian: @systemsflow we develop #entarch for an organisation, but about whole-enterprise – are not the same! http://slidesha.re/8wWNSq
  • tetradian: systemsflow: “theme for today is ‘benefit bottom line w/EA = succeed'” – hmm. indicates limited model of how enterprise works…?
  • JWGaus: @tetradian @systemsflow #entarch there are too many nuances of ‘make money’, the next level of detail is needed.  Too generic to be useful. // define vision and principles for how to ‘make money’ and define enterprise structure to that. // summarize higher than your vision and principles and you’ve lost your enterprise.
  • tetradian: RT @JWGaus: define vision / principles for how to ‘make money’ , define enterprise structure to that. >wrong way round? http://bit.ly/9zU9J
  • Cybersal: @tetradian @systemsflow The negative consequences of focusing on bottom line ahead of everything else http://bit.ly/oYCEiE #entarch #bizarch
  • iansthomas: RT @systemsflow BizArch can’t every biz be boiled down to 1 use case: Make Money? <custs or emps r more attracted to purpose >exactly!
  • JWGaus: @tetradian #entarch Yes, #sustainability is a key thing I was referring to in “nuances of making money”. Making money must include it // #sustainability includes care of enterprise ecosystem, people, and yes, the planet. Oh, and shareholders 🙂
  • theopengroup: David Baker, PriceWaterhouseCoopers: How do you manage the complexity of running a business while trying to transform it?
  • larrycincy: David Baker showing how to have business plan become the foundation of connecting solutions to business intent <- interesting goal
  • theopengroup: Baker cites Disney: moving from from physical assets to intellectual prop. Investors are valuing those moving to an IP landlord space
  • industryleaders: business capability maps current and future critical for impact analysis and EA Live from Austin Open Group
  • theopengroup: Baker: Strategic planning requires architects from both business and technology competencies, a true multidisciplinary team
  • theopengroup: Next up: “The Devon Energy #EA Story” Tim Barnes, Chief Architect, Devon Energy
  • theopengroup: “Devon Energy’s Enterprise Architecture Journey” presented by Tim Barnes, chief architect at Devon presenting an #EA case study
  • theopengroup: Devon utilized an urban planning-like vision to reduce complexity of Devon’s info systems and technologies (the result of 26 mergers)
  • theopengroup: Barnes agrees with Baker: successful #EA requires multidisciplined team that includes non-architects and various kinds of architects
  • larrycincy: Devon Energy got matrixed team with executive sponsorship to ensure EA function success
  • theopengroup: It’s been 2 years since #EA effort began at Devon; $16 million in hard-dollar savings recognized, 227 apps/technologies retired
  • theopengroup: Other successes at devon: Common languages created, permanent business owners for every system across divisions, repeatable processes
  • productmarketer: “227 applications retired. $16m in hard savings” Tim Barnes, Chief Architect at Devon’s Energy presenting #entarch case study at #ogaus
  • systemsflow: Important point in @devonenergy talk at #ogaus: what’s the right mix of consultants & employees for a large organization’s EA practice?
  • theopengroup: Tim Barnes sharing three key successes and seven lessons learned during the course of Devon Energy’s successful implementation of #EA
  • systemsflow: Japanese manufacturing mantra: if you can’t measure it you can’t improve it. True for EA work too
  • practicingEA: Nice observation from Chief Arch of energy company. Everyone defines application differently. W/o common Defn, how can u measure? // Corollary from last tweet…if u can’t define EA how can you measure it’s results? #entarch
  • systemsflow: Devon Energy’s Tim Barnes this morning: Critical to have the business – not IT – deliver EA-related communications.
  • theopengroup: Last plenary speaker today: Mike Walker, Microsoft: “The New World of #EA, from IT Architecture to Enterprise Architecture”
  • theopengroup: Mike Walker, Microsoft speaking: Where is #EA going? What are TOGAF’s complementing methods, models, tools? How does Micrsoft do it?
  • theopengroup: Walker: IT is the business. The two are the same. There needs to be partnership, not just alignment between IT and the business #ogaus >??? – might be true at Microsoft, but in most places IT is part of the business, not ‘is’ the business
  • systemsflow: Microsoft’s Mike Walker: Forget about IT “aligning with” the business; IT is *part of* the business. >(okay, Mike got it right, OG misquoted)
  • theopengroup: Walker: 71% of execs say that IT must be tightly integrated with biz strategy; only 27% say this actually happens (McKinsey)
  • stevenunn: Mike Walker of Microsoft: “Must ensure there’s a balance between IT Architecture and Enterprise Architecture.” >and Mike is one who does understand there’s a difference… 🙂
  • stevenunn: Mike Walker: Also need balance between IQ and EQ (soft/emotional skills). Only the combining the 2 will get EA a “seat at the table”
  • theopengroup: Walker: IQ’s technical know-how must be balanced by EQ, which is motivational/empathetic to customer/stakeholders
  • systemsflow: Good point from Microsoft’s Mike Walker: IQ gets an enterprise architect noticed, EQ (emotional intelligence) gets you further
  • stevenunn: Mike Walker: “EA connects strategy & implementation” // Mike Walker of Microsoft: “We believe in The Open Group’s tagline [mission] of Boundaryless Information Flow.”
  • systemsflow: Interesting quandary for a technology product company (e.g. @microsoft) who also sells EA services: can it “eat its own dogfood”?
  • stevenunn: Mike Walker of Microsoft “3 things to remember for EA: mindset, methods, & make it happen”
  • theopengroup: Walker: Microsoft’s framework leverages many other frameworks, including TOGAF; Most important is common vocabulary
  • henryfranken: Nice quote today in Austin (#ogaus) by Mike Walker: ‘Microsoft is actively using ArchiMate in our engagements with end customers’
  • theopengroup: Heading into tracks! World Class #EA Workshop; Professionalizing the Discipline of EA; Strategic View of Secure Computing in 2030
  • systemsflow: Peter Haviland in “World Class EA” talk at #ogaus – US regulatory regime provides “happy hunting ground” for EAs. Don’t we know it…
  • systemsflow: Rolf Siegers from Raytheon: Big difference between trained architects and certified architects. >but what’s the difference? – oh well, I guess that’s why we go to conferences… 🙂
  • systemsflow: How do architects get extracted from SWAT project-level problem-solving? First: be paid not by a project but by operations
  • systemsflow: Greg Akers: EA documentation into the wrong hands is a huge threat to an organization
  • systemsflow: Architectural significance: useful concept/litmus test for what IT projects need an EAs attention
  • systemsflow: Is there a reason the “Architecture at the Project Level” block in @theopengroup EA capabilities map is red?? 😉
  • Technodad: Whitlock at #ogaus: We moved the world economy to the Internet – without a backup plan. >v.good point… #entarch #economics
  • jamestaulbut: RT @theopengroup: RT @systemsflow:  <so who carries the can for tech delivery excellence? Also ops with give them the service issues. // also architects need to take responsibilty for their architectures and not sit in ivory towers
  • systemsflow: Brian Hopkins from @Forrester makes good point about Big Data projects – business use them to flip requirements/solution sequence
  • systemsflow: Cute concept from Brian Hopkins @Forrester – “Dirty ODS”. 360 customer view solutions are largely unicorns. Mash it up instead?
  • larrycincy: Brian Hopkins @Forrester – “No data is discarded anymore” at one company
  • mikejwalker: #entarch can learn from Benjamin Franklin “Vision without implementation is hallucination”. EA connects strategy to implementation >strong agree
  • systemsflow: Job descriptions are independent of roles, but often cause confusion among project participants. (Hint: Use a RACI matrix.)
  • systemsflow: James Stikeleather makes an observation regarding the “life safety” issues we face due to the tie between cyber and physical worlds. >yup – which is why calling #itarch ‘#entarch’ is so darn dangerous…

systemsflow: Raveesh Dewan:  Enterprise Architects at CareFirst are centrally funded (not project funded.)  Project partners not project members.

  • aogeacolombia: ea is about people, enterprise and it capabilities transformation thanks to a clear strategy lets align strategy and execution
  • systemsflow: Refaat Shulaiba now speaking: Rapid Business Transformations in Health Care: A Systems Approach
  • systemsflow: @BalajiPrasad_ speaking soon.  Enterprise Architect – more than a technologist // One of the most interesting side-benefit of #ogaus is learning about the different business lines our EA colleagues work in
  • systemsflow: The one thing that is common to all our approaches is that there is nothing in common. @BalajiPrasad_
  • systemsflow: Getting “shot at & wounded” is part of the experience required to become a strong EA @BalajiPrasad_ >sadly true… 😐
  • systemsflow: Repeated meme in the #ogaus security track: Pervasive Simplicity. Great example – gmail, send, manage, find email w/minimal effort
  • systemsflow: Business “capabilities” a common theme today at #ogaus. The challenge: Ensuring all stakeholders agree on what the term means. >yep: that’s a big challenge…
  • theopengroup: Final tracks of the day: EA and Biz Strategy; Data and Information Management; Strategic View of Secure Computing in 2030
  • theopengroup: Ramírez: giving insightful, practical advice on how companies in Latin America are relating their #EA to their mission statements
  • theopengroup: Ramírez: Social environment and responsibility part of Latin America #EA philosophy >yes! – real #entarch
  • theopengroup: Now Dave Hornford, Conexiam, speaking on “Accelerating Value: Align Focus to Desired Outcomes & Investment”
  • theopengroup: Hornford: If you want to chase value as an enterprise architect, you need to ask: What problem are we trying to solve? // When orgs shut down EA practice then start up again they’re looking for a solution to a problem. Engage and solve that prob #EA
  • theopengroup: Hornford: Successful EA teams are closely aligned to strategy, clear objectives, deliver up and execute = that is delivering value!
  • systemsflow: #entarch Info sharing shift: From “Need to know” to “Responsibility to share” >strong agree #km #collab
  • systemsflow: Heat mapping of systems getting a lot of mentions as a means of targeting IT investments.
  • systemsflow: Siegers: Establishing certification process can take years but helps ensure everyone is executing architecture process consistently.
  • systemsflow: Mei Selvage of IBM: 1 current challenge: “No information architecture, or architectures don’t land into projects”. What’s worse?
  • systemsflow: “Tacit Knowledge” – aka the ultimate info management anti-pattern: “Don’t write it down”. Make it explicit #entarch >nice idea, but contradicts most #km experience – e.g. Snowden “people know more than they can say, and say more than they can write down”
  • systemsflow: Siegers: Requiring architecture review board members to be certified enhances their credibility in evaluating others’ work.
  • systemsflow: Deloitte’s William Sheleg spoke earlier on EA and Business Transformation: How to Architect for the Future.
  • systemsflow: Sheleg: Future architectures require understanding the aspirations, strategic priorities and capabilities req’d for…
  • systemsflow: Sheleg: Evaluate target capabilities in terms of business value, risk, and affordability to identify path(s) to the future.
  • systemsflow: Eugene Imbaba of IBM: “I don’t want 3g/4g/etc – I want phone service” – solution architecture models shld avoid lingo
  • systemsflow: Mei Selvage of IBM’s response to “what about ‘good enough’ data quality?” – depends on business – core/non-core? Sliding scale

  • theopengroup: Starting the morning with Open Group CEO Allen Brown and Dr. Peter Alterman, NIST, setting the stage for #security & #Cloud plenary
  • mikejwalker: Peter Alterman – “I don’t call it cloud, I call it fog” #entarch
  • theopengroup: Peter Alterman, NSTIC: “Industry knows a whole lot more about you and me than government does”
  • mikejwalker: Alterman – Don’t worry about the government knowing too much about you,the private sector has much more information on you #entarch
  • theopengroup: NSTIC goal by 2016: ability to choose among various identity providers and electronic identity credentials for secure transactions
  • systemsflow: Dr. Peter Alterman now speaking on the Digital Identity Challenge. // Alterman: We as users/consumers are all responsible for what privacy standards and expectations look like. // Alterman on NSTIC: We think we can have security and privacy without losing our civil liberties.
  • mikejwalker: NSTIC wants to avoid a George Orwell 1984 scenario to protect privacy and civil liberties
  • systemsflow: Dr Peter Alterman of NSTIC is quite a comedian. Who knew trusted identity was so fun! #entarch
  • theopengroup: Alterman: “I think we can have privacy without losing fundamental civil liberties”
  • theopengroup: Alterman: there is interest in NSTIC initiatives by social network providers… but not all, notably a “major player”
  • systemsflow: Alterman: There is no single solution to identity problem.
  • JWGaus: @mikejwalker re:Alterman #entarch Yeah I was surprised Google+ didn’t fill out my profile for me.
  • theopengroup: Alterman: Smart credential-based ID cards are already being used but won’t be whole solution; no need to stifle innovation

  • mikejwalker: Learned that Armadillo’s contain leprosy but humans originally gave it to them! So don’t eat them or it’s payback…
  • systemsflow: Brandon Dunlap of BrightFly up now talking about cloud computing lessons learned.
  • mikejwalker: ISACA Risk/Reward Barometer US Edition says that 41% of its survey participants feel that the risk outweighs the reward of #cloud
  • theopengroup: Brandon Dunlap, Brightfly, now speaking on “What I’ve Learned in 10 Years of Cloud Computing” // Brandon Dunlap, Brightfly: Are we as security blocking the adoption of a technology that would be hugely beneficial to biz – Cloud?
  • mikejwalker: Brandon Dunlap – #cloud limits our visibility in #security controls. I disagree. Often times they are more secure than on-prem
  • JWGaus: @mikejwalker #cloud being more secure and having less visibility are not mutually exclusive.
  • theopengroup: Dunlap: Workers with a credit card are the new IT department; they are going out and procuring services that you are unable to vet // Dunlap: The weakest link in Cloud security is not technology, it’s the people, mostly those procuring low-cost services = Rogue IT
  • systemsflow: Dunlap: Business users with a corporate credit card buying cloud-based services are the new “rogue IT” // Dunlap: Individuals are still the weakest link in security, and especially when using #cloud services / SaaS.
  • mikejwalker: Dunlap providing great tips to get in front of cloud security and operational risks
  • dave_mcnally: Brandon Dunlap at #ogaus “in many cases they (cloud providers) can do IT better than us”
  • mikejwalker: AMR: NA companies are estimated to spend $29.9B on reg compliance and will spend $8.8B this year on technology solutions #entarch
  • systemsflow: Big message from BrightFly’s Brandon Dunlap: cloud providers (Dropbox, Google, 37 signals, etc.) need to publish security controls // @bdunlap 1st response to “InfoSec too expensive” argument – save $$ by ditching half your security app portfolio as redundant
  • theopengroup: Dunlap: You need to understand the business that your organization is in so you can protect it. Talk to people find their pain points >yes – my point exactly – #entarch is about people first, tech second
  • mikejwalker: Ben Franklin – “Any society that would give up a little liberty to gain a little security will deserve neither and lose both.”
  • systemsflow: Fantastic, practical, and fun presentation by Brendan Dunlap of Brightfly on how to get a handle on #cloud security risks.
  • theopengroup: Now listing to Andras Szakal speak about The Open Group Trusted Technology Forum (OTTF)’s accreditation program
  • theopengroup: Heading into morning parallel tracks: Architectural View of Security for the Cloud; Business Architecture; Data Quality & SI
  • systemsflow: Tony Carrato makes the point of the importance of the process to make and record architecture decisions. // Carrato: Record architecture decisions and solve a problem only once.
  • systemsflow: UDEF = framework to build a metadata-based data architecture for your biz that stands a chance of interoperating w/others
  • systemsflow: UDEF IDs like Dewey decimal #s for objects & their attributes #entatch
  • systemsflow: Surprising that UDEF has only 2 adopters & 1 is @theopengroup. Interoperability needs numbers
  • systemsflow: Interactive architecture decision session led by Carrato and @omkhar.  Skills building at #ogaus // UDEF mapping exercise forces a deliberate, repeatable normalization of data models
  • systemsflow: UDEF success use case: multinational merger, convert Chinese HR system to US easy if both already UDEF-mapped #entarch
  • theopengroup: Sitting in on #BizArch track: Kevin Daley of IBM discussing Business Architecture Building Blocks //Big audience today for the Business Architecture track.. a discipline whose time has come, perhaps? Forum has formalized a definition
  • practicingEA: RT @theopengroup: Big audience today for the Business Architecture track.. an idea whose time has come #forrester agrees
  • systemsflow: IBM’s Kevin Daley: A well-defined biz arch covers strategy, technology, & operations domains + governs their intersection. >oops… this looks suspiciously like an (incomplete) #entarch definition, not a #bizarch one…
  • systemsflow: Kevin Daley: You [inadvertently?] change your biz strategy every time you budget by choosing where you spend.
  • visualmodeling: Daley: “Organizations will have a cultural affinity to a specific biz arch perspective.” // Yes!  Use the capabilities you have!!
  • theopengroup: Daley’s BizArch track: Now capturing audience observations and reactions about the #bizarch building blocks
  • systemsflow: Daley: Biz architecture evolves holistically – no one stops doing business for a year to develop their biz architecture.
  • LarsHouge: Could it be a good idea to include an information architect in the work related to the Business Architecture Method Framework? >sounds wise… and maybe even some business-architects too? 😐
  • systemsflow: Nice reminder during Q&A: Importance of accepting and not debating feedback when seeking feedback.
  • LarsHouge: The BA definition was good, but it seems like the Method Framework is less mature, ex. a clear link to the BMM stuff. #entarch
  • systemsflow: Interesting #bizarch Q&A comment: Biz arch is as much about connections between orgs as about the orgs themselves. #stillparsing >this is news…?!?
  • systemsflow: Another comment in the #bizarch track. Let’s avoid EA landgrabbing and competing with MBA-type biz strategy field. >yep – for biz-strategy, EA is decision-support, not decision-making
  • krismeukens: RT @systemsflow avoid #entarch landgrabbing & competing w MBA-type #biz strategy #bizarch < circular rather than linear causality
  • systemsflow: Interesting #bizarch debate during Q&A.  Does #EA = #bizarch + #techarch?  Or does #bizarch include technology as well? >oh not, not again… this is positioning bizarch as entarch – which it isn’t!
  • theopengroup: More post-lunch tracks: Security Architecture, Business Architecture, TOGAF/SOA
  • systemsflow: Sitting in with Gail Wright and Peter Haviland on getting started with business architecture. #bizarch
  • systemsflow: Wright/Haviland: The #bizarch focus is at the intersection of Strategy, Operations and Technology. >oops… that’s not a good start… implies business-centric ‘EA’ rather than a proper separation of bizarch and #entarch
  • systemsflow: For #bizarch approach, as in all things except elastic waist pants, one size does not fit all!
  • systemsflow: Q: What do biz leaders expect from #bizarch? A: Nothing, because they don’t know what it is. (Because we can’t tell them!) >yes, that’s painfully obvious. and OpenGroup and the big consultancies have consistently screwed things up by presenting bizarch as ‘something to do with IT’, when in reality it barely touches IT at all… ::sigh::
  • systemsflow: Governance unwrapped: Whoever controls the purse, in truth makes the architecture decisions. #bizarch >that may be ‘business-reality’, but it’s really, really dumb: what happens if ‘whoever controls the purse’ doesn’t understand the context?
  • systemsflow: Haviland: “Sitting around white boarding is not architecture.” #bizarch  // Yes! Don’t confuse motion with progress. >having proper conversations around a whiteboard with real implementors is architecture, ‘motion’ without agreed direction is not…
  • systemsflow: Make sure what you architect is implementable and implemented. #bizarch >yep – that’s what those whiteboard conversations are for…
  • systemsflow: Iver Band: Modeling needs of RBAC met using the strengths of #SABSA, #TOGAF, and #ArchiMate.  Use of multiple tools shown at #ogaus.
  • systemsflow: Trulove from Sailpoint: #Cloud allows biz the opportunity to “go rogue” and avoid IT. Future audit woes brewing? >yup… 🙁
  • theopengroup: Rounding out the day with more tracks: Digital Identity, Business Architecture and #SOA
  • systemsflow: Sitting in with Mieke Mahakena & Erik Proper to discuss the role of the business architect. #bizarch
  • systemsflow: Mahakena/Proper: biz architects focus on broad view of operations; biz analysts focus on solution-specific reqs. What do you think? >agree – as long as analysts are not solely assumed to be ‘part of IT’
  • systemsflow: Great insight from Len Fehskens: For any architect, it’s less about what you know and more about what you know how to do. #bizarch >…and who you know who can (help you to) do what you don’t know how to do 🙂
  • LarsHouge: Influencers-ends-bus capabilities-means-tech capabilities-ABB’s-SBB’s. Certified, but still a little bit frustrated… Need beers.
  • CH_FEDARCH: @LarsHouge Might “lessen” – add? – frustration: Capabilities should be treated ABBs, for they’re not “Detail”, but rather ‘Gestalt’ // Additionally, usefulness of those concepts depend on “planning mode”: “Strategy4Direction” or “Strategy4Implementation”
  • togaf_r: Official ArchiMate resource:online spec – mobile edition at http://ow.ly/5IS1G #entarch #itarch #archimate
  • togaf_r: Read the smartphone/tablet friendly edition of TOGAF on our mobile site http://ow.ly/5ISv4 #entarch #itarch #togaf

—-

  • theopengroup: Welcome to Day 3 of The Open Group Conf/Austin. No plenary; going into tracks #Cloud Roadmap/Strategy; ArchiMate, Aligning IT and Biz // The program for today’s conference is available at http://ow.ly/5EVl5 and on the mobile site at http://ow.ly/5EVmK
  • systemsflow: Mark McCormick kicking off Business Alignment Track talking about IT Transformation. #bizalign
  • systemsflow: Defined business strategy is a prerequisite to IT Transformation.  Can’t hit the target if you can’t see it! #bizalign
  • systemsflow: Mark McCormick shows that the Starbucks value map drives sbux arch decisions.  Mark is speaking @systemsflow language! #bizalign
  • systemsflow: McCormick: “making pictures to show the business” a critical part of the IT #bizalign process. // We are grokking!
  • systemsflow: McCormick: Discussing the importance of a IT charge-back model, or at the very least, IT cost visibility to the business. #bizalign
  • systemsflow: Bill Cason beginning his talk on #bizalign at #ogaus
  • systemsflow: Bill Cason: Biz arch benefits – improve IT portfolio/execution as well as biz performance/model #bizalign
  • systemsflow: Cason: Use a “capability lens” on your application portfolio to have a fact-based discussion with the biz. #bizalign
  • systemsflow: Cason’s capability map clearly shows if IT investments align with biz needs #bizalign
  • systemsflow: Assets are the lang of IT; capabilities the lang of biz.  #bizalign must provide Rosetta stone for IT to talk to biz.
  • systemsflow: John Dohm: We need to move away from IT being a silo to IT being an integral part of the business. #cloud // Yes! But why haven’t we?
  • systemsflow: Dohm: IT consumers will drive adoption of cloud services; IT will be left cleaning up after them. #cloud // Get agile or move aside!
  • systemsflow: Gloria Killen of Intel: Biz strategy drives EA principles. EA principles drive IT building codes
  • systemsflow: Bill Brierley of TRM Technologies:  “Whenever you put an EA program in place it is a fundamental shift.” Culture shock poses problems
  • systemsflow: Ken Street: #KM and #EA are at similar levels of maturity [acceptance?] within orgs – struggling for full value equation buy-in.
  • systemsflow: Brierley: EA is about recognizing the collective wisdom of your org. It requires a key set of soft skills that not everyone has.
  • systemsflow: Your #entarch repository is like a garden that requires constant cultivation. Street: Reuse, Reduce, Recycle
  • theopengroup: Going into afternoon tracks: #Cloud #EA & Deployment; Agile Business Architecture; #TOGAF 9 Case studies. Impressive speaker lineups
  • theopengroup: Sitting in on Stephan Amsbary’s interesting presentation on the US power grid and an associated #TOGAF case study
  • theopengroup: Amsbary: evolving to a smart grid, pervasive computing that includes billions of devices, monitoring by tens of 1000s of applications
  • theopengroup: Now sitting in on TOGAF 9 Case Study: eGovernmental Services and Public Investments in Norway by Lars Christian Houge
  • theopengroup: Houge: Norway decided on TOGAF to help it a change concept with the highest possible economic returns and best use of public funds
  • togaf_r: Houge: TOGAF and the ADM gave us a “kick-start”, common vocabulary, common understanding, roles and responsibilities
  • theopengroup: Final tracks of the day coming up: Holistic #EA; Paths to Creating Successful #Cloud Computing Solutions. OR: #TOGAF Camp!
  • BalajiPrasad_: “takes an org to deliver on EA.  An Architect’s role is no more important than an analyst, manager, etc.” – Tim Barnes #ogaus #EA
  • BalajiPrasad_: “#EA is not well understood outside of #architecture teams” – Chris Forde.  So he prefers “strategy”, “planning” etc. with others.

And a handful of follow-up summaries and pointers to presentations:

Posted in Business, Enterprise architecture Tagged with: , , , , , , , ,

Leave a Reply

Your email address will not be published. Required fields are marked *

*