Service providers who carry out projects for their customers generally want two things: on the one hand, a fast and satisfactory result for their customers, and profitability on the other hand. An optimal allocation of employees to the projects is crucial. Yet, we often see that project and resource planning is limited to a one-off activity at the start of the project. Shouldn't more attention be paid to this?
If you look at the picture, you might be thinking there are more stones and sand in the first jar than in the second jar, but nothing could be further from the truth. The second jar contains the exact same amount of sand and stones, only the content doesn't fit in the first jar. That has to do with the order of filling the jar. If you first fill the jar with the large stones, then the smaller stones and
For many organizations, they are only able to see in hindsight what the margin was they achieved for their project, which for many, leads to disappointment. The project ended not being as profitable as they had thought. Even while remaining within the budgeted number of hours. How is that even possible? An analysis showed that they, for example, relied on freelancers instead of internal staff on which the project was budgeted. Or that more senior employees were used, disproportionately, which
I have been in touch with a number of organizations lately, which had all tried to plan their projects in Workforce Management software. In other words, they tried to make up a roster of their projects in rostering software. Can this actually be done and if so, what are the limitations? In this blog we will look at this, using a practical case.
If you create many small tasks and include in your planning, you can end up "blowing up" you planning. The risk is that you will end up spending your entire day on updating your planning, especially in a dynamic environment that requires many changes. This blog will explore what alternatives there are and what factors determine whether you should plan in detail or not.