RELATED IDEAS
Resource capacity leveling for individuals and Teams
Add leveling options for as soon as possible (front loaded), Level across the duration, As late as possible (back loaded), and Manual.
Currently, leveling is only front loaded which makes it difficult to manage a resource who spends 10% on support during a year i.e. requires multiple features for each individual.
Like wise this would be useful for Teams.
© 2024 Aha! Labs Inc.•All rights reserved
This would be very helpful to me and my time.
Let me give you an overview of what our team does. As solutions architects/engineers, we are responsible for working with customers to identify their specific needs and then we propose a mix of already built applications and integrate those applications where necessary into the customer ecosystem. We refer to one such integration as a “program”.
Most of our work is in ensuring that the solution is documented and the requirements are agreed to. Throughout the solution integration and after delivery, we support internal teams and customer teams with any questions, concerns, or requirements questions that arise.
This support is not insignificant. For example, during different phases of the program, we can expect to spend an hour per month supporting the customer, an hour per month supporting our integration teams, and an hour per month supporting our field teams.
Each member of our team may be assigned between 5 and 10 simultaneous programs so it’s very possible that support may add up to 10 or more hours per month (about 7% of total capacity).
I did consider adding these support tasks per month, but just having these tasks in the board would overwhelm the other items of work we need to do for a program. For example, I currently have defined 25 activities/tasks. Breaking the task down by month would add approximately 33 more activities across an 18 month program.