Thanks to the Capacity view, you'll have the basis for a pragmatic discussion to answer the question: are we capable of carrying out the projects planned for this year, this semester, this quarter?
The Capacity view will help you answer these questions, by team and for your entire organization.
Setting up a capacity system is often a cumbersome and time-consuming process. Maintaining it over time looks like an impossible task.
To overcome this problem, we've taken the following approach:
Here's how we make it happen.
There's no need to go into micro-detail: t-shirt sizing the scale of the milestone is enough to give you a good estimate of the time required.
When you're setting up your capacity planning, it's essential to think about the time you have available for projects (aka the build). Rather than doing this on an individual basis, we suggest you do it on a team level.
Maintaining a weekly capacity requires that all tasks start and finish within a week. At AirSaas, we want to bring you a more macro view, closer to your realities. You can choose the capacity time scale: quarterly, half-yearly or according to the duration of your IP.
Visualize at a glance if you are in trouble... or in trouble. Thanks to this view you have the basis for a pragmatic discussion to make decisions:
Can we do more projects? Do you have to remove them?
What are the milestones that are weighing us down? Can they be cut?
Should we recruit or put the team in tension? For how long?
Let's discuss, and book a free AirSaas trial.
The challenge is to divide up the teams into groups of people with similar skills. For example: data marketing, IT security, IT data, etc.
Yes, and if you have a more precise idea of the time needed for a delivery, you can also write it down.
It's up to you! What seems to work well is the quarter, because you can focus on the temporality of the organization (finance, commercial)
Cut it down! You're probably thinking about your last ERP or CRM project that lasted 18 months. We suggest that you break those types of projects down into deliverables that allow you to measure progress and reprioritize what needs to be done.
Yes, to know what can be done at the macro level. This is what Top Management often lacks in order to prioritize. Then you can give the person a capacity check at 2 or 3 months, but no more.
No worries, you create a team for your IT architect.
.webp "integration")
