
We begin this course with a little bit of personal history on the part of the instructure. He shares his background on how he came to acquire the value that will be delivered in this course. He then proceeds to share why he considers it important to deliver the message of Enterprise Thinking to technical audiences.
Lecture 2 proceeds with a historical perspective of the instructor's career sharing themes that collectively create a turf in typical coporate environments. Technology professionals in corporate organizations find themselves emergesed in these turfs and their associated wars leading to unproductive outcomes such as working in silos and playing the blame game. This is antagonistic to Enterprise Thinking.
Clear definitions of the concept of an Enterprise and the core concept of the course - Enterprise Thinking - are explored in this lecture relying on approapriate sources. More information about the concept can be found in the resources section.
We begin the lecture by exploring the value of enterprise architecture and making a case. The lecture does not market any particular framework or technology. The idea is to share the rationale behind big picture, long term thinking.
We went on to explore the downsides of what some may consider "emergent" architecture and emphasizing the need to think before doing. Architecture is not just documentation, it is planning the implementation. There must be a good enough view of the end state to begin with.
In this lecture, we draw simple lessons from the town planners who built the city of Dubai. The lessons are basic assumptions we could make about any carefully planned city not exact data from the middle eastern city.
Enterprise Architecture is one of the functions that has the greatest capacity to inspire Enterprise Thinking. This lesson discusses the meaning of Enterprise Architecture by disecting Gartner's definition of the concept.
In this video, I share the real-world experience of having to deal with techies who are not very enthusiatic about documenting architecture. When someone does the job of documenting architecture, it is likely it will not be followed. As inconvenient as going through the architecting process is, the effort is worth it in the long term.
We distinguish the expression "architecture" from the related expression "architecture model". Even when an architecture is yet to be explicitly documented, it exists. However, the idea of practicing architecture implies that we become more deliberate about creating models that define what we want to build.
In this seven-and-half minute video, I share a real-world example of a transformation project I was involved in while working for a financial institution. The issues we had to deal with are recounted in the video and used to illustrate the concepts taught in this section - people, process, technology.
In this lecture, we give an overview of a few enterprise functions that are not necessarily technical. This short list of functions is derived from industry experience. They support technical functions to deliver value to the organization in an organized fashion. Techies are encouraged to support such function as inconvenient as it might seem.
In this video, we give more practical insights from a real life scenario on the value of working with enterprise functions as a technology professional.
This lecture focuses on decision making with respect to adopting solutions and rolling out initiatives in a large organization. The process is derives from industry experience and resembles a waterfall approach. However, the learner should be conscious that this course does not address implementation (HOW) but design (WHAT). In many cases, design must be sequenced behind implementation.
This course has been developed as a response to gaps observed in the way technology subject matter experts work. Stringent KPIs, competitive postures and plain old politics are typically strong influences in the way IT units deliver their work in large organizations. Technology experts tend to compete, be defensive and generally work in silos failing to grasp the big picture in the role of IT within an enterprise. In order to escalate the value add of IT, it is important for techies to see the big picture, work more collaboratively and understand business and IT alignment.
In this course, we shall touch on the importance of cross-functional roles, the practice of enterprise architecture, the relationship among people, process, technology and data as well as how decisions impacting multiple components within an organization are made. We shall delve into definitions, value and practical applications of such concepts as Enterprise Thinking, Enterprise Architecture, EA Frameworks, Cross-functional Processes, The Four Dimensions and more.
At the end of this course, the student will have a much broader understanding of the role of IT within an organization and develop the frame of mind necessary to grow beyond working in silos to a more holistic view of information technology and how they fit in. All information technology professionals working in the modern workplace need to have a good understanding of the concepts shared in this course.