28.06.2013 Views

Papers in PDF format

Papers in PDF format

Papers in PDF format

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

group focuses on management issues versus technical issues. [Fig. 2] provides an overview of this measurement from the<br />

three focal groups <strong>in</strong> this study. Whereas last year’s group had an almost 50% split <strong>in</strong> terms of management versus<br />

technical issues, this year’s groups dropped to 44% and 31% <strong>in</strong> the number of focus discussions on technical issues. This<br />

significant decrease <strong>in</strong> technical focus must be exam<strong>in</strong>ed to determ<strong>in</strong>e the answer one of two questions: 1) Is the decrease a<br />

result of <strong>in</strong>creas<strong>in</strong>g communications on the roles and responsibilities with<strong>in</strong> the consortia; or 2) is the decrease an <strong>in</strong>dication<br />

of greater friction with<strong>in</strong> the teams which is surfac<strong>in</strong>g through electronic mail messages? This question sets the stage for<br />

the next phase data analysis.<br />

TIMELINE FOCUS<br />

30<br />

25<br />

20<br />

15<br />

10<br />

5<br />

0<br />

Grp 1 Grp 2 Base<br />

Grp<br />

Management<br />

Technical<br />

Figure 2: Comparison of Management and Technical<br />

Communications<br />

The f<strong>in</strong>al area of focus is a timel<strong>in</strong>e analysis result<strong>in</strong>g from the management and technical discussions. In an optimum<br />

situation, teams should rapidly decide on a management organization and then focus the majority of their efforts on solv<strong>in</strong>g<br />

technical issues [Bounds, et al. 1994]. However, the personalities and <strong>in</strong>dividual goals evident with<strong>in</strong> every <strong>in</strong>terdiscipl<strong>in</strong>ary<br />

team cannot be overlooked [Katzenbach and Smith 1993]. These external issues constantly create friction with<strong>in</strong> project<br />

teams [Krackhardt and Hanson 1993]. The research team established an hypothesis that the <strong>in</strong>troduction of the Web<br />

communications center would reduce the time required to focus on management issues. [Fig. 3] illustrates the actual results<br />

from the timel<strong>in</strong>e study. As the figure illustrates, the hypothesis did not materialize. In reality, the management<br />

discussions cont<strong>in</strong>ued throughout the project while the technical discussions dropped off well before the management<br />

discussions ended. This discrepancy represents a notable divergence from the <strong>in</strong>itial project expectations and sets the stage<br />

for critical follow-up study.<br />

10<br />

8<br />

6<br />

4<br />

2<br />

0<br />

Week<br />

1<br />

Week<br />

2<br />

Week<br />

3<br />

Management<br />

Technical<br />

Figure 3: Analysis of management vs. technical<br />

discussions <strong>in</strong> virtual team <strong>in</strong>teractions.

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

Saved successfully!

Ooh no, something went wrong!