The paper describes the principle of the public-private partnership as a mechanism for implementing infrastructure projects in cities as well as the forms of organization and financing options for such projects. The basic concepts of the public-private partnership are analyzed. The experience of implementing the public-private partnership in the framework of the project for the construction of the Moscow-Saint Petersburg interstate route is presented. The bottlenecks of the current practice of the public-private partnership were revealed. The purpose of this paper is to propose recommendations for improving the effectiveness of public-private partnership as a form of government-business relations in the Leningrad region based on an analysis of the model of public-private partnership in the region.

The agile project management approach has been considered to be one of the most popular approaches for developing IT solutions. Use of this approach allows us to change the requirements at any stage of the IT project, and one of the twelve principles of Agile Manifesto, -"Simplicity", -promotes the use of a minimum amount of project documentation. One of the disadvantages limiting the implementation in such resource-intensive projects as Information Systems Projects (ISP) is the risk of exceeding budgets and time limits. Therefore it is highly important to develop such a tool that will contribute in discussion and approval process with the customer before changes are started so as to minimize the possibilities of changes at further stages of the project. This article investigates the possibility of applying holistic methods of the Enterprise Architecture (EA) in order to support solutions design during an Information System Project, in particular, in the form of documentation at the stage before implementation planning. The main aim of our research is to develop a tool that will help the customer to understand the planned changes and will contribute in that their infl uence on the already existing EA is taken into account. This article fi rst reviews standards of IT project management in the context of recommendations for "conceptual project" outcomes. Next, the results of interviews conducted with IT consultants are presented. The proposed Architectural Solution (AS) is a document that completes the stage of design and coordinating IT changes. It is based on the application of methods and models from the fi eld of EA. We believe this solution may be a suffi cient document for coordinating projects that are conducted under agile philosophy.

The agile project management approach has been considered to be one of the most popular approaches for developing IT solutions. Use of this approach allows us to change the requirements at any stage of the IT project, and one of the twelve principles of Agile Manifesto,-"Simplicity",-promotes the use of a minimum amount of project documentation. One of the disadvantages limiting the implementation in such resource-intensive projects as Information Systems Projects (ISP) is the risk of exceeding budgets and time limits. Therefore it is highly important to develop such a tool that will contribute in discussion and approval process with the customer before changes are started so as to minimize the possibilities of changes at further stages of the project. This article investigates the possibility of applying holistic methods of the Enterprise Architecture (EA) in order to support solutions design during an Information System Project, in particular, in the form of documentation at the stage before implementation planning. The main aim of our research is to develop a tool that will help the customer to understand the planned changes and will contribute in that their infl uence on the already existing EA is taken into account. This article fi rst reviews standards of IT project management in the context of recommendations for "conceptual project" outcomes. Next, the results of interviews conducted with IT consultants are presented. The proposed Architectural Solution (AS) is a document that completes the stage of design and coordinating IT changes. It is based on the application of methods and models from the fi eld of EA. We believe this solution may be a suffi cient document for coordinating projects that are conducted under agile philosophy.