Quotes:
Good decisions come from experience, and experience comes from bad decisions.
You never learn anything when you're talking.
Spagetti Code to Ravioli Code (more modular)
Most ideas die in your head or around the table of friends or colleagues; start something
Henry Ford was heard to say, "If you do what you've always done, you'll get what you always got!"
Drucker: Culture eats strategy for breakfast (lunch)
Tell me how [and when] you'll measure me, and I'll tell you how I'll behave
What gets measured, gets done.
Nobody ever 'growed' a hog by weighin' it
Plant lots of seeds; 1% of the seeds turn into 50% of the flowers. Basic Garden Math.
Douglas Mc Gregor:
Theory X (managers believe people are lazy and must be motivated and controlled)
Theory Y (people are basically self-motivated and need to be channeled and challenged)
http://www.accel-team.com/human_relations/hrels_03_mcgregor.html
Dr.Eli Goldratt
"Tell me how you'll measure me, and I'll tell you how I will behave. If my measurements are not clear, no one can predict how I will behave, not even me." - Dr.Eli Goldratt, gives the direction for a metrics solution, according to a methodology called the Theory of Constraints,or TOC for short
Negotiation:
Always leave money on the table for your partners. Not only will you be very rich, you will be very happy. If you allow your partners to benefit from the deal, they always come back and want to do business with you. There will never be a shortage of opportunity.
It is the man who goes to the table to ask and squeeze for the last nickel who is never happy. Do you know why? It is because that person leaves the table, typically getting the nickel, but then hates himself for not asking for the two nickels. As a result, he is never happy.
I immediately thought about all of the people I knew from Wall Street who were very rich, but also miserable. While I may be driven to the point of driving those around me crazy, I have never let success stand in the way of my happiness. And, as I've put this advice into practice in the years since that meeting, I have also realized the value of many other forms of capital. Again, as described in Goodbye Gordon Gekko:
Capital is not only cash, stocks, and real estate. Capital is any asset that you can store and rely upon, and it comes in many forms. There is capital in economic terms, which consists of investment assets, cash, and things like equipment on a company's balance sheet. There is also human capital, which is made up of those who work with you. When you establish healthy win-win relationships with people, your capital account grows and can earn you a lot of dough. But accumulating enough of any of those can only happen if you trust that your actions are worthwhile no matter what the return.
The method of principled negotiation is based on five propositions:
"Separate the people from the problem"
"Focus on interests, not positions"
"Invent options for mutual gain"
"Insist on using objective criteria"
"Know your BATNA (Best Alternative To Negotiated Agreement)"
NYT Article on Amazon Culture:
"It would certainly be much easier and socially cohesive to just compromise and not debate, but that may lead to the wrong decision."
Amazonians are instructed to "disagree and commit" and "to rip into colleagues" ideas, with feedback that can be blunt to the point of painful, before lining up behind a decision.
Friday, November 4, 2016
Zachman vs TOGAF Comparision
Enterprise Architecture Framework Goals
The Zachman Framework is based on the idea that the same complex thing can be described for different purposes in a different way with different types of descriptions. The main goal of Zachman framework is to enable different persons to observe the same thing from various perspectives.
The main goal of the Open Group with TOGAF is to create an industry standard. They are trying to develop a tool and repository for experience-based, practical information on how to act when it comes to the enterprise architecture processes. Also, it provides a specific technique with particular sets of architectural assets, strategies and deliverables can be integrated.
Closer Comparison of the Zachman Framework and TOGAF
TOGAF is one of the enterprise architecture software tools which provide a far-reaching approach to the planning, design, implementation and use of enterprise architecture. It has 4 domains:
• Business - specifies the business strategy, administration, organization and important business processes in the company.
• Technology - presents the software, hardware and IT infrastructure required for the setup of core applications.
• Data - presents the structure of the physical and logical data resources and related information management.
• Application - defines the model and interactions for the application frameworks to be setup to the core company's processes.
TOGAF also includes a set of tools in order to enable enterprise architecture team to picture the present and future state of the architecture. This includes:
- a list of recommended standards
- a method used for defining information as building blocks
- information on how these building blocks can fit together
- a common vocabulary
The Zachman Framework, on the other hand, is very generic and applies only to enterprises.
The Zachman Framework is a simple logical structure for organizing and classifying items developed in enterprise architecture. It uses classification methods from engineering and architecture. There are 6 viewpoints in the 6 rows of the Zachman Framework:
1. Row - The Scope (Contextual) – directed to the planner
2. Row - The Business Model (Conceptual) – directed to the owner
3. Row - The System view point (Logical) – directed to the designer
4. Row - The Technology viewpoint (Physical) – directed to the builder
5. Row - The Detailed Representations viewpoint (Out of Context) – directed to the subcontractor
6. Row - The Functioning Enterprise viewpoint
The 6 questions which they have to answer are:
- The Data aspect – What?
- The Motivation aspect – Why?
- The Network aspect – Where?
- The Time aspect – When?
- The People aspect – Who?
- The Function aspect – How?
Basically, the Zachman framework is used for descriptive representations of any complex models and it does not describe any particular EA method, technique or tool.
source: EAComposer Article
The Zachman Framework is based on the idea that the same complex thing can be described for different purposes in a different way with different types of descriptions. The main goal of Zachman framework is to enable different persons to observe the same thing from various perspectives.
The main goal of the Open Group with TOGAF is to create an industry standard. They are trying to develop a tool and repository for experience-based, practical information on how to act when it comes to the enterprise architecture processes. Also, it provides a specific technique with particular sets of architectural assets, strategies and deliverables can be integrated.
Closer Comparison of the Zachman Framework and TOGAF
TOGAF is one of the enterprise architecture software tools which provide a far-reaching approach to the planning, design, implementation and use of enterprise architecture. It has 4 domains:
• Business - specifies the business strategy, administration, organization and important business processes in the company.
• Technology - presents the software, hardware and IT infrastructure required for the setup of core applications.
• Data - presents the structure of the physical and logical data resources and related information management.
• Application - defines the model and interactions for the application frameworks to be setup to the core company's processes.
TOGAF also includes a set of tools in order to enable enterprise architecture team to picture the present and future state of the architecture. This includes:
- a list of recommended standards
- a method used for defining information as building blocks
- information on how these building blocks can fit together
- a common vocabulary
The Zachman Framework, on the other hand, is very generic and applies only to enterprises.
The Zachman Framework is a simple logical structure for organizing and classifying items developed in enterprise architecture. It uses classification methods from engineering and architecture. There are 6 viewpoints in the 6 rows of the Zachman Framework:
1. Row - The Scope (Contextual) – directed to the planner
2. Row - The Business Model (Conceptual) – directed to the owner
3. Row - The System view point (Logical) – directed to the designer
4. Row - The Technology viewpoint (Physical) – directed to the builder
5. Row - The Detailed Representations viewpoint (Out of Context) – directed to the subcontractor
6. Row - The Functioning Enterprise viewpoint
The 6 questions which they have to answer are:
- The Data aspect – What?
- The Motivation aspect – Why?
- The Network aspect – Where?
- The Time aspect – When?
- The People aspect – Who?
- The Function aspect – How?
Basically, the Zachman framework is used for descriptive representations of any complex models and it does not describe any particular EA method, technique or tool.
source: EAComposer Article
Subscribe to:
Posts (Atom)