Tag Archives: Togaf

The Buzz about Togaf as an essential Transformation Framework tool kit for Architects

 

 

 

 

 

Just saw the above job ad from my linkedin feed and this one talks about the company needing a security with a T skill profile.  Meaning have deep dive skills in one or two areas and broad based skills in other areas. Togaf that way has been mixed and matched with other architect skills like Security , Infra , Business , Data , Domain , Functional , Technology architecture domains. This helps a professional have a broad based skill or outlook when they reach a certain career progression path. So one typically gets into the question of what is needed to be an architect . Here is a link on what would be needed to become a good architect for the ones who may want to make that career progression. Steps to transition into an architect path .

The ancient definition of an architect was that he/she should be a many of letters , arts , science , literature , music , architecture ( building / landscape ) etc. Meaning that you should be a Da Vinci to really have that title. But it is not that bad if you are planning to become a solution , IT or enterprise architect. As we all can’t be Da Vinci’s to fill that slot.

Kiran , so if you are wanting to make that transition happen or be exposed to that body of knowledge to help you with having an architect’s mindset then Togaf comes to the rescue.

Mind you it is not really needed to have a certification to become a good architect. But certifications expose one to a body of knowledge that companies and peers value. You may possess this knowledge by virtue of being in a certain role or vantage point in a company.

Every skill you acquire doubles your odds of success. Scott Adams

 

What does Car Service and Architecture Compliance reviews have in common ?

I had given my car for a service recently and it so happened that I was driving it around the city for couple of days post the service. Was getting a wobbling feeling on the left front wheel of the vehicle  it then occurred to me that there could be something that could be a problem on that side of the wheel.Took the vehicle back to the car clinic only to find that the wheel post service as fixed back in place using only two nuts out of the four . It was lucky to have noticed it at least at that point of time. Did advice the floor manager to put back the wheel tightening part in the vehicle checklist before commissioning the vehicle that it is fit for the roads. It was an eye opener for the importance of having set rules and checklist for anything in your life , be it planning a trip with friends and family , checking items off your to do list or even it that means delivering software or architecture the right way.  A checklist’s value is immense and is only known when you have missed something in the case of the car the crucial wheel nuts itself . As we could see that the lynch pin if it goes missing then it can be life threatening. Similar is the case with creating a product or a service , it can be mission critical if you miss that important nut or bolt that shall latch the end product.

Let’s us look at the above process which is detailed as a part of the Open Group Togaf which talks about creating an architecture compliance review process . As you can see the whole process starts off by having an architecture lead who leads the process and continues the whole chain of activities in between looks at a checklist to see all the nuts and bolts are in place and tight.

So What can be few of the checklist

  1. Hardware and Operating System Checklist
  • How does the system design impact or involve end-user devices?
  • What is the quantity and distribution (regional and global) of usage, data storage, and processing?
  • What applications are affinitized with your project by similarities in data, application services, etc.? To what degree is data affinitized with your project?
  1. Software Services and Middleware Checklist
  2. Applications Checklist
  3. Security Scrutiny Checklist
  4. System Engineering Methods and Tools Checklist.
  5. Application Integration Checklist….etc 

 

So what is your story around checklist . We all agree that they are the must have in an software professional’s toolkit.

Self Paced Elearning- Agile Enterprise Architecture for the Digital World

 

 

 

 

 

 

 

 

 

 

 

 

Overview:

Agile Enterprise Architecture Essentials. What is Agile Enterprise Architecture? How to apply and relate to this in your organization ?

Architect there are many types which one are you ? What is your aspiration ?

What does it take to become an Enterprise Architect with agility in all your interactions and touchpoints? What key skills and frameworks are in use ? What tools and methodologies are in use and how you can leverage them effectively ?
Build your organizational specific EA story. Evaluating Architecture trade off decisions and arriving at a best fit architecture. Covering EA and its practice with real life examples on how to leverage EA in your organization.

Learning Objective:

• Enterprise Architecture and how to practice it ?

• What skills to learn and how to apply EA skills at work and add value?

• Overview of various popular frameworks and its application.

• How to do architectural trade off decisions.

• How to practice EA and how to apply them to real life situations.

• How to prioritize architectural roadmap items and drive decisions?

• Build an EA story that suits your organization and the one that works for you.

Prerequisite:

Basic Understanding of Architecture, Familiarity of having worked in either a big or small software project and passion for architecture and to do things better. Have used architecture / design principles in the course of work helps.

Overview:

Agility and Architecture are two wheels that makes an organization move ahead when in balance. What is the right balance to have them work for your organization? How can you balance it and at the same time achieve business results, transformations and even simple align your organization goals in the right direction.

Course Takeaways:

You will be able to mix agility and know how architecture relates to it. Very useful for a solution architect, enterprise architect as you move along your career path and how to apply Togaf EA framework in practice. Practical knowledge of TOGAF 9.1 and help you with clearing the TOGAF Certification and become a TOGAF 9.1 Certified Architect. A case study will run through the course which will help get the practical side of using and tailoring TOGAF 9.1 for your organization.

Who Should Attend:

Course Content:
Module Leads,
Business analysts,
Project Managers,
Managers working on enterprise architecture projects,
Business Leaders in transformational roles,
IT Architects , Solution Architects
Integration folks in client facing roles,
IT professionals wanting to become IT, Software and Enterprise Architects.
1. Enterprise Architecture and Agility
2. TOGAF 9.1 and Real World Application
3. TOGAF 9.1 Tools and Techniques
4. TOGAF with other frameworks
5. TOGAF Customization
6. Become TOGAF Certified Practioner
7. ADM and how architecture is iterated and developed.

Detailed Outline

Workshop Objective:

* The objective is to help the participants understand Enterprise Architecture and TOGAF for its practical application.
* How to align the business and IT aspects of your organization together?
* Understand TOGAF 9.1 and how it can be tailored for an Organization.
* How to go from strategy to execution when posed with having to find a solution to a customer problem?
* Basics of Architecture Frameworks (Zachman / Togaf) and how to apply them.
* How to dive deep from Enterprise Architecture to Solution Architecture.
* Architecture and Design how to apply them to practical scenarios.
* Solution Architecture and how to custom tailor solutions based on customer needs.
* Requirements Prioritization for an Architect.
* Agility and an Architect. How much architecture is just needed for the hour and how much later?
* Project Management essentials for an Architect…

Learning Objective:

• Enterprise Architecture and how to practice it ?

• What skills to learn and how to apply EA skills at work and add value?

• Overview of various popular frameworks and its application.

• How to do architectural trade off decisions.

• How to practice EA and how to apply them to real life situations.

• How to prioritize architectural roadmap items and drive decisions?

• Build an EA story that suits your organization and the one that works for you.

Request for a quote : Individuals or Corporates looking forward for this course please send a mail to maileturnti@eturnti.com .

Will there by a participation certification ?  

Yes there shall be a participation certification acknowledging on the concepts learned.

 

Value Stream as an Essential Tool for Architects…

This topic came to my mind while I was chatting with my cousin over the weekend who was presenting on this topic as a part of the CII ( Confederation of India Industry ) conference. He works for a mechanical company and was to present the business benefits in his company. They had optimized their existing set of process to reduce the cycle time of churning new products. They had mapped their existing process structure from the point where the raw materials are procured to the place where they undergo various levels of transformation / integration to finally give that polished output. This happens as a part of various business process work flows. He had his presentation ready and was to explain how useful this technique is for extracting maximum enterprise value in an organization.

What does Value Stream mean to an architect ?

value chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement.

Porter’s Value Chain analysis is used to develop a focus on those activities within your Company that significantly add value and thus give you a competitive edge. For instance, if your team is very good at analysis and design such that you can define and bound a problem better than anyone else in the world, you could put in a process to continually implement new design and analysis methods and disseminate that throughout the organization so that you are always the best. And you can lead with that in your marketing efforts by calling that out as a “feature” and highlighting the benefits to the customer of lower development cost, more robust solutions, etc. Value Chain Analysis is a way to get at your key competencies which create differentiated products and services.

Although the above diagram can look like more of an MBA kind of material trying to unify the business problem and the IT solutions to plug the same. As you progress in your careers you are expected to understand both the business and the IT sides of the equation well and this is a useful tool to help one with the mental model for the same. This is very useful in getting discussions started with the customer and quite handy during consulting and internal process revamp exercises.

As far as architects are concerned their efforts should be focused on activities that bring the highest business value to the organization and the customer. This needs them to understand in the sense of what constitutes primary and secondary activities that bring value to the end customer. Once this is understood the organization can pull the strings in the right direction and focus its efforts in the right direction. Here is leaving you with a brief intro video on what is value chain https://www.youtube.com/watch?v=g8p2H7EvoGM.

Getting your requirements right the first time is all you need…

Most often getting business architecture requirements right is a challenge and it means there are two types of people who need to converge at a common point to where they could make sense it each other. The business people are concerned with the business side of things and look at the picture from an angle which could be quite different from the IT folks. For example the IT team is worried about building requirements that are more better versions of working software or rather refinements in releases but the business is concerned about what business value will this piece add to the overall product strategy or solution point of view. Many a times it so happens that there is no clear articulation of business value and organizations spend time and effort in producing waste or MUDA ( Toyota / Six Sigma ) prefers to call it. This can happen because in the name of taking up an initiative a wrong requirement was envisaged as having to be completed.  Many a times the requirements although is an art and science by itself and needs to be done with the right focus as all the downstream actions based on this can create mis alignment in the vision and mission of an enterprise. So is there is definitive prescription to doing this , how is this similar to user stories or epics that agile teams talk about . User stories are not enough to detail all possible requirements more so when they depict the end to end system goals where aligning business and IT is paramount. This being the case there needs to be a structure to capture all the actors and details that goes into getting a business scenario right.

Recently been to an IT company where the issue was product owners hand over requirements over email or chat sessions or simply over a phone call. It was said that requirements not getting correctly scoped was the single most productivity loss and created enormous amount of wasteful downstream activities. What has been your experience here ?