2.6 Develop an Issues List

< Day Day Up >

Now, we have already accomplished two things. We have uncovered some serious issues. For example, there is no mass transit to link the airport to, and no water, sewer, or telecommunications infrastructure at the site. Second, we know with some specificity how much we do not know. This we can document as an issues list that will be circulated relentlessly. With a little common sense, we can build an airport issues list that probably would look like Exhibit 3.

Exhibit 3: Airport Project Issues List

Financing: how does that play out?
How do we handle the politicians?
Do we have staffing to provide environmental studies work?
Airlines: how many, gate assignments, and features?
Catering, plane cleanup, fueling, and plane maintenance?
How many terminals, what style, and how many floors?
Runways: how many, how long?
Luggage handling and tracking.
Fire department, public safety, and security.
Bathrooms, garbage, and other health or sanitation requirements.
How do you hook up to mass transit, and what will that be?
Shops, hotels, restaurants, VIP lounges, and bars.
What about air freight?
Where do smokers go?
Pay phones, arrival/departure displays, etc.
ADA (Americans with Disabilities Act) requirements.
Grounds: landscaping, public park, or other "features."
What do the FAA (Federal Aviation Administration, Customs, and INS (Immigration and Naturalization Service) need?
Private aircraft and charters.
Internet kiosks for travelers?

Of course, this is just the beginning of the fun. You need a game plan to deal with these issues. I recommend the following strategy:

Eliminate as many issues as possible, particularly if they do not impact scope.
Those issues that cannot be eliminated get assigned to specific individuals.
Issues assignees must convert issues into assumptions by a specified date.
Assumptions are then circulated for refinement and acceptance.
Only upon sign-off does an assumption become a requirement.

< Day Day Up >