Download K. Fowler (CRC, 2008) BBS - Web server administration

Aerospace Video Processor
11.16
11.16.1
277
Summary
Do It Right
These folks recognized the problems with bad processes midway through
the project. They reevaluated, regrouped, instituted good processes, and
pushed through the problems to a successful end result.
This project had enormous potential for severely damaging the customer’s reputation and its relationship with its final customer. Both sides took
tough measures to complete the work; the customer insisted on recovery
and good processes and then worked as a team member to accomplish those
goals; Ecliptic agreed to change its processes. These two companies ended
up working together well and hopefully have a new level of trust.
11.16.2
Emphases
This subsystem was simpler than many spacecraft projects because it did
not have the level of documentation and qualification required for those
space projects. It represents a good middle ground for space flight experiments and instruments that do not need the standard space guidelines or
bureaucracy.
This case study ends well—which is unusual for projects that encounter
serious difficulties midway. The development of this video compressor/
multiplexer system had complex components, interactions, and processes. It
only succeeded because good people with good attitudes did good work
with the right processes.
11.16.3
Gotcha’s
The customer, who called me in to help solve the problem, was part of the
problem in the beginning. Their contract was weak; it did not provide any
requirements for custom development. This meant that they did not have
recourse if the product did not perform as they had expected. Expectations must be clearly communicated—the requirements must be clear and
well-thought-out! Contracts must state the requirements and development
processes expected if any custom work is to be done.
Acknowledgment
My thanks to Douglas Caldwell at Ecliptic Enterprises Corporation for
helping to provide some of the information for this chapter.