Project management is an activity which is given special attention, as a guarantee that all projects which are carried out will be done on time and within planned budget, thereby satisfying the most rigorous quality requirements. Project management is performed using the methodology and standards recommended by PMI - Project Management Institute and are contained in the book PMBOK (Project Management Book of Knowledge).


According to the proposed methodology, the project takes place in the following stages :

Initiation Phase

Establishment phase, the initiation of the project (engagement initiation) is the driving phase of the overall relationship with the end user. Within this phase, the focus is on establishing the basic guidelines before launching the project, ie, the connection between the service provider's existing resources and scope of the project end-user. In this step, ending the phase of the project options (opportunity) and begins with the preparation of actual involvement in the project.

Although the user manager (account manager, which is different from the project manager) is responsible for establishing the project, this is also an opportunity to establish a relationship between the whole, sometimes virtual, team. This includes sales, service, marketing with the bidders with the same groups with the end user.

What is the establishment of the project according to PMBOK methodology?

Setting up the project, according to the PMBOK methodology consists of processes that enable the formal authorization and start of the project or if it is a project where the project phases observed throughout the process, each phase of the project. Initiation is often done even before the project actually starts, and the great role played by the project sponsor or the external resource for project preparation.


Planning Phase

The planning phase is the phase where most of the planning of the project ends. During this phase, the project team prepares the functional specification, through the design process and the preparation of work plans, cost estimates and schedule a variety of project delivery and control points.

Design process gives the team a systematic way from the abstract concepts that exist in the establishment phase of the project (initiation) to make assignments of specific technical details of the tasks - provided that it is possible to monitor the transition between user requirements and product features.

The result of this design process is documented in the functional specification. The functional specification describes in detail how it will look like and how it will work individually possibility final solution. Also, the specification describes the architecture and design of all product features (features). The functional specification has multiple purposes, such as instructions for developers to build the program, the basis for the evaluation of the work you need to do an informal agreement with the customer about what exactly needs to build the synchronization point for the entire project team.

Once the functional specifications set, part of the detailed planning starts. Every single team is preparing plans for project delivery that fit their roles in the project and participate in meetings at which planning is done. As a group, the team for review ("review") and establishes the interdependence between the individual plans. All plans are synchronized and used together as the main project plan ("Master Project Plan"), which should not be confused with Microsoft Project project file (. mpp files). The number and types of individual project plans which will be included in the main project plan depends on the extent and type of project.

Team members representing each roll in the project produce estimates of total project time and time schedules when they made ​​the delivery of the project. Different time of delivery are synchronized and incorporated into the main project plan.

At the end of the planning phase, users and project team members must agree to the details which will be delivered and when. A single control point of the project team has reviewed the risks of the project, changing the priorities of the project and concludes estimate of the time and resources.

Executing Phase

Execution phase of the project consists of project tasks and actions that need to be performed during the time the project lifecycle. For example, reporting on project status, managing customer satisfaction, etc. are just some of the repetitive tasks that must be performed during the execution of the project.

Execution phase, is also a control point in the project life cycle, when all the project plans integrate. In complex projects, the elements of a vision are transform to elements of execution, and then executed until the execution phase is complete. In conventional projects, sometimes performed only segment: for example, carrying out security reviews as part of a phase of stabilization.

In most of the methodology, the execution of the project relates 80% - 90% of the total effect (effort) of the project. However, this does not mean that it takes the same percent of the total duration of the project. Simply, in the execution phase, all should be more or less known, and all that is left is the famous "execution", ie construction projects under the terms of reference. Within the execution phase of the project are carried out the project processes - establishing a vision, project planning, project work and its setting in a production organization. Phase of project implementation ends when all the tasks that are set before the project finished.

Monitoring and Control Phase

It includes all activities that ensure that the project manager at any time 'knows' where the project is located, what activities and action have been completed, to monitor the allocation of resources in the project and in the case of discrepancies or problems arise can react.

Closing Phase

Closing phase of the project is a chance that the project is completed in a structured manner, and thus close the project by the end user. However, it is important to know that project for the end user can continue and, as such, may depend on the successful delivery of project deliverables that are created during the execution phases of the project. It is also very important to ensure that the basic customer expectations are realized, which are set in terms of customer satisfaction (Satisfaction of Conditions), and that neither one important question remained open. Finally, it is an opportunity to re-establish the business value of your services and the possible existence of opportunities for additional services and solutions that could offer the end user.

As with the establishment of the project, the project manager is responsible for closing the project, but this is an opportunity to meet the entire team responsible for the project, including all executive sponsors and project technical team.

INFONET d.o.o., Mehmedalije Maka Dizdara 26, 75000 Tuzla, BA
phone.: + 387 35 306 550_, fax.: + 387 35 306 551