Information Technology Reference
In-Depth Information
failed until several hours later in the day, you are unable to take imme-
diate action and fix the problem before it propagates and causes other
failures. The same goes for a database failure or a failed deployment.
Feedback is necessary to take action, and it provides the real, current
status of your integration build (see Figure 9-1).
Information on a software project is always changing. As the
ancient Greek philosopher Heraclitus noted, “The only constant is
change.” We must communicate information to our customers, devel-
opers, management, or any other stakeholder on a project, and it is
vitally useful when it is pertinent, concise, and up-to-date. While face-
to-face communication may be the most effective, it is
not
very scal-
able. Making feedback
continuous
provides a team the capability to
inform more people on more projects automatically; moreover, this
information can be aggregated to detect trends across a project.
This chapter covers why and how to send the right information to
the right people at the right time and in the right way.
Compile
Source Code
Integrate
Database
F
e
e
d
b
a
c
k
Integrate
Run
Tests
Run
Inspections
Deploy
Software
Improving Software Quality and Reducing Risk
Providing feedback with the Integrate button
FIGURE 9-1
