Information Technology Reference
In-Depth Information
All the Right Stuff
Sending information to whoever, whenever, however is not what will
achieve results. The purpose of feedback is to create a notification that
most quickly and precisely stimulates action. You must send the right
information to the right people at the right time and in the right way . In
considering the right information, we first focus on the type of infor-
mation we are sending and ensuring that it is accurate. Next, we discuss
who gets the information, why they get it, and when they receive it.
Continuous Feedback and CI
Getting the right information to the right people at the right time
and in the right way—CI is the best tool for making this feedback
automated, targeted, and real-time (continuous).
Finally, in discussing the right way to send information, we'll dis-
cuss some of the communication mechanisms that can be employed
with a CI system, which are known as continuous feedback devices
(CFDs). CFDs typically notify project stakeholders of the success or
failure of a build, but they also can notify them of other issues. For
example, a CFD can notify specific parties that a threshold has been
exceeded (e.g., code duplication has gone over a specified percentage).
Figure 9-2 illustrates this approach.
The Right Information
Continuous feedback doesn't take the action to improve the software,
project members do—typically, software developers. The information
may be useful to others, such as analysts, testers, and management, as
well. Continuous feedback provides the means to structure the infor-
mation, and you decide what portions are delivered to which project
members upon certain events. You and the other recipients know both
that the information is accurate and fresh and that you are taking the
most effective action to solve an issue. Instead of waiting for stake-
holders to notice they have questions and then putting them to you, you
 
Search WWH ::




Custom Search