Lesson

Make use of different approaches and techniques to manage software acquisitions.

A national experience in acquiring software for ITS projects.


July 1998
United States


Background (Show)

Lesson Learned

Software acquisitions will involve situations that may be unfamiliar to many Department of Transportation (DOT) project managers. Construction projects usually include a set of design requirements and, with the exception of a few change orders due to unforeseen circumstances, the contractor usually adheres to the requirements to complete the project successfully. This is usually not the case with software acquisition. Intuitions gained from managing construction projects do not necessarily work with software. Software needs to be managed differently. However, there are established techniques to managing software acquisitions successfully.
  • Maintain flexibility throughout the acquisition. Flexibility is needed in the contract to accommodate changes and take advantage of opportunities that may present themselves during design and implementation. With software, there needs to be more give and take than on typical construction projects that are successfully built to a rigid set of design specifications. Flexibility is needed in the requirements, in the working relationships, in the contracting mechanism, and most importantly, in the mindsets of those involved. At the outset of a project, a flexible mindset allows a wide range of options to be considered in selecting the most appropriate contracting mechanism, perhaps even some that have not been tried previously. Similarly, in developing the requirements for a system, there has to be recognition that the users may not be able to get everything they want; there may be tradeoffs among functionality, price, and schedule. Caution in maintaining flexibility is necessary as well; there can be too much flexibility where the scope of the project is increased or new requirements continue to be added. These situations should be avoided.
  • Address all acquisition activities in the planning stage. Up-front planning is needed early in the acquisition, even for activities such as system acceptance that do not take place until late in the acquisition process. Activities such as requirements walk-throughs, design reviews, training, acceptance testing, and maintenance do not take place until after a contract is awarded or even at the end of the project. Nonetheless, these items must be planned up front, even before a Request for Proposal (RFP) is issued. This allows the procuring agency to plan for the various activities in the project schedule and allocate adequate time for them. It also enables the agency to address the operations and maintenance concepts, system acceptance criteria, and software intellectual property rights in the RFP and contract. Conformity with the National ITS Architecture is another area to address in the up-front planning of a project.
  • Recognize that there are no "silver bullets." No one acquisition practice or contracting mechanism is the solution that can be relied upon to ensure project success. As an example, there are some in the ITS community that believe new contracting mechanisms for software are needed. This is probably a good idea; although new mechanisms will not solve all problems with software procurement.
The techniques described above are not necessarily unique to software acquisition. They represent good management practices and can be applied to other types of ITS projects as well; however, relying on these techniques may contribute to the success of an ITS software system acquisition. Each agency should choose the techniques that are the most appropriate for their project criteria. Maintaining flexibility, addressing all acquisition activities during planning, and recognizing that there is no one cure-all for software acquisition will provide the project manager with solid footing to successfully procure ITS software. A successful software acquisition can have a significant impact on an ITS project. The agency benefits from a project completed cost effectively and in a timely manner; while the traveling public benefits from a system that improves safety, mobility, and efficiency.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

The Road to Successful ITS Software Acquisition: Executive Summary, Volume I - Overview and Themes, and Volume II - Software Acquisition Process Reference Guide

Author: Arthur E. Salwin

Published By: U.S. Department of Transportation Intelligent Transportation Systems Joint Program Office Federal Highway Administration

Source Date: July 1998

EDL Number: 4130

Other Reference Number: FHWA-JPO-98-035

URL: http://ntl.bts.gov/lib/jpodocs/repts_te/4130.pdf

Other Lessons From this Source

Lesson Contacts

Lesson Contact(s):

Dr. Arthur Salwin
Mitretek Systems
202-863-2985

Lesson Analyst:

Cheryl Lowrance
Noblis
202-863-2986
cheryl.lowrance
@noblis.org


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)



Notes

Lesson of the Month for October, 2006 !


Application Areas

None defined

States

None defined

Countries

United States

Focus Areas

None defined

Goal Areas

Productivity

Keywords

None defined

Lesson ID: 2006-00275