IT Project Management

from idea to software product

From idea to the desired result: In order to realise what is useful and important, in practice it requires a framework with clearly defined fixed points and a matching process model that combines these cornerstones. Flexibility between the fixed points on the one hand and consistent clarity on the goal to be achieved on the other hand are fundamental pillars upon which the successful conclusion of a project is based. This is accompanied by implementation of a functioning software product or service that corresponds with the needs as per a conventional or agile project approach.

Why it isn't always easy

It isn't hard to find examples of projects which are outside the agreed time frame, over budget, under the quality requirements, or that have in fact failed. What are the reasons for this? Why do these project results arise again and again, despite the most outstanding skills of those involved?

The causes are complex and often occur in combination. Here are some examples:

• Implementing a project always represents a unique and often a new undertaking. In contrast to the standardized production of an article, for example, to a degree you are operating in unknown terrain.
• Goals which have not been specifically agreed upon between the parties cannot be carried out, expectations cannot be served. Much more important: a clear, common understanding of a goal.
• Social factors and the work environment affect work results to a much greater degree than you might imagine.
• Things that have not been taken into account during planning or were wrongly assessed, at a later stage have the potential of becoming irreversible negative factors.
• Quality issues, which are often first detected by the customer due to an insufficient quality assurance process.

Why professional expertise is worthwhile

• Via discussions, visualizations, and prototyping, my experience helps you to identify solutions that can be put into practice, thus closing the gap between desire and realisation.
• Influencing factors, such as identifying stakeholders together, and giving due consideration from the outset
• Thoroughly going over the process in a structured way, especially in the initial and planning phases, substantiating each section with appropriate documentation in German or English
• Selecting appropriate methods of implementation, which can actually be realised in their organization
• Leading a project team or assuming the role of project owners with an agile approach
• Carrying out reporting, which in addition to the standard for your organization, also contains concise information appropriate to the size of the project, the number of participants, and its duration