+++ Choosing which PM resource planning processes to implement at your company +++ How the organizational structure affects project resource management processes +++
How can you determine if your resource planning processes for project management are adequate? What requirements do they have to meet?
Resource planning processes are shaped by your company’s form of organization. This article will outline how the process of resource planning differs between matrix and line organizations.
Appropriate process cycles are important for both forms of organization, and resource commitments should always remain stable over an entire cycle.
Note: By tactical resource planning, we mean the coordination between project and line managers. This is dependent on the company’s form of organization (matrix or line). The goal is to meet the project resource requirements by providing the necessary skills in a timely manner using the line staff. This tends to be the team leaders’ responsibility.
In this article, you will learn more about:
- What is resource planning in project management?
- Requirements for the coordination process between project and line managers
- The solution: a suitable planning cycle
- The planning process in the line organization
- The coordination process in the line organization
- The planning process in the matrix organization
- The coordination process in the matrix organization
- Conclusion – processes for resource planning in project management
What is Resource Planning in Project Management?
Definition: Resource planning in project management is a key element of project management. It ensures that a project has access to the necessary resources (staff, facilities, etc.) at all times. This planning is very closely related to the development of schedules and budgets.
Resource planning is an important part of project management because:
- Resource planning in project management, together with resource management, helps a company reach its targetsby focusing on optimization and efficiency.
- The goal of every company is to achieve its objectives with as little effort as possible.
- Knowing what you need for the project to be successful lets you plan effectively and make economic use of the available resources.Larger companies often have a resource manager for specifically this purpose. This person relieves project managers of tasks such as organizing the necessary resources for already planned projects for the team leaders involved.
Requirements for the Coordination Process between Project and Line Managers
On the one hand, project managers tend to desire resource commitments from the line managers as fast as possible because they need these commitments to plan their projects. On the other hand, these commitments should be truly reliable.
Given these constraints, the following problems emerge for team leaders:
- Multiple project managers will send repeated requests to the same team leaders at different times
- This hinders the team leaders from having a stable basis for their decisions
- Yesterday’s carefully coordinated plans may be obsolete today already due to a new incoming request
- Team members are often assigned responsibilities outside of projects. This affects productivity in the projects.
The Solution: A Suitable Planning Cycle
The key to success is to agree on a planning cycle. This can greatly help facilitate the resource planning process.
The length and duration of the cycle should be aligned with the lifespan of projects at your company. The organizational effort for planning and coordination needs to remain within reasonable limits over the long term.
The important thing to remember is that the longer the cycle, the more stable the system. However, too long also means too rigid. Cycles between one and four weeks are customary and useful.
We recommend starting with a monthly cycle. This will ensure acceptance without overwhelming the organization. Only shorten the cycle once the system works and if the dynamics require it.
Our tip: Start with a monthly planning cycle. This will ensure acceptance without overwhelming the organization. Shorten the cycle to 2-3 weeks once you know that the system works and if the dynamics require it.
Get everyone involved to agree that PM resource plans for the current and the upcoming cycle can only be changed under exceptional circumstances. The use of resources should only be rescheduled for subsequent cycles.
This will save the company a lot of coordination effort because you won’t have to deal with constant changes. Instead, rescheduling only happens at fixed intervals.
Another interesting read: The Challenge of Resource Planning in Project Management
This approach requires all the participants to work harder at coordination. Ad-hoc changes only happen as a last resort. This lets the project be handled more efficiently because it shields staff members from interference for a longer period of time.
The figure below shows this type of process cycle at the levels of the roles involved.
Here is a practical example:
- First, the team membersmust submit their time tracking reports by Friday.
- The project managersmust accept these by Monday night and reschedule the resulting remaining effort.
- This may result in resource conflicts that only become apparent on Tuesday after all project managers have updated their plans (red square).
- The team leaders have until Tuesday night or Wednesday (red circle) to resolve any conflicts. It is essential that the priorities are aligned with the strategy. Remember that those involved need to understand the strategy so that it can be considered here.
- Finally – depending on the PMO competencies – there will be a meeting with a steering group / top management in which the resolutions are passed for all remaining decisions resulting from conflicts.
Below you will find out how the planning processes differ between line and matrix organizations.
Our tip: Get everyone involved to agree that resource planning in project management for the current and the upcoming cycle can be changed solely under exceptional circumstances. The use of resources can only be rescheduled for subsequent cycles.
The Planning Process in the Line Organization
In the line organization, the negotiations are not about people but rather the deliverable deadlines. The project managers plan which deliverables they need by what date. They forward these requirements to the team leaders.
The detailed planning is done by the line managers. The project manager is not involved in resource planning at the level of individual staff members.
Project managers in the line organization are mainly involved in coordinating the scheduling of projects and sub-projects or work packages. Resource coordination takes place within line departments / teams. The team leader is responsible for this.
In this environment, stable process cycles and traditional PM tools enable multiple projects to be managed transparently and can produce very good results.
In a line organization, team leaders can also use PM tools. These help them create detailed plans involving factors such as tasks and times (including absences) for their team as shown in the figure below.
In addition to project tasks, it is also possible to manage the team’s operations using the project plan. This means that the team leader only has to maintain one plan because it also includes all the team’s tasks:
- Project-related tasks
- General operations
- Individual operations
Special Download: Resource Planning Software for the Roles Involved (PDF file)
Please fill in the form.
* Required Fields | Data Protection
The Coordination Process in the Line Organization
The coordination process in a line organization looks roughly like this:
- The project managers plan approximate work packages – without the details or resources, but with the planned efforts / budgets.
- The project managers forward their rough plans / milestones to the team leaders.
- The team leaders integrate these rough plans / milestones into their own plans.
- The team leaders break down the work packages into individual tasks in their own planning. Next, they assign these tasks either only to people in their own team or also to external resources.
- The team leaders’ planning can be checked against the project managers’at the level of work packages with regard to scheduling and efforts (see yellow bar on the left in Figure 2).
- The variances are visible on both sides. The project manager and the team leader need to discuss these variances to coordinate and eliminate them.
It is vital that the project manager and team leader each use their own planning. In a separate step, the two plans are checked against each other.
Our tip: Make sure that the people in these roles aren’t able to change each other’s data! Protecting the autonomy of each person’s data enables project managers and team leaders to plan independently. Nonetheless, there should be a technical link between the team leader’s and the project manager’s plans to enable the sharing of data. This can be used to coordinate the use of resources.
The Planning Process in the Matrix Organization
The matrix organization is a different thing altogether. Traditionally, project managers plan their projects with detailed tasks. They then assign these tasks to people or skills (generic resources).
The team leaders or the respective teams are the ones who decide which people are committed to them and to what extent. The team leaders must consider all the requests from different project managers, as well as the absences and operations, to explore the possible commitments.
However, it usually makes little sense to make these commitments at the individual task level. As a rule, team leaders do not need to know which exact tasks have been assigned to their team members. They are more concerned with which team member is working on what projects – and when. For this, it’s enough to have the project managers coordinate this at the project level.
Looking to introduce resource management? Here is how to do it fast and well.
Team leaders in a matrix organization have the undesirable task of handling commitments of the required resources for different projects. In most cases, traditional project management tools are inadequate for handling this. Why is this? Because the team leaders’ commitments are not maintained as an individual data pool. They are normally only marked with the status of the project or task.
The inherent problem: Postponements can occur in a project. If this happens, the staff commitments (which are only assigned a status) are simply postponed along with the tasks. However, team leaders only commit staff resources for designated periods of time. This is logical because these same resources also need to work on other projects. For this reason, postponements usually result in resource conflicts, which spark new discussions (and require additional coordination).
For the coordination, the project manager and team leader need to maintain their own planning data at the project level. These need to be compared (see figure below).
If there is only the project managers’ plan, the team leaders are completely “at the project managers’ mercy”, at least in terms of the data. They can suggest ways to resolve the conflicts, but this will not change the project managers’ plans. Neither can they negotiate with all project managers at once.
To be able to make commitments to the projects, team leaders need to first plan the absences and operations. They can only determine the real availability of a team member for the project on this basis. The team leaders therefore need their own separate planning.
The Coordination Process in the Matrix Organization
This is what the resource planning in the project management process in the matrix organization looks like:
- The project managers plan their projects in detail at the task level.
- The project managers assign either people or skills to the tasks.
- The team leaders determine the project availability of their team members from capacity minus absences and operations.
- The team leaders analyze the resource requests from the different projects. They commit their team members for available periods of time.
- The project managers incorporate these commitments (as time frames) at the project level. Within these time frames, the project managers have flexibility in planning the tasks.
- By comparing both roles’ planning, variances become visible. This provides a good basis for direct discussions to coordinate the efforts.
Our tip: Ensure team leaders in a matrix organization have their own planning in which they also manage absences and operations. This enables an accurate evaluation of the availability and gives project managers the confidence to rely on the resource commitments.
Free Download: eBook “Tactical Resource Management” (more than 80 pages)
Resource planning between project managers and team leaders is always a challenge in project management. In this free eBook, you will learn how meeting this challenge can become easier.
> Click here to download your free copy of the eBook.
Conclusion – Processes for Resource Planning in Project Management
This article has described the requisite processes for resource planning in project management. It has also shown how these processes are shaped by the organizational structure. In addition, we have presented examples showing how these processes can be coordinated within the line and the matrix organization.
For both forms of organizational structure, make sure that you establish adequate process cycles. Your team leaders cannot respond to resource requests for the coming week several times a day. You need to gather requests for the cycle after next, as well as the subsequent cycles, over the period of the current cycle. Responses to the requests are only required by the due date.
Ensure that the commitments for the current cycle remain as stable as possible. Changes should only be permitted under exceptional circumstances. This approach makes resource coordination reliable for all involved. It also allows the project to be handled more efficiently, as each member of staff is able to work free of interference for a longer period of time.
Please send us your feedback!
What experiences have you had with successful program management? Is there a critical success factor that you feel we have missed? Have these tips been helpful? Please let us know in the comment area below. We look forward to your feedback!
Final tip: Subscribe to the TPG Blog Newsletter now and never miss another blog post.
About the author: Johann Strasser, a certified engineer, has been a managing partner at TPG The Project Group since 2001. After many years as a development engineer in the automotive and energy sectors, Johann Strasser spent a decade as an independent trainer and consultant in the field of project management. During his tenure, he also served as project manager for software projects in the construction industry and provided scheduling and cost management support for large-scale construction projects. At TPG, he applies his expertise in product development and consulting services for international clients. His special focus is on PMO, project portfolios, hybrid project management, and resource management. For many years now, he has shared his knowledge through presentations, seminars, articles, and webinars.