Advertise on podcast: 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 focuses on the formative role of contractual agreements in project success. Gerhard Friedrich, an expert in IT governance, points out that contracts set crucial course for all aspects of project work. In particular, they have a positive or negative influence on the mindset, an effect that is often overlooked.

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 importance of clearly distinguishing between objectives, constraints, and actions in complex situations, particularly in projects. Objectives define the problems to be solved, while actions represent possible solutions. Constraints are unchangeable circumstances that affect the effectiveness of actions. Gerhard Friedrich, a program and project management expert, emphasizes that mixing up objectives and actions can lead to actions becoming an end in themselves. A clear understanding of this distinction is crucial to being successful in projects by quickly recognizing what can be done to make the project a success. It also shows that often even constraints that are considered immutable can be changed by appropriate measures.

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.

This podcast presents Disciplined Agile (DA) as an integrative approach to project management. DA emphasizes that context, choice, and workflow optimization are crucial to making projects successful. In contrast to rigid agile frameworks like SAFe, DA encourages adapting the “way of work” (WoW) to specific project requirements. DA positions itself as a collection of good ideas from various agile and traditional methods, such as Scrum, Kanban and the waterfall model. A core aspect of DA is the consideration of contextual factors and the flexible selection of procedures for individual tasks. DA supports companies in continuously developing their agile practices.

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.

Conflict and failure are often seen as project killers—but what if they were actually the key to success? In this episode, we explore how project managers can harness friction to drive creativity and innovation. 🔹 The Power of Conflict: Learn how goal and method conflicts can lead to breakthroughs rather than breakdowns. 🔹 The Truth About Failure: Why acknowledging mistakes early can save your project—and why avoiding blame is crucial. 🔹 Lessons from the Field: How a strong error culture and open communication lead to better decisions and stronger teams. Join us as we challenge conventional wisdom and uncover the surprising ways that tension and setbacks can fuel project success.

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.

In this podcast we explore the key elements of effective leadership and team dynamics. This episode will delve into four core leadership tasks, that means what a leader has to do. We will also examine three distinct leadership styles, that's about how a leader should do his job. This podcast is designed to assist you as a project manager in analyzing and improving your leadership style to become more effective and inspiring. We'll show you how to support your team members, resolve conflicts, and create a positive work environment. Together, let's unlock your leadership potential.

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.

This podcast discusses the challenges of process analysis in the context of IT projects. Effective process optimization requires close collaboration between business and IT, where premature detailing of target processes is often inefficient. Instead, Gerhard Friedrich advocates an iterative spiral model that enables flexible adjustments and keeps the dialog between users and the IT department permanently in focus. Standard software is favored over custom development, and agile methods should include appropriate preparation phases. Finally, the importance of open exchange and joint solution finding is emphasized. Here is the original blog post (in German): https://it-governance.blog/prozessanalysen-helfen-nuetzen-aber-nichts/

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.