Companies and other organizations have to change and adapt their strategies and redefine their goals constantly. Actions and steps that are needed in order to achieve the defined goals and to realize the change are often executed in a form of a project. There is no doubt that projects need to be managed in an appropriate way. In organizations where there are more than one project executed in parallel and other projects are being planned or proposed at the same time it is necessary to manage not only the individual projects but the entire portfolio of projects and programmes. Portfolio management is needed to ensure that the selected projects are best aligned with the defined goals and the strategy but this requires an analysis of a large amount of data about current and upcoming projects or about available resources and their utilization. It is not always easy to get all required data and to perform the analysis. This is the reason why deployment of some project and portfolio management software tool should be considered. This thesis deals with a search for suitable open source project and portfolio management tools and with assessment of costs and benefits of deployment of selected open source tool in a hypothetical IT company. The goal of this thesis is to define the term project and portfolio management tool and to find at least five open source tools of this type that are suitable for deployment in an organization. At least one of these tools should be suitable for deployment in the IT company. Another goal is comparison of features and functionality provided by the open source tools with functionality provided by the robust proprietary project and portfolio management solution deployed on premise and with one solution offered in the Software-as-a-Service model. Creation of a business case dealing with implementation of the selected open source tool is the last goal of this thesis. Identification and description of available open source tools and comparison of these tools with representatives of the robust project and portfolio management tools developed and distributed in models different from open source are considered the main benefits of this thesis. The terms "open source software" and "project and portfolio management tool" are defined in the first part of this work. The definition of terms is followed by the definition of the overall approach to the assessment of the open source tools which involves definition of assessment criteria and obligatory requirements. Next part of the work is dedicated to the selection of the open source tools that are suitable for deployment in an organization and which represent candidates for project and portfolio management tools. Assessment of these tools using the defined criteria is performed as the next step which is followed by the comparison with representatives of proprietary project and portfolio management tools. Last part of the work is dedicated to the business case which deals with deployment of the selected open source tool. This work concludes with discussion whether the defined goals were met or not, and with the summary of the results.

Weitgehend unbeobachtet von der Disziplin Wissensmanagement haben sich seit vielen Jahren Open Source Softwareentwickler erfolgreich im Wissensaustausch geübt. Ohne direkten Auftrag- oder Geldgeber arbeiten sie über lange Zeiträume und häufig sehr erfolgreich als virtuelles Team zusammen. Die dabei wirksamen Mechanismen sind von Unternehmen bislang wenig untersucht oder beachtet worden. Können sie davon profitieren, indem sie die Motivationsgrundlage von Open Source Projekten auf sich „übertragen“?

Weitgehend unbeobachtet von der Disziplin Wissensmanagement haben sich seit vielen Jahren Open Source Softwareentwickler erfolgreich im Wissensaustausch geübt. Ohne direkten Auftrag- oder Geldgeber arbeiten sie über lange Zeiträume und häufig sehr erfolgreich als virtuelles Team zusammen. Die dabei wirksamen Mechanismen sind von Unternehmen bislang wenig untersucht oder beachtet worden. Können sie davon profitieren, indem sie die Motivationsgrundlage von Open Source Projekten auf sich „übertragen“?