All episodes

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.

This podcast discusses the global shortage of software developers and presents Citizen Development as a possible solution. Citizen development, the development of applications by business users using low-code/no-code platforms, is presented as a paradigm shift that can improve collaboration between business and IT. Gerhard Friedrich emphasizes the importance of governance and an agile corporate culture for the success of citizen development and warns of the risks of "shadow IT". Success factors lie in the cooperation between business users and IT as well as the right choice of implementation model. Gerhard Friedrich illustrates this using a case study with a business...

This podcast discusses Ashby's Law of Requisite Variety and argues that it is misinterpreted in practice, especially in project management. Gerhard Friedrich points out that the law only applies within a common set of rules. It is a mistake to conclude from this that complex projects must be managed with complex organizational forms. Instead, he argues for the use of agile methods, which are characterized by simplicity and efficiency, to manage complexity. Gerhard Friedrich illustrates his point using examples from project management and game theory.

This podcast deals with the question of how to deal with mistakes and problems in projects. Gerhard Friedrich criticizes the widespread practice of obscuring mistakes or referring to them as “challenges” and argues that mistakes should be addressed openly and learned from. He argues that in projects there is very often a clear “right” and “wrong”. While avoiding blame is important, mistakes must be recognized as such and analyzed. It is important to learn from mistakes and improve processes instead of glossing over them just to avoid hurting anyone's feelings.

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 compares the strategic approach of Luis de la Fuente, coach of the Spanish national team, with IT governance in companies. De la Fuente relied on an offensive playing style, team spirit, flexibility and creativity, which led to winning the Nations League. Gerhard Friedrich argues that IT departments would also benefit from an offensive strategy instead of relying on defensive measures. He advocates a proactive approach to requirements, teamwork, flexibility and creativity in IT development. The recipe for success lies in execution and a willingness to implement changes, even when setbacks occur.

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.