10.16 Matching Resources to Business Need

---

Having the ability to look at the project from an overall scope-ofeffortrequired point of view will assist you in determining how much process is necessary to achieve the goals of standardization and delivery of business value to your organization. It makes no sense to form a Core Team and begin work on a project that can be completed by a single developer in a day. Generally, the BROC in an organization will set a dollar limit on the value of a project. This is a tradeoff—as is much in life—regarding the value of the effort versus the cost. If a programmer can solve this problem on his or her own in a day at a cost of less than $1,000, compare that to the cost of having a meeting with eight Core Team members for an hour and getting nothing but discussion and agreement accomplished. In one instance, you have agreement and no solution; in the other, you have a working solution. The point here is that each organization needs to determine the threshold at which constituting a team makes sense. In most organizations, that spending limit is set at $50,000 to $100,000. I have been in other organizations where it was only done for projects costing $500,000 or more. It is all relative to the business you support.

---