{"id":7284,"date":"2025-09-25T08:00:00","date_gmt":"2025-09-25T06:00:00","guid":{"rendered":"https:\/\/www.se-trends.de\/?p=7284"},"modified":"2025-09-25T14:49:11","modified_gmt":"2025-09-25T12:49:11","slug":"modern-re-keynote-prof-wagenpfeil","status":"publish","type":"post","link":"https:\/\/www.se-trends.de\/en\/modern-re-keynote-prof-wagenpfeil\/","title":{"rendered":"Modern RE keynote: Requirements specification or project grave? Lessons learned from the perspective of an IT expert"},"content":{"rendered":"

Register quickly<\/a><\/strong>: Today at 16:00, free webinar with Michael on interfaces with SysML and Rhapsody.<\/p>\n\n\n\n

We can learn a lot from failure. Experts are the ones who look at the shambles and analyze why projects go off the rails. Few will be surprised that the problems almost always arise at the beginning, before the actual work begins.<\/p>\n\n\n\n

The keynote speech \"Requirements specification or project grave?\" at Modern RE was given by Prof. Dr.-Ing. As an IT expert, he regularly analyzes failed projects and shows how to recognize early on whether a project is viable or not. A perfect topic for a keynote speech at a conference on requirements management.<\/p>\n\n\n\n\n\n\n\n

\n

As IT experts, we ensure that we act as a neutral authority in court proceedings and disputes regarding the quality assessment of software products.\"<\/p>\nProf. Dr.-Ing. Stefan Wagenpfeil<\/a><\/cite><\/blockquote>\n\n\n\n

Modern RE 2025<\/h2>\n\n\n\n

The This year's Modern RE<\/a> took place from September 17-18, 2025 in Leibzig. The conference was well attended with around 130 participants and covered a wide range of content in various formats, from lectures to workshops. On the following day, I had the pleasure of second keynote on Product Velocity<\/a> hold.<\/p>\n\n\n\n

Why planning is so difficult<\/h2>\n\n\n\n

The theory sounds simple: Write clear requirements<\/a>then implement it. But practice is complicated. Requirements are often unclear, contradictory and incomplete. What's more, they often change during the course of the project. But even carefully written requirements are rarely as clear as the client would have expected. Here is an example from the keynote speech that illustrates how difficult planning can be.<\/p>\n\n\n\n

\n

A company put an SAP project out to tender with over 1000 pages of detailed requirements. The bidders' offers ranged between 13 and 43 million euros - a deviation of 300 percent. Despite the great effort put into the preparation, there was no comparability. <\/p>\n<\/blockquote>\n\n\n\n

\n
\n
\n
Review: INCOSE guide for writing requirements<\/a><\/blockquote>