IT Governance - Make IT a success factor!

This podcast episode synthesizes the core principles for managing projects in turbulent environments, as outlined by Dr. Gerhard Friedrich. The central argument is a rejection of traditional, prediction-focused project management in favor of a systemic approach that prioritizes adaptability, simplicity, and a holistic view of projects as socio-technical systems. In turbulent times, success hinges not on creating complex plans to mirror complex environments, but on building resilient systems capable of rapid adaptation. Key strategies include minimizing Decision Latency, as speed is more critical than perfection, and focusing on a Minimum Scope. The briefing challenges the practical application of Ashby’s Law of Requisite Variety, presenting empirical evidence that simple heuristics often outperform complex models in uncertain conditions. To thrive, organizations should be restructured as Fractal Organizations—decentralized, autonomous, and self-similar units—drawing lessons from the robust governance of firefighters. Leadership is redefined as a distributed process, not a role, with an emphasis on fostering peer leadership and social support to create psychological safety and empower teams. Ultimately, project success requires the joint optimization of both social (people, culture) and technical (processes, tools) dimensions, as one cannot compensate for the failures of the other.

This podcast shows that careful preparation is essential for agile IT projects as well. Gerhard Friedrich criticizes the fact that frameworks like Scrum often neglect the early project phases and presents DSDM (Dynamic System Development Method) as a more comprehensive approach. DSDM covers the entire project life cycle, from the feasibility study to project completion, and integrates iterative development methods. The article highlights the pre-project and planning phases, emphasizing the importance of goals, architecture and resource planning. Friedrich suggests that combining different frameworks such as DSDM and PMI (Project Management Institute) can increase project success.

This podcast discusses the necessity of commitments and responsibilities in agile software development projects. The podcast is based on a blog post by Gerhard Friedrich. He emphasizes that users and IT teams must have clear ideas about their respective tasks and contributions, especially in terms of strategic, economic and organizational frameworks. He argues that flexibility and agility do not mean being superficial or noncommittal, but on the contrary, require structured collaboration and professional project management. A well-thought-out IT architecture is essential to avoid a chaotic “mess” of isolated solutions. Ultimately, Friedrich underscores the importance of discipline and stable structures for the success of agile projects.

Unrealistic project plans often arise not out of ignorance, but to avoid unpleasant discussions with stakeholders. This happens because it can be difficult to enforce realistic timelines and budgets, or because unrealistic goals are necessary for project approval. How should one deal with this? This is discussed in this podcast, along with some very practical tips for use.

This podcast is about the tasks and responsibilities of business and IT in agile projects. It explains why Scrum can only cover some of the requirements to be met and is not always the best approach to a project. The DSDM model is recommended as a comprehensive approach that includes phases such as feasibility study and foundation planning before implementation starts, e.g. with Scrum. The paper argues for a methodical eclecticism that combines Scrum with other approaches such as Lean or XP. The key success factor is a holistic view of the project that goes beyond pure software development.

This podcast is an excerpt from a book about IT law and mindset in project management. It deals with the importance of contracts for the success of IT projects. It shows how contracts shape project work and that contracts that do not fit agile projects endanger their success. It is shown why fixed-price contracts are dangerous and how contracts should be designed to promote project success.

What can we learn from TOC and EKS This podcast describes different approaches to bottleneck orientation in project management. Central to this is identifying and eliminating bottlenecks – both external (customer needs) and internal (resources, processes) – in order to maximize project success. The Theory of Constraints (TOC) with its cyclic approach and the Bottleneck-Concentrated Strategy (EKS) are presented, whereby the EKS offers a broader strategic framework while the TOC provides concrete tools for increasing productivity. The author, Gerhard Friedrich, emphasizes the importance of stakeholder management and prioritizing measures to achieve the greatest benefit in each case. Finally, TOC and EKS are not presented as opposing approaches, but as complementary ones, with EKS serving as an overarching guide

This podcast emphasizes the importance of Test Driven Development (TDD), in particular the early formulation of test cases, in order to avoid misunderstandings and mistakes in software development. It argues that tests should not only be applied to finished software, but to all intermediate results, such as project plans or requirements descriptions. An example from the insurance industry illustrates how user stories can be specified with test cases to describe requirements in detail and validate them early. Identifying errors early saves time and effort.

The role of IT has to change signifcantly to master today's challenges This podcast deals with the changing role of IT in the age of digitalization. It criticizes the traditional view that regards IT as a pure service provider that carries out instructions from specialist departments. Instead, it argues that IT must be an equal partner in the development of business models and processes. The text calls for close cooperation and dialogue between IT and specialist departments in order to successfully meet the challenges of digitalization.

This podcast discusses the use of user stories in agile project management and analyzes their strengths and weaknesses. Gerhard Friedrich argues that user stories are a good starting point for requirements definition, but should not serve as the sole form of requirements definition. He advocates taking into account various perspectives (user, business, task, implementation, environment) when analyzing requirements and points out the limitations of INVEST criteria.

This podcast examines the challenges that arise from using traditional contract models in complex IT projects. Classic contracts, which focus on fixed services and prices, hamper successful collaboration and lead to inflexible and confrontational working relationships. The author argues in favor of relational contracts that are based on mutual trust and flexible adaptation to changing project conditions. Agility is identified as a crucial success factor for modern IT projects, with a focus on the ability to cooperate and mutual appreciation.