You get a bonus - 1 coin for daily activity. Now you have 1 coin

11. Planning project labor resources

Lecture



Human resources planning is the process of defining and documenting roles, responsibilities and accountability, and creating a personnel management plan for a project [16].

11.1. Defining project roles

When assigning the roles and responsibilities necessary to complete a project, the following points should be considered.

Role in the project (project role) - a specific set of functions and powers in the project, created to distribute responsibilities among the project team members. The project role can be considered as a temporary position in the organization (company).

Powers - the right to use project resources, make decisions and approve actions or results approval. Examples of authority: the choice of the method of completion of the operation, the quality acceptance and the procedure for responding to deviations in the project.

Responsibility - the work that a member of the project team must perform to complete project operations.

Qualifications - the skills and abilities necessary to carry out project operations. The lack of the necessary qualifications of the team members affects the project schedule, the quality of the performance of work, threatens the project objectives. To improve the qualifications plan to conduct training of team members.

Forming a project management team, it is necessary to identify key project decision makers.

On the client side, the project sponsor and the project manager on the client side play key roles. The project sponsor provides the organizational side of the project and confirms the correctness of the project objectives. He is in charge of the project budget. The project may be sponsored by an individual or a whole committee, depending on the scope and complexity of the project. The project manager on the part of the customer is appointed even if the implementation of the project by the customer’s organization requires daily management. His responsibilities include providing customer resources, solving problems, and tracking project status.

Key roles on the part of the contractor are the project manager (project manager) on the part of the contractor and the business manager.

The business manager is responsible for the successful execution of the project and represents the contractor in his contractual relationship with the customer. The project manager (project manager) is responsible for both the successes and failures of the project. Its task is to manage the timing, cost, quality of work in order to meet customer expectations and achieve the contractor’s business goals.

The project management team includes a project coordinator, project administrator, and configuration manager. For large projects, several people may be involved in each of these roles. On small projects, the project manager can combine several roles. Large-scale projects require a quality manager who is responsible to the business manager of the contractor.

In large projects, a management committee, a change control committee, a controversial analysis committee can be organized [8].

The following list of key roles of the project management team is necessary to manage the work during the implementation of the information system. Some modifications of the team are possible depending on the complexity and scale of the project, for example, if necessary, you can include a deputy project manager, managers of functional areas (finance, logistics, personnel, etc.).

The composition of the management team should be sufficient to implement [11]:

  • project resource management, including:

o determination of the resources required to achieve the objectives of the project;

o preparation of proposals for changing the composition of the project management team;

o approval of personal changes in the composition of the project working groups;

o project cost estimation, preparation of project budgets and budget execution reports;

  • management of the project timeframe, including:

o preparation of the project work plan;

o control over the implementation of the project;

o preparation of project progress reports;

  • project quality management, including:

o control of the compliance of the developed design solutions with the technical task;

o organization of the expertise of design solutions;

  • project risk management, including:

o project risk analysis;

o developing risk mitigation plans;

o implementation of risk reduction measures;

  • problem management of the project, including:

o analysis of project problems;

o development of measures to resolve project problems;

o implementation of measures to resolve project problems;

  • control over the organization of work in project groups, including:

o approval of progress reports;

o control over the functioning of the system for collecting and distributing information;

o control of documenting project results.

The project team includes not only the project management team, but also the project executives. Examples of project roles that are specific to IT projects: functional architect, functional consultant, developer, IP administrator, tester, quality manager, system analyst. In the project, one member of the team can act simultaneously in several roles. The combination of roles is often found in small projects, which reduces project overhead. But not all roles can be combined, since such a combination may make it difficult to monitor and evaluate project results. It is allowed to combine such project roles as project manager and project administrator, functional architect and functional consultant, functional consultant and analyst, development manager and developer, quality manager and tester. But one should not combine the roles of a quality manager and a developer, a project manager and a developer, a tester and a developer.

At the planning stage as part of the human resource management process, no long-term planning is envisaged, but a plan is drawn up for the implementation of the first phase of the project. The main tasks are the development of the organizational structure of the project and the selection of personnel.

The organizational planning work is carried out by the project manager on the part of the executor together with the manager on the part of the customer. By negotiation, agreement is reached on the level at which approval of the customer’s allocated resources should be made and discussion of the requirements for the members of the contractor’s team. The project administrator records the results of the negotiations.

Hierarchical organization charts are a simple and clear tool for determining the hierarchy of accountability, starting from the bottom level of the organization to the project manager.

  11. Planning project labor resources


Fig. 11.1. An example of the organizational structure of the project

There are various formats for documenting the distribution of roles and responsibilities of project team members, for example, hierarchical, matrix, or textual. Regardless of the format of documentation, organization charts allow assigning a person responsible for its execution for each work package, and also ensure that each member of the team understands his or her role and responsibility.

In fig. 11.1 presents an example of the organizational structure of the project, documenting the distribution of roles and responsibilities of members of the project team, made in the form of an organizational structure. The organizational structure is a hierarchical organizational chart of the existing divisions of the organization (departments, groups or teams). Under each department there is a list of project operations or a work package. Thus, you can see the consolidation of responsibility in a project for a given functional department (for example, an information technology department or a procurement department) in one place next to the department name.

11.2. Project Responsibility Matrix

To reflect the hierarchy of accountability on the project and indicate the responsibilities of each of the groups included in the project team, it is recommended to include a responsibility matrix in the project description document, the most common variant of which is known as the RACI matrix. The use of this tool is especially relevant in a situation where the project team consists of representatives of various legal entities (for example, a typical team on an implementation of an integrated computer system includes employees of the customer, general contractor and subcontractors). Responsibility matrix solves the problem of demonstrating inter-organizational or inter-group interaction and, as a result, avoids misunderstandings that occasionally arise in projects between departments and organizations due to ambiguities who should be approached on certain issues and who should decide on them and who - directly implement the adopted resolution.

It is important to make the delimitation of all formal powers, rights and obligations as early as possible, while the project team has not yet begun active work. Otherwise, when employees develop their own ideas about their place in the project, differences of opinion on these issues may develop into protracted conflicts and have a significant negative impact on the project implementation schedule.

Building a responsibility matrix

1. List the main work of the project.

Vertically, the matrix reflects only the main work of the project (not lower than level 2-3 of the SRI ), but with a sufficient degree of detail to ensure that it is possible to indicate the different roles needed to perform these works. When it comes to large projects and programs, it may be necessary to develop several responsibility matrices with varying degrees of detail.

2. List the groups / roles within the project team.

Horizontally in the matrix are listed groups / roles within the project team. Note that in the responsibility matrix of the group / role, and not the names and surnames of individual team members. Personal consolidation of design work is done later, at the stage of developing the project schedule .

3. Encode the responsibility matrix .

Using the codes in the cells at the intersection of the corresponding columns with roles and the lines with the project’s works, indicate the degree of participation, formal authority, and distribution of responsibility for performing each operation. A clear indication of the different levels of formal authority is especially useful in situations where many members of the project team wish to make special demands on the project.

Table 11.1. Legend of Responsibility Matrix (RACI)

Designation

Decryption

Description

Use (R)

Performer (Responsible)

Responsible for the immediate execution of the task. At least one performer must be assigned to each task.

Approved (A)

Accountable

Responsible for the final result before the higher management. Each job must be assigned strictly one accountable

According to (C)

Consulted

Coordinates decisions, interaction with it is bilateral

N. (I)

Observer (Informed)

He is informed about the decision already taken, interaction with him is one-sided.

Table 11.2. Distribution of functional responsibilities of the project management team

Functional responsibilities

Project Curator (Sponsor)

Project Manager

System architect

Project Administrator

Planning

Development and periodic update of the plan

+

+

Plan approval

+

Project team management

Appointment of an employee to the role of project manager

+

Formation of the project team

+

Determination of qualification requirements and composition of working groups of specialists on IP functionality

+

Ensuring the allocation of the necessary resources to carry out the project

+

Direct management of the project team

+

Formation of proposals to stimulate the project team

+

Providing Incentive Project Team

+

Organization of work

Organization of interaction with the Customer and provision of all necessary communication links with other project participants

+

Organization of preparation, coordination and approval of all technical documentation necessary for the creation of IP in the framework of the project

+

Organization, carrying out and documenting the procedures for transferring the developed IC to the Customer

+

+

Consideration and approval of regulatory documents necessary for the organization and implementation of the project

+

Conducting organizational, administrative and reporting documentation. Keeping up to date the project team list

+

Providing the project team with the necessary information materials

+

Logistical and economic support of the project team

+

Monitoring project progress

Organization and holding of meetings to discuss the progress of the project

+

Preparation and submission of project progress reports to the Curator

+

Receipt and analysis of the consolidated reporting on the project implementation

+

Control of compliance of the project results with the TOR for the development of IP

+

Coordination of actual labor costs of specialists in the execution of the project

+

+

There are no restrictions on the codes used in the liability matrix , but the most widely used method is RACI (Responsible (R), Accountable (A), Consulted (C), Informed (I)), which describes the corresponding codes.

4. Initiate the use of the matrix and include the procedure for using the responsibility matrix in the document “ Project Management Plan ”.

After approval of the responsibility matrix, all further changes in it should go through the procedure of integrated change management with the participation of the authors of the original version.

The advantage of using a structured approach to changing the responsibility matrix is that the project manager receives an up-to-date document to which he can refer in case of any disputable situations concerning the distribution of powers in the project.

In particular, the liability matrix can be used to allocate core functional responsibilities. So, in tab. 6.2 in the left column lists the functional responsibilities of the project work, a list of which is based on the methodology used and the accumulated project experience, and the right part of the table is marked on the degree of responsibility and participation of each member of the project management team in the respective function.

11.3. Securing the functions and powers in the project

Earlier in the section on the formation of the project charter, we briefly described the nature of the roles and the basic job descriptions of the project management team members. In this section, we will examine this aspect in detail and form a more detailed list of functions and authorities for each of the roles mentioned below.

The project curator (sponsor) is the project role of the official responsible for the strategic management of the project implementation. The curator decides on the strategic issues of the project, approves the main changes in the scope of work, deadlines, stages, and project budgets that are beyond the competence of the project manager. As a rule, the project supervisor (sponsor) is the senior manager of the organization.

Main functions:

  • general management of the project implementation;
  • ensuring the allocation of the necessary resources to carry out the project, providing financing for the work
  • consideration and approval of regulatory documents necessary for the organization and implementation of the project;
  • obtaining and analyzing a summary of the progress of the project;
  • managing changes to the basic parameters of the project and solving problems that are beyond the competence of the project manager.

Basic powers :

  • approval of project objectives;
  • approval of the appointment of a project manager;
  • approval of the overall plan and budget of the project;
  • receiving from the project manager a summary report on the progress of its implementation;
  • making fundamental decisions when critical changes occur that affect the time, cost and quality of project results.

Project manager - project role of the official responsible for project management . The project manager is directly responsible for achieving the objectives of the project within the allocated budget, in accordance with the planned project implementation timeframes and with a given level of quality.

Main functions:

  • formation of the project team and project management team;
  • planning, organizing and monitoring the implementation of work to achieve the objectives of the project with the required quality, cost, and in the specified period;
  • distribution of project resources and organization of interaction of the project team in the process of its implementation;
  • organization of interaction with the customer and provision of all necessary communication links with other project participants;
  • accounting of actual expenses of resources for project execution;
  • generation and submission of project reporting to the curator.

Basic powers :

  • assigning tasks to the project team (its individual members) and monitoring their implementation;
  • the requirement from the project team to perform their role functions;
  • confirmation or rejection of reports on the actual costs of the project executors;
  • justification of the need and request of the project supervisor for the allocation of additional resources for the project;
  • appeal to the curator for support if necessary.

The system architect is the project role of the official responsible for the project subject area. The system architect reports directly to the project manager.

The system architect is directly responsible for the development of the information system in accordance with the planned project deadlines and with a given level of quality.

The specialist who is most competent in the information system being implemented is assigned to the role of the system architect. The system architect must know the methodology and technology of building IP, standards and regulatory documents in the field of design and creation of IP, development and execution of technical documentation.

Main functions:

  • determination of the composition, duration and technology of work on the development and implementation of an information system;
  • identification of resources that are necessary for the development and implementation of IP within the framework specified by the project conditions;
  • determination of qualification requirements and the composition of the working groups of specialists in areas of activity, their distribution according to tasks, work organization and verification of results in the process of project implementation;
  • ensuring the integrity of the functional architecture of the information system being implemented;
  • organization of preparation, coordination and approval of all technical documentation necessary for the creation of IP in the framework of the project;
  • planning and coordination of actual labor costs of specialists in the execution of the project;
  • Forming and providing the project manager with necessary reporting
  • analysis of the implementation and intermediate results of the creation of IP;
  • organization, conduct and documentation of the transfer procedures developed by the customer IC.

Basic powers :

  • participation in the scheduling of work on the creation of IP;
  • assigning tasks to project teams and monitoring their implementation;
  • the requirement from the executors of high-quality performance of the assigned tasks and timely information on emerging problems;
  • justification of the need and request the project manager to allocate additional resources to the project.

Project Administrator - the project role of the official responsible for the information support of the project manager, organization and management of the project document flow. The project administrator is functionally assigned to a specific project and reports directly to the project manager.

Main functions:

  • providing the project manager with structured information enabling the control of the project, plans, resources and priorities;
  • meeting minutes;
  • ensuring timely preparation, movement and archiving of project documents.
  • Basic powers :
  • transfer and receipt of project documentation from project participants;
  • контроль соблюдения участниками проекта установленной системы документооборота;
  • требование от конкретных исполнителей по проекту оперативной информации и отчетов о ходе работ по проекту.

Для того чтобы закрепить функции и обязанности по проекту, составляют ролевые инструкции или положение по проектной роли . В ролевой инструкции должно быть определено следующее:

  • какие цели стоят перед сотрудником, назначенным на данную роль;
  • кому подчиняется сотрудник, назначенный на ту или иную роль;
  • каковы его функции, обязанности, полномочия .

Крайне важное замечание, высказываемое многими экспертами, состоит в том, что определение ролей и ответственности в проекте должны производиться с учетом факторов внешней среды предприятия. In tab. 11.3 приведены примеры возможного влияния организационных, технических, межличностных, политических и прочих факторов на процесс планирования команды проекта.

Table 11.3. Влияние факторов внешней среды на планирование команды проекта

Факторы внешней среды

Влияние на определение ролей команды и ответственности

Организационные

Взаимоотношения организаций или отделов, участвующих в проекте, механизмы взаимодействия между ними

Technical

Навыки и специальности, необходимые для выполнения проекта, необходимость обеспечения координации между языками программного обеспечения, наличие специфических сложностей при переходе от одной фазы жизненного цикла к другой

Межличностные

Официальные и неофициальные отношения между потенциальными членами команды проекта, их должностные обязанности. Культурные или языковые различия между членами команды, которые могут оказать влияние на их рабочие взаимоотношения

Политические

Цели и интересы потенциальных членов команды проекта, люди (или группы людей), которые имеют неформальное влияние в областях, представляющих важность для проекта, существование неформальных связей между потенциальными участниками проекта

На этапе планирования для каждой роли должен быть определен список навыков, необходимых членам команды проекта. Для разработки списка рекомендуется использовать реестр навыков - список категорий и компонентов навыков для определенного класса команды исполнителей проекта (см.табл. 11.4).

To provide an analysis of skill sets, the components are grouped into four categories: technical skills, administrative, interpersonal skills, strategic skills. For each skill, rating and ability rating are noted [12]. To assess the rating, it is customary to use a 4-point scale (see Table 11.5).

Table 11.4. The skills register for the project team

Skill categories and components

technical skills

  • Ability to manage the project and its technology
  • Assist in resolving project issues
  • Interaction with technical staff
  • Participation in reaching compromises
  • Understanding Trends
  • Understanding the main objectives of marketing
  • Presence of system analysis skills

Interpersonal and leadership skills

  • Assist in solving problems
  • Building a multi-functional team
  • Target definition
  • Getting top management support
  • Team members motivation
  • Conflict Management

Administrative skills

  • Attraction of unique specialists
  • Effective communication skills
  • The ability to delegate authority
  • Negotiating to Provide Resources
  • Scheduling
  • Understanding of policies and work procedures
  • Collaboration with other project teams

Strategic skills

  • Strategic planning
  • Strategic decision making
  • Ability to work under risk
  • Ability to lead

11.4. Skill registers

Skills inventories should be compiled for each class of personnel, such as, for example, a project manager, a system architect, a quality specialist. The criticality of skills for a project manager is largely determined by the scale of the project and the organizational structure of the project. The greatest authority is vested in the project manager in the project organizational structures, and therefore, the highest demands must be placed on him. The list of skills can be determined based on professional standards in the field of information technology. The distribution of skills depends on the level of administrative responsibility. Rating критичности смещается от "технических" в сторону "административных", а затем в сторону "межличностного общения" и "стратегических навыков" по мере роста административной ответственности. Следует подчеркнуть важность навыков межличностного общения. Команда проекта может многократно снизить количество возникающих проблем и повысить взаимодействие сотрудников, если будет понимать настроение членов команды проекта, предвидеть их действия, внимательно выслушивать и признавать их мнение и решать их проблемы. Для управления командой проекта и работы в проекте такие навыки, как умение сопереживать, оказывать влияние, творческий подход к работе и способность облегчать работу группы, приобретают значение ценных активов. После того как реестр сформирован, он может быть использован с минимальной точной подстройкой к новой проектной ситуации

Пример разработки реестра навыков

Ниже (табл. 11.5, табл. 11.6) выделены категории навыков для консультантов и менеджеров проектов: технические, административные, навыки межличностного общения, стратегические навыки. Для каждого консультанта (как при приеме на работу, так и при зачислении в команду проекта) необходимо проводить оценку навыков по шкале 1-4 ("плохо", "удовлетворительно", "хорошо", "отлично" соответственно)

Стоит подробно остановиться на том, каким образом оценивать технические компетенции консультантов компании. Это наиболее важные навыки, которые необходимо учитывать при планировании сотрудников на проекты.

Table 11.5. Scale of ratings of criticality and abilities

Rating

Criticality

Qualification

one

It doesn’t matter

Lack of skills / weak skills

2

Important

Basic skills

3

Very important

High qualification

four

Critical for project success

Unique qualification

Table 11.6. Skills inventory for team members

Skill categories and components

Criticality

Full name

Technical Skills (Category I)

  • Special knowledge of SAP ERP HCM
  • Assist in solving problems
  • Interaction with technical staff
  • Facilitating compromise
  • Integration of technical, business and human goals
  • System thinking
  • Understanding of technology and trends (trends)
  • Understanding marketing application and product application
  • Rallying the technical team

Very important

Good

Administrative Skills (Category II)

  • Ability to communicate effectively (oral and written)
  • Ability to effectively delegate responsibilities (from senior to junior)
  • Minimization of changes
  • Understanding of policies and work procedures

Important

satisfactorily

Interpersonal and leadership skills (category III) Communication skills

  • Easy to understand the client, he likes
  • Consistent
  • Does not force to commit certain actions.
  • Helps to think and make decisions
  • Do not substitute your solutions client
  • Honesty, ability to admit mistakes
  • Offers arguments, not just ready-made solutions.
  • Optimism, the ability to have a positive impact
  • Sense of humor
  • Possession of a number of persuasion tactics
  • Conflict Resolution
  • Teamwork and cooperation: interaction with other employees and team building
  • Understanding of professional needs

Very important

OK

Strategic Skills (Category IV)

  • Building alliances, coalitions and achieving cooperation
  • Ability to work in conditions of risks and uncertainties
  • Motivating and inspiring others
  • Strategic thinking, planning and decision making
  • Understanding the business environment
  • Foresight

To some extent important

fine

Table 11.7. Roster skills project management team members

Skill categories and components

Criticality

Abilities

Technical Skills (Category I)

  • Knowledge of SAP ERP HCM
  • Assist in solving problems
  • Interaction with technical staff
  • Facilitating compromise
  • Integration of technical, business and human goals
  • Understanding of technology and trends (trends)
  • Understanding marketing application and product application
  • Rallying the technical team

To some extent important

Administrative Skills (Category II)

  • Attraction and retention of high-class workers
  • Ability to communicate effectively (oral and written)
  • Ability to effectively delegate responsibilities
  • Evaluation of resources and negotiation to obtain them
  • Measurement of progress and performance
  • Scheduling Multidisciplinary Operations
  • Understanding of policies and work procedures
  • Work (cooperation) with other organizations

Important

Interpersonal and leadership skills (category III)

  • Encouraging the development of other people's abilities through feedback and guidance
  • Ability to initiate transformations, improve management methods
  • Conflict Resolution
  • Action orientation
  • Assist in group decision making
  • Assist in solving problems
  • Building multifunctional teams
  • Ensuring staff engagement at all levels
  • Forming a perspective point of view
  • The trust
  • Setting clear and clear goals
  • Conflict Management
  • Motivation of people
  • Understanding of professional needs
  • Understanding the organization

Very important

Strategic Skills (Category IV)

  • Building alliances, coalitions and achieving cooperation
  • Ability to work in conditions of risks and uncertainties
  • Motivating and inspiring others
  • Resource Negotiation and Resource Mobilization
  • Strategic thinking, planning and application of solutions
  • Understanding the business environment
  • Foresight

Important

В консалтинговых компаниях, в том числе системных интеграторах, довольно сильно распространена практика разделения консультантов на так называемые грейды, или уровни, в соответствии с их технической компетенцией и возможностями выполнения тех или иных задач 1 Пример четко сформулированных требований к грейдам представлен в сводной табл. 11.8 - в ней приведен пример описания технической компетенции консультанта по внедрению модуля управления человеческими ресурсами в системе SAP .

Таблица 11.8. Реестр технических компетенций

Level 1

Weight

Level 2

Weight

Level 3

Weight

Компоненты НСМ-1

70

Администрирование персонала

12

Бизнес-процессы

2

Инфотипы

one

activity

2

Стажи

2

Отчетность

four

Interfaces

one

Управление временными данными

ten

Бизнес-процессы

one

Charts

0.3

Отсутствие, присутствие

one

Лимиты

1.5

Временные события

one

Оценка времени

1.5

Рабочий стол менеджера

0.5

Планирование смен

0.7

Сдельная оплата труда

2

Отчетность

one

Payroll preparation

21

Business processes

one

Infotypes

one

Calculation of basic types of payments

2

Average calculations

2

Taxes

2

Hold

3

Non-cyclical calculations

3

Transfers

one

Posting

3

Reporting

3

Organizational Management

five

Business processes

0.5

Standard objects, infotypes, links

one

Integration with other components

0.5

Hierarchy architecture

one

Own objects, infotypes, links

one

Versions of the plan. Object statuses

0.5

Reporting

0.5

Employer Benefits

3

Business processes

one

Infotypes

one

Reporting

one

Global Employee Management

3

Infotypes

0.5

Process

one

Compensation package

0.5

Payroll preparation

one

Office staff with multiple contracts

five

Administration Processes

one

Time management

one

Employer benefits

0.5

Payroll preparation

2

Posting

0.5

Post budget management

3

Liabilities

0.5

Budgets

0.5

Integration with other components

one

Budget management

one

Travel Management

five

Business processes

one

Planning

one

Travel expenses

2

Reporting

one

Pension Funds

3

Business processes

one

Functions

one

Integration with other components

0.5

Reporting

0.5

Programming in NSM-1

nineteen

Standard Reporting / SAP Query / BW

2

Using standard reports

one

BW content for NSM-1

0.5

Extensions for SAP Query

0.5

Workflow in HCM -1

five

Basic process

2

Workflow in Personnel Administration

one

Wbrkflow in time management

one

Wjrkflow in travel management

one

AVAR in NSM-1

ten

AVAR workbench

four

User-exits, badis, includes, enhancements

one

AVAR repository

2

MS Office integration (OLE, DPI), Adobe

one

Alv

2

Drilldown reporting + HR forms

2

Create drilldown reports

one

Creating Hrforms Reports

one

Administration in NSM-1

eleven

Authority

3

Setting up roles, powers

1.5

Structural powers

one

Content dependent permissions

0.5

Ale

2

Distribution model

one

Create, edit idoc

one

CATS

2

CATS Setup

one

CATS Integration

one

LSMW + SXDA

2

Batch input, direct input, BAPI

one

Upload to external systems

one

Archiving data

one

Archiving processes

one

Archive link

one

Archive link

one

In the " Weight " column, the maximum value for the skill is determined based on the overall significance of the skill for knowledge of the component as a whole.

The next step is to determine the level of employees in the context of each skill and calculate the overall rate.

Further, according to the technical competence, the grade of each employee is determined. The coefficient is defined as the total value of all weight values ​​for each skill.

Table 11.9. An example of assessing the technical skills of the project team members

Level 1

Weight

Level 2

Weight

Level 3

Weight

Petrov Ivan

Sidorov Arthur

Components NSM-1

70

Staff administration

12

Business processes

2

1.5

2

Infotypes

one

0.7

one

activity

2

1.5

2

Experience

2

one

1.7

Reporting

four

one

3

Interfaces

one

one

one

Time Management

ten

Business processes

one

0.8

one

Charts

0.3

0.4

0.5

Absence, presence

one

0.8

one

Limits

1.5

one

1.4

Temporary events

one

0

0.5

Time evaluation

1.5

0.8

1.2

Manager's Desktop

0.5

0.2

0

Shift Planning

0.7

0.1

0.7

Piece wages

2

0.05

1.5

Reporting

one

0.6

one

Payroll preparation

21

Business processes

one

0.8

one

Infotypes

one

0.8

one

Calculation of basic types of payments

2

one

2

Average calculations

2

1.8

2

Taxes

2

one

1.5

Hold

3

one

1.7

Non-cyclical calculations

3

0.5

one

Transfers

one

0.3

one

Posting

3

one

3

Reporting

3

one

2

Organizational Management

five

Business processes

0.5

0.4

0.5

Standard objects, infotypes, links

one

0.3

0.7

Integration with other components

0.5

0.2

0.4

Hierarchy architecture

one

0

0.5

Own objects, infotypes, links

one

0

0.2

Versions of the plan. Object statuses

0.5

0.1

0.4

Reporting

0.5

0.1

0.5

Employer Benefits

3

Business processes

one

0

0.5

Infotypes

one

0

0

Reporting

one

0

0

Global Employee Management

3

Infotypes

0.5

0

0

Process

one

0

0.2

Compensation package

0.5

0

0

Payroll preparation

one

0

0.1

Office staff with multiple contracts

five

Administration Processes

one

0

0.1

Time management

one

0

0

Employer Benefits

0.5

0

0

Payroll preparation

2

0

0.2

Posting

0.5

0

0

Post budget management

3

Liabilities

0.5

0

0.3

Budgets

0.5

0

0.3

Integration with other components

one

0

0.3

Budget management

one

0

0.5

Travel Management

five

Business processes

one

0

0.4

Planning

one

0

0

Travel expenses

2

0

0

Reporting

one

0

0

Pension Funds

3

Business processes

one

0

0.5

Functions

one

0

0.3

Integration with other components

0.5

0

0.3

Reporting

0.5

0

0

Programming in NSM-1

nineteen

Standard Reporting / SAP Query / BW

2

Using standard reports

one

0.7

one

BW content for NSM-1

0.5

0.2

0.5

Extensions for SAP Query

0.5

0

0

Workflow in HCM -1

five

Basic process

2

0

0.1

Workflow in Personnel Administration

one

0

0.2

Wbrkflow in time management

one

0

0.1

Wjrkflow in travel management

one

0

0

AVAR in NSM-1

ten

AVAR workbench

four

0.5

2

User-exits, badis, includes, enhancements

one

0.05

0.5

AVAR repository

2

0

one

MS Office integration (OLE, DPI), Adobe

one

0

0

Alv

2

0

one

Drilldown reporting + HR forms

2

Create drilldown reports

one

0

0

Creating Hrforms Reports

one

0

0.5

Administration in NSM-1

eleven

Authority

3

Setting up roles, powers

1.5

0.8

one

Structural powers

one

0.5

0.7

Content dependent permissions

0.5

0

0.2

Ale

2

Distribution model

one

0

0.8

Create, edit idoc

one

0

0

CATS

2

CATS Setup

one

0

0.5

CATS Integration

one

0

one

LSMW + SXDA

2

Batch input, direct input, BAPI

one

0.4

0.8

Upload to external systems

one

0

0.5

Archiving data

one

Archiving processes

one

0

0.2

Archive link

one

Archive link

one

0

0.1

Total

24.9

55.7

In tab. 11.10 presents the requirements for grades, developed on the basis of the experience of implementing projects on the functionality of SAP HCM -1.

It is important not just to make a register of this kind, but also to set a goal - to develop the skills of the maximum number of young employees; only then can the organization accumulate and maintain the knowledge and skills that it sells in the market.

Table 11.10. Description of grade consultants

Code

Description

Coefficient

K1

Consultant Trainee

0-19

K2

Consultant

20-34

K3

Senior consultant

35-44

K4

Lead consultant

45-59

K5

Expert consultant

60-100

When planning a project team, in addition to defining roles, responsibility and accountability in the project, a personnel management plan is created that includes defining the terms and methods for recruiting project team members, criteria for their release, recommendations for additional training. In the planning process, a concept of motivation is formed, ways of resolving conflicts are determined, a schedule of meetings of the project team and its participants is developed.

11.5. Project staff evaluation and management

Assessment of the competence of employees to their tasks is performed by comparing the qualification requirements for performing planned operations (see the vocabulary in the content management section) with the competence of employees determined using the skills register.

Evaluation of personnel qualifications is recommended only for work planned for implementation in the current and subsequent phase.

If there are concerns that the qualifications of some team members involved in the project may not be sufficient, a training plan for staff should be developed as part of the project plan. The plan may also include training programs for team members and their obtaining certificates, the presence of which contributes to the successful implementation of the project.

11.6. Definition of updated project requirements

The use of the quality function, which was originally considered in the section “Formation of Project Requirements”, is recommended during the entire life cycle of the project. For this purpose, it is recommended to develop three more “quality houses”: iteratively derived requirements (project requirements in the first quality house being developed at the planning stage) are moved to the primary (customer requirements in the first quality house) - this will ensure correct and consistent translation of customer requirements ( see fig. 11.2):

  • to the level of product requirements - 2nd quality house;
  • to the level of design work - the 3rd quality house;
  • before the quality program - the 4th quality house.

Each of the above iterations (see Fig. 11.2) solves the tasks of one of the three main project documents: the project's charter, a description of the content, and a management plan. At the same time, the contradictions found on the 2nd, 3rd and even 4th iterations of the formation of a multi-level quality house can be traced to the root causes, which are, for example, at the level of the customer's requirements, using the control loop mechanism.

  11. Planning project labor resources

Fig. 11.2. An example of the consistent use of the quality function

11.7. Monitoring project content and scope

This process, which is implemented at the design stage, is aimed at ensuring continuous monitoring of the project status and product content (project delivery result), as well as making changes to the basic plan for the project content. All changes to the project must be carried out in accordance with the procedures of the integrated change management project.

Table 11.11. Project status report template (adapted from [8]

PROJECT NAME

.

REPORT INFORMATION

Report preparation date

Reporting period

COST PERFORMANCE OF THE PROJECT

Current value deviation

[%]

Project cost for the current date according to the plan

Actual project cost

Approved estimated project cost

Project cost estimate at completion

CALENDAR DESCRIPTION OF THE PROJECT

Deviation from the plan

[%]

PROJECT STATUS

Issues requiring urgent attention from management

1. [Description]

2. [description]

3. ....

Changes in the content, cost and schedule of the project for the reporting period

1. [Description]

2. [description]

3. ....

Problems encountered during the period and actions taken to eliminate them

1. [Description]

2. [description]

3. ....

Key results and achievements for the reporting period

1. [Description]

2. [description]

3. ....

Key results scheduled for next week

1. [Description]

2. [description]

3. ....

In addition, it is recommended to keep a log of project status monitoring using the following template (see Table 11.11).

11.8. Management of project requirements

In accordance with the recommendations of the expert [5], requirements management activities include:

  • determination of the main version of the requirements (in other words, their documentation in the description of the content of the project);
  • assessing proposed changes in requirements and assessing the likelihood of the impact of each change before it is accepted;
  • consideration and adoption of resolutions for each change made in accordance with the adopted procedures;
  • discussing new commitments based on the estimated effect of changing requirements;
  • tracking the status of individual claims, -

Thus, project requirements management is implemented in accordance with the steps described in the project change management matrix (see the relevant section).

11.9. Assessment of user training needs

As part of the process of assessing user training needs, it is necessary to classify project participants in the context of the groups below, which will accurately determine and optimize the intensity of training individually for each group.

1. End users

These are employees who perform the bulk of transactions in the system being implemented. Most often they are called "users".

2. Key users

Key users are usually appointed from among the leaders of functional groups , they play several roles at the same time and are responsible for on-site training in their groups.

3. Information Users

As a rule, employees from among the managers who make management decisions, using the information obtained through reports from the information system.

4. Specific individual users

Table 11.12. Factors of choice of content and teaching methodology

No

Factor

Components

one

Conditions of education

Is it important to complete the training?

Will the results be reported outside the organization (department / unit)?

2

Availability of resources

Are there any subject matter experts in the organization?

Does the organization have development experience?

What is the available budget?

Is outsourcing the most efficient choice from an economic point of view?

3

Learning Content Attributes

How valuable is the object of study for the organization?

What character has the studied subject: informational, procedural, behavioral or conceptual?

How can I increase the intensity? Is group interaction necessary?

Do I need to update the curriculum content frequently?

What is the typical duration of teaching this material?

four

Target group

Do trainees have access to premises / laboratories?

Do all students speak the same language?

Do they have free internet access?

Is the material being taught new to the listeners?

How will this knowledge be used?

What learning style is closer to the majority of students?

For how long can employees be distracted from their core responsibilities for training?

What motivates employees to effective training?

Do all [potential] listeners live in the same time zone?

To what extent is it necessary to monitor the training and prepare reports on it?

Table 11.13. Forms of education (adapted from [5])

Form of study

Benefits

disadvantages

Audit training

o Habitual form

o Familiar atmosphere

o Engagement / high immersion listener

o Socialization and direct communication with the coach

o High cost

o Reproductive process (passive participation of listeners is allowed)

o Difficulty planning and planning twice

o Limited coverage and impossibility of replication

Internet-based training course software

o Interactivity

o Convenience and ease of replication

o Flexibility in class schedule

o Ability to select settings

o High risk of distraction from listeners

o Often, localization and basic PC skills are required from the listener.

o High development cost

Software training course on local media

o Interactivity

o Convenience and ease of replication

o Performance evaluation

o High risk of distraction from listeners

o Costly development and distribution

Virtual classes, online seminars (webinars)

o Convenience and ease of replication

o Interactivity for small groups

o Ease of development and delivery

o Reproductive process (passive participation of listeners is allowed)

o Required infrastructure for delivery

Conferencing

o Convenience and ease of replication

o Ease of development and delivery

o Background mode

o Low interactivity

o High risk of distraction from listeners

Manuals (templates and checklists)

o High portability

o Ease of use

o Low interactivity - almost no feedback

o High risk of distraction from listeners

o Difficulty updating material

Online portals with additional materials

o Convenience and ease of maintenance and replication

o Insufficient attention from users

o Difficulty in operating and maintaining relevance

Expert online communities: forums, groups in social networks, corporate wikis

o High interactivity

o Socialization

o Ease of use

o Difficulties with maintaining infrastructure and storing data

o Impossibility to use for certain topics and tasks

These are employees whose implementation of IT has little impact; nevertheless, they need to possess a number of skills to perform specific, narrow and clearly defined tasks.

5. Supervisors

This is a group of employees that does not directly work in the system being implemented; At the same time, its representatives should be aware of the principles of the process approach embodied in the implemented integrated IS.

After identifying groups of project participants from the point of view of their further work in the implemented system, it is also necessary to determine the combination of training tools. One of the approaches to solve this problem is the method described in the book by Luc Galoppen [5], - according to him, the choice of educational material and methodology depends on the factors and components, the characteristics of which are given in Table. 10.4.

Taking into account the result of the survey, a combination of types of training is formed from the standard list in Table. 10.5.

Thus, the result of this process at the design stage becomes the classification of various project participants by user groups and the formation of an optimal combination of types of training.


Comments


To leave a comment
If you have any suggestion, idea, thanks or comment, feel free to write. We really value feedback and are glad to hear your opinion.
To reply

software project management

Terms: software project management