Frequently Asked Questions - General

Define priorities of your project and PM2BP will generate the specific planning process for it. The most critical parameters will be planned first and then less important ones on the basis of its. Herewith the logical sequence of the planning process will be met i.e. every input of planning subtasks would be defined in the previous steps. (The inputs of the subtasks can be viewed by choosing “Detailed” option.)

To get the access please log in or sign up.

 

Key project parameters could have constraints besides priorities against each other. These constraints should be taken into account during the planning process. Prescriptive milestones are an example of such constraints:

In present version it is supposed that every project parameter could be limited.  For this reason with setting priorities the user defines the importance, i.e. “rigidity” of applied constraints.

These two terms will be separated in upcoming versions.

Abstract resources (or types of recourses) are nonfinancial recourses that are not associated to real appointments yet. I.e. “business analyst” is an abstract resource, but business analyst John Black is personalized “resource”.

Abstract resources are used if the project has no resource constraints (besides financial ones maybe) or level of importance of these constrains is lower than another ones (see 1 in the figure)

For the same reason abstract resources have no schedule of availability because it is supposed that the project will be provided with these resources as needed.

Standard performance and cost are defined for abstract resources to be used for project planning.

Later abstract resources will be personalized when the register of resources is forming i.e. they get its names (see 2 in the figure). Standard performance and cost should be met when selecting candidates.

 Note: if there is defined resource pool in company these resources are not abstract and each resource has its availability schedule.

The result could be unpredictable in this case. In fact, the system will determine the priorities by itself:

PMBoK proposes unified planning process regardless of project priorities. On the contrary, PM2BP forms different planning processes taking into account your priorities.

The planning of risks, quality and other project aspects will to be realized in further versions of PM2BP.

Another inputs of subprocesses are not displayed (but implied) in current version (for example: archive data or expert judgments).

Main chapters of project charter are developed as part of “Setting of goals and objectives of the project” and “Defining of breakdown structure and list of results and indicators of the project”.

These functions are to be realized in further versions. 

The subscription will be launched soon. Еmail us and we will include you in the first newsletter.