Lecture

Organizational Culture and Change

Graph Chat

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.

In course

CS-491: Introduction to IT consulting

This course is an introduction to the alignment of enterprise needs with the possibilities offered by Information Technology (IT). Using a simulated business case, we explore how to define the requirements for an IT service that matches stakeholders explic ...

Description

This lecture discusses the importance of organizational culture in maintaining identity and managing change. It covers topics such as the impact of motivation on requirements, the guaranteed requirements engineering process, and the role of culture in organizational behavior. Key points include the significance of maintaining constancy in a changing environment, the creation of norms to counter change, and the relationship between culture and change management.

This video is available exclusively on Mediaspace for a restricted audience. Please log in to MediaSpace to access it if you have the necessary permissions.

Watch on Mediaspace

Instructor

Gil Regev

Gil Regev joined EPFL in 1997 as Senior Researcher after 9 years at Logitech Switzerland and USA. Gil obtained his Ph.D. in Communication Systems in 2003. Since 2008 Gil works both at EPFL and Itecor

Official source

Ontological neighbourhood

Systems science and engineering

Systems thinking: Systems engineering

Related concepts (32)

Requirements engineering

Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term requirements engineering was probably in 1964 in the conference paper "Maintenance, Maintainability, and System Requirements Engineering", but it did not come into general use until the late 1990s with the publication of an IEEE Computer Society tutorial in March 1997 and the establishment of a conference series on requirements engineering that has evolved into the International Requirements Engineering Conference.

Requirements analysis

In systems engineering and software engineering, requirements analysis focuses on the tasks that determine the needs or conditions to meet the new or altered product or project, taking account of the possibly conflicting requirements of the various stakeholders, analyzing, documenting, validating and managing software or system requirements. Requirements analysis is critical to the success or failure of a systems or software project.cite book |editor1= Alain Abran |editor2=James W.

Requirement

In product development and process optimization, a requirement is a singular documented physical or functional need that a particular design, product or process aims to satisfy. It is commonly used in a formal sense in engineering design, including for example in systems engineering, software engineering, or enterprise engineering. It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.

Organizational culture

Historically there have been differences among investigators regarding the definition of organizational culture. Edgar Schein, a leading researcher in this field, defined "organizational culture" as comprising a number of features, including a shared "pattern of basic assumptions" which group members have acquired over time as they learn to successfully cope with internal and external organizationally relevant problems. Elliott Jaques first introduced the concept of culture in the organizational context in his 1951 book The Changing Culture of a Factory.

Organizational behavior

Organizational behavior or organisational behaviour (see spelling differences) is the: "study of human behavior in organizational settings, the interface between human behavior and the organization, and the organization itself". Organizational behavioral research can be categorized in at least three ways: individuals in organizations (micro-level) work groups (meso-level) how organizations behave (macro-level) Chester Barnard recognized that individuals behave differently when acting in their organizational role than when acting separately from the organization.

Related lectures (64)

An Introduction to Systems Engineering: Requirements, Architecture, and Concept Generation

Covers the 'V-Model' of Systems Engineering, emphasizing good requirements, system architecture, concept generation, and concept selection.

Requirements Definition

Explores the fundamentals of requirements definition in systems engineering, emphasizing the importance of clear and concise requirements for successful system design.

Design Review Process: Principles and Examples

Explores the principles and examples of the design review process, emphasizing documentation, risk analysis, and verification.

Systems Engineering: Introduction and Stakeholders

Introduces Systems Engineering, emphasizing stakeholder analysis and clear requirement definition for project success.

Scenarios and Requirements