Skip to content

Resource Allocation Process

After a project is vetted (and before it is signed, if possible), it is important to know the resources that will be used to fulfill the project.  Additionally, in the event that a project loses active resources it is important to refill the position.  

Here is some guidance around our staffing and project policies.

  1. We find work for employees first above contractors
  2. Fill positions with employees before contractors
  3. Whenever possible, have the engineer who will be doing the work, bid the work
  4. For employee engineers who are not full-time on a project, add them as a shadow or a participant on a real project.  Notes:
    1. A real project will be better than a training class (although a training class may be necessary in order to start on a real project).
    2. Bill, if possible (without affecting the budget), but can include non-billable work to the client.
    3. Work can include testing and support, even if they are engineers.  For example, put Drew on testing and support on projects.
  5. Strive to have 2 brains with domain knowledge on every projects (hit by a bus problem)
  6. We have the ability to set the timeline.  Should always underpromise and overdeliver.  If the client timeline isn’t going to work, just say that and give a timeline on when we can get it done. Honesty is the best policy.
  7. If we bring in a principle-level engineer, have an employee engineer learn and shadow so we don’t need them in the future.

Here is a link to the current list of engineers associated with Lab 651. Engineering Coverage 

Here is a link to the decision flowchart for assigning engineers.  Engineering Decision Tree 

Here is a link to a gap analysis for our current projects.  This should be updated as new clients/projects are added and old clients/projects leave.  Client Gap Analysis