08.01.2013 Views

Back Room Front Room 2

Back Room Front Room 2

Back Room Front Room 2

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

50<br />

ENTERPRISE INFORMATION SYSTEMS VI<br />

more interworking among roles and people. Do you<br />

think work gets done in meetings and through<br />

management channels? Guess again. Grinter and<br />

Herbsleb (Grinter Herbsleb 1999) argue that most of<br />

the useful communication in an organization takes<br />

place in the hallways. WATER COOLER is a closely<br />

related pattern.<br />

6.6 Face to Face Before Working<br />

Remotely<br />

If a project is<br />

divided geographically,<br />

Then: begin<br />

the project with a<br />

meeting of everyone<br />

in a single place. Of<br />

course, you want to<br />

avoid geographically<br />

distributed development<br />

when you can. If you must support remote<br />

development, invest in a travel budget so people can<br />

meet face to face. If you think it’s too expensive,<br />

experience indicates that you pay now—or pay later.<br />

(The picture was taken at Camp Carson, Colorado,<br />

and shows Colonel Wilfrid M. Nlunt, the U.S.<br />

commanding officer shaking hands with Colonel<br />

Denetrius Xenos, military attaché of the Greek<br />

ambassador to the United States—a face-to-face<br />

meeting before working remotely.)<br />

6.7 Apprenticeship<br />

If you have difficulty<br />

retaining expertise, Then:<br />

grow expertise internally<br />

from existing employees or<br />

even new hires. Don’t put<br />

everyone through one big<br />

training program. Nurture<br />

expertise (another one of our<br />

patterns is DOMAIN EXPER-<br />

TISE IN ROLES).<br />

7 TOWARDS A PATTERN<br />

LANGUAGE<br />

Each one of these patterns incrementally adds<br />

structure to the organization: structure between the<br />

organization and the customer, structure between the<br />

organization and its developers, structure that cuts<br />

across formal structures, structure across geographic<br />

distance, and the establishment of a structural link to<br />

a new hire. We can build these structures one at a<br />

time. These patterns, and dozens like them, combine<br />

and interact with each other in rich ways to yield an<br />

overall structure that is more powerful than the sum<br />

of its parts. We can put patterns together in many<br />

different ways to achieve many different<br />

organizational styles. Imagine patterns as being like<br />

words in a language, and imagine a grammar that<br />

defines legal combinations and sequences of these<br />

words. Such a collection of patterns, together with<br />

the rules for composing them, is called a pattern<br />

language.<br />

Pattern languages rise to deal with system<br />

concerns. They can handle so called “wicked<br />

problems” where it’s difficult to determine a proper<br />

solution given the observed symptoms. What most<br />

organizations do when faced with such symptoms is<br />

to just try anything—which, in fact, is better than<br />

doing nothing. Patterns are a more informed way of<br />

just trying anything. They build on years of<br />

experience, on the experience of hundreds of<br />

organizations that have faced analogous situations in<br />

the past.<br />

Pattern languages build cultures. They bring<br />

development beyond something technological to<br />

create structures and processes at human scale. They<br />

help restore the human dimension to software<br />

development. We encourage organizations to use try<br />

these patterns, to write their own organizational<br />

patterns, and in general to use patterns to unleash<br />

their own instincts to do what is right, humane, and<br />

for the greater good. Many of these patterns are<br />

common sense. In a world full of methods,<br />

notations, and processes, common sense is so<br />

uncommon.<br />

8 CONCLUSION<br />

What is the bottom line? All of this talk about beauty<br />

and human value is fine, but it is profitability and<br />

market position that dominate software conferences<br />

and business plan. Any viable idea must ultimately<br />

stoop to that level of concern. So, then: Where does<br />

business success start?<br />

Business success starts with business values: the<br />

principles and value systems that an enterprise uses<br />

to judge its success. Does success depend on<br />

usability of the software? Or does your company<br />

base success on sales? Can the latter be an accurate<br />

reflection of the former? Profitability owes to much<br />

more than to having a great product; it owes just as<br />

much to being first to market with a product, or to an<br />

effective sales campaign. Most markets focus on the<br />

so-called bottom line as the measure of success.<br />

Profit is an abstraction that has allowed businesses

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!