The BAM List

When an organization starts a new project, there is often a flurry of activity. Most of it revolves around cost in some form or fashion.

Some questions I’ve seen asked at the onset:

  1. How many people will this require?

  2. What types of resources will be used?

  3. What is our budget allocation?

  4. When are deliverables due?

Where I have seen organizations struggle, though, is in allocating resources to get started. Different types of projects require varying levels of expertise. A lot of discovery time is spent determining the right group of people and technologies to achieve success. More often than not, none of that information is recorded for future use, though.

Enter the concept I like to call the Bare-Ass Minimum (BAM) List.

A BAM List is a way to record, at a minimum, what is required to get a project underway. This can include:

  1. Roles

  2. Technologies

  3. Cost of these resources.

It sounds simple, and honestly, it is. If you find that your organization undertakes similar projects, such as a common CRM for a client, then create a BAM List for it. Who is involved, what technologies are you using, and what is the cost each time? If your organization does a lot of prototyping, identify the commonalities and create a list.

You don’t have to create one BAM List; make one for each identified situation. That way, your discovery phase doesn’t have to spend resources on figuring it out each time.

How can a BAM List help your organization?

If you are bidding on a contract and need to determine if it is feasible, a BAM List will provide a quick, ballpark figure to work with. Is it doable for you to perform the work within the allotted budget? Your BAM List would be a good indicator.

Does your organization have a new application idea? What will it cost to create a workable prototype? Your BAM List will give you an idea of where to start.

This isn’t a new concept, I’m just providing you with an easy-to-remember idea. Additionally, it allows your project manager a chance to say 'BAM' a lot, which is fun.

And that, folks, is half the battle.

Previous
Previous

The Cost of Quality - Bugs vs. Defects

Next
Next

Scope vs. Impact