Develop a strong collaborative process for software acquisition.
A national experience in acquiring software for ITS projects.
- Work closely with others in your agency. A software acquisition is a collaborative process. Project managers cannot do it alone or make unilateral decisions. Instead, they must work closely with others in their agency. For example, the end users must be involved at all points to help decide what the system should do, determine how users will interact with the system, and participate in making tradeoffs between cost and functionality.
- Involve the software contractor. Collaboration also extends beyond organizational boundaries to involve others, especially the software contractor. The contractor is in a better position to determine the possible design ramifications of seemingly innocent requirements. The contractor also has experience to draw upon in determining how best to meet the transportation agency’s needs.
- Build a team of professionals. Many skills are needed for carrying out a software acquisition. No one individual or agency can possibly have all of them. Therefore, a team of professionals is needed. Some of the diverse skills represented on the team include hardware, software, and systems engineering; contracting, operational, domain, and legal expertise. By having the contracting office on the team, the transportation agency will be able to explore the range of contracting mechanisms and find the one that is most appropriate for software. A team is more than a collection of players with diverse skills. To be part of a team, the member must work together towards common goals and objectives. The foremost goal sought after is to establish mutual trust among the team members. Trust helps achieve the functional goals and objectives of the software acquisition.
- Maintain open communications with the contractor. Because transportation agencies and suppliers approach software from very different perspectives, there will be misunderstandings unless open communications are continually cultivated. The communications must start even before a contract is signed in regards to terms and conditions, and especially intellectual property rights. Open communications proceed with discussions on requirements and continue with any and all decisions through acceptance testing and maintenance.
- Require continuous, active involvement by the owning transportation agency. The agency cannot simply “turn things over” to a contractor or systems manager. On transportation construction projects, it may be sufficient for the owning agency to take a more passive role, perhaps conducting inspections. But for software, up to half the total requirements and design effort may actually be expended by the agency and end users, even after a software contract has been issued. Clearly, sufficient resources must be allocated for this agency involvement to take place. Active agency involvement also means a willingness to decide upon and commit, in writing if necessary, to a specific course of action after various options have been presented.
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-035URL: http://ntl.bts.gov/lib/jpodocs/repts_te/4130.pdf
Dr. Arthur Salwin
Average User Rating