Resource allocation survey: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
== Overall Process == | == Overall Process == | ||
* Survey will be sent out first week of the following month. (i.e. | * Survey will be sent out first week of the following month. (i.e. June for May data) | ||
* Fill out the survey as soon as you receive it | * Fill out the survey as soon as you receive it | ||
* Survey results will be used to allocate our people costs to these initiatives | * Survey results will be used to allocate our people costs to these initiatives | ||
Revision as of 20:20, 7 June 2013
Link
Just looking for the link to the survey?
Here it is: Resource Allocation Survey
About
- Why is this survey needed?
- As we grow from our historical one product area roots (Firefox Desktop) to a multi-product organization, this survey is designed to help us figure out if we are spending our time and resources on the things that are the most important, and if not, to help us make re-balancing decisions over time.
- How will the data be used?
- Our intent is to publish this internal data monthly to help us all understand our activities and align them to our goals and investments on a more regular basis. Our collective goal is to ultimately to build a great activity feedback loop that maps what we are working on against our quarterly product and project goals. We believe this level of transparency will help us all increase our focus on ensuring we are all doing the right things at the right time.
- How often is this survey sent out?
- We are a dynamic bunch that is agile and mobile. Some will be on the same projects but some will change based on needs and/or timelines. This survey will be sent out on a monthly basis to capture any potential changes.
Overall Process
- Survey will be sent out first week of the following month. (i.e. June for May data)
- Fill out the survey as soon as you receive it
- Survey results will be used to allocate our people costs to these initiatives
- Finance then can provide more insights on how we invest against each initiative. This is an area we are currently estimating heavily. With the survey data, we will be able to provide more accurate analysis.
Schedule
- October 31, 2012 - March 31, 2013: Development, Testing, Staging and Fixes
- May 20, 2013: Email sent out to MoCo Employees
- Etherpad for questions & feedback
- May 20, 2013: Yammer Post Announcement
- May 22, 2013: Brown Bag