My team and I are trying to figure out how many resources we need for a year. Forecasting our time has proven difficult, because internally to our organization our time is not tracked hourly, but is known as Business As Usual, which usually denotes coming off of a bottom line SOMEWHERE, but it's not specific to a specific project per se.
There in lies the problem.
We are slated for a lot of new projects, with promise of funding, amount of scope on the projects, etc. and we're trying to see what's truly feasible to work within our project timeline. Our release schedule is such, that there SHOULD be a natural ebb and flow to the projects, yet lately we're not seeing that happening and we're struggling with finishing projects we've started documentation on 8 months ago while trying to wrap our brains and drive out business requirements for 2 months from now.
As you can tell from my rambling, it's a little bit of a headache. ;)
So, here's my question.
From a resource planning perspective, how have you or others you know within large scale organizations account for a) all the amount of documentation, testing, etc. to happen, and align that with timelines.
I'm thinking of starting with an equation to at the very least get a ballpark number.
Here's a rough idea of what i'm thinking: Project scope value * Usability Testing funded (yes/no) + paper prototpying(1 week) + iterative testing(5 weeks of prototyping) / Amounf of time till delivery = OMG! WHAT JUST HAPPENED!?! ;)
Have you used something similar in your resource planning for UX? Thank you for your help in advance! :) ~Josh