Free TOGAF 9 Exam Simulator and Sample Questions

Manuel Di Toma has created a great resource for Enterprise Architects looking for TOGAF 9 certification. He built a set of TOGAF 9 simulation tests to help prepare you for the big test. Manuel ensures that all the resources in…

Rumination on the concept of “best practice”

I heard some very interesting talks today from Len Fehskens and Jeff Scott at the Open Group conference.  One thing that I picked up in a meeting yesterday was the notion that TOGAF 9.1 is built on “best practices.”  Today, as Jeff spoke about the transformation of a technical architect into a business architect, and as Len spoke about the challenges of communicating complex ideas, the notion of a “best practice” kept bothering me, and I cross-pollinated my concerns with the concepts that they were sharing.

I agree that the intent of the people who shared their practices with the Open Group was to provide practices that can be taught and followed.  I even agree that the people on the TOGAF committees that accepted the content felt that the practices represented the best that the industry had to offer at the time.  But I wonder if any of the work done in framework committees of any stripe (not to pick on the Open Group) can be held to the standard of being a “best practice.”

Are the practices in the TOGAF framework truly “best��� practices?  Are these practices the best ones that the EA field has to offer? 

I guess I would have to follow the EA rabbit hole and ask “what criteria do we use to judge if a practice is the best one?”

After all, when Jeff Scott talks about business architecture using capability modeling, he believes that the practice of capability modeling is the best one to use for the results he is trying to achieve.  (I nearly always agree with Jeff, BTW.  We sometimes differ in language, but nearly never in approach).  That said, as much as Jeff and I agree, our agreement does not mean that the practice should be considered a “best” practice.  Who are we to say?  We are practitioners.  While that is good, it is not enough in my mind to qualify the practice as “best.”

To be a best practice, in my opinion, a method or approach has to meet a higher bar.  There has to be evidence that it is, in fact, better than just a “good practice.” 

I think a best practice should have:

  • Some measurement (evidence) that demonstrates that it is an effective practice, and that the measurement shows that it is at least as effective as other practices,
  • A clear understanding of the results of the practice and the context in which it is to be performed (think “Pattern Language” criteria),
  • Some analysis to show that it meets other criteria like broad applicability and simplicity, and
  • We should demonstrate the ability for that practice to be understood and performed by people who are currently in the role (e.g. can we teach it, and if we teach it, can others do it?).

 

I wonder if we went through most of our frameworks and highlighted the text that is able to meet a higher bar, like the one I describe, how much of the text would we cover?  2%?  10%? 

Is 10% coverage enough to say that a framework is based on best practices?

Successful Enterprise Architecture using the TOGAF® and ArchiMate® Standards

The discipline of Enterprise Architecture was developed in the 1980s with a strong focus on the information systems landscape of organizations. Since those days, the scope of the discipline has slowly widened to include more and more aspects of the enterprise as a whole. Architects, especially at the strategic level, attempt to answer the question “How should we organize ourselves in order to be successful?” Continue reading

Flying in the Cloud by the Seat of Our Pants

In the early days of aviation, when instruments were unreliable or non-existent, pilots often had to make judgments by instinct. This was known as “flying by the seat of your pants.” It was exciting, but error prone, and accidents were frequent. Today, enterprises are in that position with Cloud Computing. Continue reading

2013 Open Group Predictions, Vol. 2

Continuing on the theme of predictions, here are a few more, which focus on global IT trends, business architecture, OTTF and Open Group events in 2013. Continue reading

Togaf and GERAM

[amazon_image id=”3642055664″ link=”true” target=”_blank” size=”medium” ]Handbook on Enterprise Architecture (International Handbooks on Information Systems)[/amazon_image] Some time ago I read this book on Enterprise Architecture, which is a compilation of various chapters about the GERAM framework for Enterprise Architecture. Now, while very extensive it seems that GERAM is dead. The last publications on the standard date […]

Het bericht Togaf and GERAM verscheen eerst op Rob Vens.

Invention (Innovation) Not Strategy Creates Renaissance – Moving from Darwinian Adaptive to Generative Transformation

Invention (Innovation), Not Strategy Creates Renaissance. Most Darwinian concepts does not engender to developing creativity, and so to innovation. Instead it is about strategy for developing dominant position, this is not a sustainable model as history has shown. Instead, Enterprise Architects should begin reinforcing energy into lost opportunities in innovation and explore to create newer […]