Don't Forget the People Side of Project

Find opportunities — and win them.

I read your article in the Nov. 20, 2000, issue, "AMS Sues National Union Over Mississippi Troubles." The article focused on lawsuits that have occurred on large, state automated projects.

I read your article in the Nov. 20, 2000, issue, "AMS Sues National Union Over Mississippi Troubles."The article focused on lawsuits that have occurred on large, state automated projects. In further explication [in the sidebar "Big Projects, Big Failures"], a judge ruled in favor of Lockheed Martin Corp., finding that the state of California failed to ensure the cooperation of the counties in the development of the California Statewide Automated Child Support System. As a social worker who is familiar with technology use in education and human services, it appears California officials and Lockheed Martin implemented this project as a pure "technology project" rather than a "people project," demanding equal importance with the technology. Lockheed Martin and California failed to build an organizational team with users, management and technical staff working together in project planning, development and execution.

Letters to the Editor
Washington Technology welcomes letters to the editor. Please cite the issue date and headline of the article to which you are referring. Letters will be edited. Include your name, job title, company for which you work and its location, and your e-mail address. Names will be withheld upon request, but we do need to contact you to confirm you are the letter's author.

E-mail your letters to Steve LeSueur, slesueur@postnewsweektech.com or send them to:

Steve LeSueur, Editor
Washington Technology
8500 Leesburg Pike, Suite 7500
Vienna, Va. 22182

I have not read anything about project committees, interagency collaboration or communications matrixes. When users, management and technical staff work together, problems such as outdated hardware and growth in caseloads can be identified as they arise and resolved.Although there will still be temporary systems crashes and frustrations, a team approach can ensure ultimate success and avoid project failures. As an example, Massachusetts, which formed an organizational team in building their FamilyNet System was among the first 18 states with an operational system in September 1998. Rebecca Sager Ashery
Doctor of Social Work
drrebecca12@hotmail.com