Introduction |
|
1 | (8) |
|
Why Do Many Collaborative Ventures Fail? |
|
|
|
|
|
What Do We Mean by Virtual Collaboration? |
|
|
|
Today's Virtual Collaborative Project Characteristics |
|
|
|
Why Should You Care about Virtual Operations? |
|
|
|
Why Was This Book Written? |
|
|
|
Specifically, What Problems Will This Book Help Solve? |
|
|
|
A Note about the Recommendations in This Book |
|
|
|
What Does The Future Hold? |
|
|
|
|
An Overview and Roadmap for Busy Project Leaders |
|
9 | (220) |
|
The High Level Virtual Project Organization |
|
|
|
About Virtual Project Leadership Struggles |
|
|
|
Conflict and Informal Activities |
|
|
|
The Virtual Culture - A Practical and Affordable |
|
|
|
|
|
Architecture, Work Split, and Tasking |
|
|
|
|
|
Competing Virtual Project Infrastructure Visions |
|
|
|
Global Component Criteria |
|
|
|
How to Leverage Your Teammates' Strengths while |
|
|
|
Managing the Integration Risk |
|
|
|
|
|
Lower Level Virtual Project Organization |
|
|
|
Virtual Project Organizations and Integrated Product Teams (IPTs) |
|
|
|
|
|
Test the Operation Concept of the Virtual Organization |
|
|
|
Is It Possible for Conflict and Common Vision to Coexist? |
|
|
|
|
|
|
|
|
|
Why Do We Need a Virtual Culture? |
|
|
|
What Do We Mean by a Virtual Culture? |
|
|
|
Informal Activities and the Virtual World |
|
|
|
The Written Word in the Virtual World |
|
|
|
|
|
Traditional Collocated Engineering from the Inside |
|
|
29 | (22) |
|
How Does an Engineer Become Effective at His Job? |
|
|
|
The Role of Informal Communication |
|
|
|
Organizational Subcultures |
|
|
|
Engineering Effectiveness and Subcultures |
|
|
|
|
|
Large and Small Engineering Organizations |
|
|
|
|
|
|
|
Architecture, User Interface, and Databases |
|
|
|
|
|
The Push-Pull Organizational Tale |
|
|
|
Common Key Characteristic of Successful Organizations |
|
|
|
Organizational Expectations |
|
|
|
Task Assignment Records (TARs) |
|
|
|
|
|
Formality and Informality |
|
|
|
|
|
Is it Easy to Physically Distribute a Mature Process? |
|
|
|
What Makes a Mature Process Mature? |
|
|
|
|
|
|
|
The Tale of Two Cultures (The Schizophrenic Project) |
|
|
51 | (24) |
|
|
|
Observations on the Effect of Personal Experience |
|
|
|
Culture, Adversity, and Communication |
|
|
|
Hindrances to Effective Virtual Team Communication |
|
|
|
|
|
|
|
Distance + Competition + Differing Experiences = Rumors + Communication Breakdown |
|
|
|
Why Conflict Resolution Often Fails on Virtual Projects |
|
|
|
|
|
A Fundamental Dilemma Facing Virtual Collaboration |
|
|
|
The Schizophrenic Project Memory |
|
|
|
The Integrated Project Memory |
|
|
|
The Adjacent Cubicle Head Popping (ACHP) Tale |
|
|
|
About the Creative Design Process |
|
|
|
|
|
Relationship to Past Experience |
|
|
|
Incubation and Assimilation |
|
|
|
Virtual Collaboration and the Creative Process |
|
|
|
Collocation at the Right Time |
|
|
|
An Implementation of a Virtual Culture |
|
|
|
|
|
|
|
|
|
Remote Task Management: Am I Doing What You Think I'm Doing? |
|
|
75 | (18) |
|
|
|
Causes of Task Miscommunication |
|
|
|
Why Architecture is Critical to Effective Remote Tasking |
|
|
|
|
|
An Organizational View of Architecture |
|
|
|
A Different Organizational View of Architecture |
|
|
|
Relationship between Organizational Structure and Task Assignments |
|
|
|
Evolution of ``Local Meaning'' of Terms and Its Relationship to Organizational Responsibilities |
|
|
|
Relationship among Critical Issues, Risk, and Past Experience |
|
|
|
Use Architecture to Aid Task Communication |
|
|
|
Is Architecture the Total Solution? |
|
|
|
The Database Process Tale |
|
|
|
|
|
|
|
Charlie's Reliance on the Informal Side |
|
|
|
Relationship between Charlie's System and the Organizational System |
|
|
|
Fundamentals, Strongly Held Beliefs, and Risk |
|
|
|
|
|
Use Task Assignment Records (TARs) |
|
|
|
|
|
|
|
|
|
An Implementation of a Virtual Culture: The Rapid Filtered Project Memory (RFPM) |
|
|
93 | (20) |
|
RFPM Construction and Maintenance Guidance |
|
|
|
|
|
Critical Issues and Agreed To Strategies |
|
|
|
Architecture/System Design Guidance |
|
|
|
|
|
|
|
Why Do We Need Increased Formality on Task Assignment Definitions? |
|
|
|
What Is A CPDM and How Can It Help? |
|
|
|
|
|
Component-Product Relationship to Task Assignments |
|
|
|
Component-Products and Deliverable-Products |
|
|
|
The CPDM and Project/Corporate Procedures |
|
|
|
The CPDM as a Bridge from Corporate Procedures to Project-Specific Information |
|
|
|
Examples of Virtual Project Pitfall Avoidance through the Use of a CPDM |
|
|
|
How to Avoid Pitfall 1 --- Miscommunication Due to Ambiguous Terminology |
|
|
|
Use of Standards and Published Methodologies |
|
|
|
Using the CPDM to Aid Task Communication |
|
|
|
How the CPDM Helps Resolve Miscommunication |
|
|
|
How to Avoid Pitfall 2 --- Miscommunication Due to Unclear Process |
|
|
|
Enhanced Task Assignment Description |
|
|
|
Integration of Systems and Software |
|
|
|
Flexibility of End-Product Deliverables |
|
|
|
|
|
|
|
|
|
Team Communication: The Rules of the Game Have Changed |
|
|
113 | (30) |
|
|
|
|
|
Categorizing Team Information |
|
|
|
|
|
Virtual Projects and Multiple Team Allegiances |
|
|
|
Wearing Multiple Team Hats and Setting The Right Priorities |
|
|
|
Are We Motivating Our Remote Team Members to Be Real Team Players |
|
|
|
Are We Asking Too Much of Our Remote Temmates? |
|
|
|
Sensitivity to Information Sharing and Team Loyalty |
|
|
|
Back to Our Tale --- The Predicament |
|
|
|
Self-Directed Teams, Tiger Teams, and Control-Oriented Managers |
|
|
|
|
|
|
|
The Quiet Sign --- A Warning Sign |
|
|
|
|
|
``Having a Say Differs from Having a Vote'' |
|
|
|
|
|
How to Effectively Use Virtual Communication Technologies |
|
|
|
|
|
The Tale of the Missing Teammate |
|
|
|
A Fundamental Difference between E-Mail and Direct Personal Contact |
|
|
|
|
|
|
|
Ramifications of E-Mail Flooding |
|
|
|
|
|
Recommendation --- Treat Lack of Trust as a Virtual Project Risk |
|
|
|
|
|
The ``Old Habits Die Hard'' Tale |
|
|
|
Keeping Aware of the Needs of Your Full Team |
|
|
|
Small Things and Big Things |
|
|
|
Rules for Effective Virtual Operations |
|
|
|
Recommended Rules and Maintenance of an RFPM |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Integration Side: It Isn't a Seamless World Just Yet |
|
|
143 | (22) |
|
The Document Production Disaster Tale |
|
|
|
Stepping Back --- The Good News |
|
|
|
|
|
|
|
Task Communication and Acceptance |
|
|
|
|
|
The Tale of ``Down Here, and Up There'' |
|
|
|
|
|
The ``Let's Use the Most Mature Process Available'' Pitfall |
|
|
|
Examples of Difficulties Transporting Mature Processes |
|
|
|
The Multiple Site Process Dilemma |
|
|
|
|
|
How to Make Effective Work Split Decisions |
|
|
|
|
|
Architecture Considerations (Subsystems) |
|
|
|
|
|
Global Component Recommendations |
|
|
|
What is a Global Component? |
|
|
|
Advantages of Using Global Components |
|
|
|
Does the Global Component Approach Contradict the Virtual Concept? |
|
|
|
Terminology Clarification |
|
|
|
Three Key Characteristics of the Global Component |
|
|
|
Complete Life Cycle Product |
|
|
|
|
|
Process Freedom Line Support |
|
|
|
Analysis and Recommendations |
|
|
|
|
|
|
|
Clear and Singular Assignment of Responsibility and Accountability |
|
|
|
|
|
|
|
|
|
|
|
|
|
Eight Practical and Affordable Steps to Set Up and Maintain a Successful Virtual Project |
|
|
165 | (50) |
|
Eleven Virtual Project Pitfalls |
|
|
|
Introduction to the Eight (8)-Step Plan |
|
|
|
How to Use the Material in this Chapter |
|
|
|
|
|
|
|
Execution-Phase Warning Signs |
|
|
|
|
|
Establish the High Level Project Organization |
|
|
|
|
|
Select the Best and Train the Rest |
|
|
|
Hierarchical and Roving Leaders |
|
|
|
Develop Charters with Clearly Defined Responsibilities |
|
|
|
|
|
|
|
Establish Approach (Subsystem, Phase, Other) |
|
|
|
Establish Initial System Architecture |
|
|
|
Political Pressure on the Architecture Contractor |
|
|
|
Skill and Experience Required during Front-End Stage |
|
|
|
Capturing and Crisply Communicating the Archicture |
|
|
|
Establish CPDM --- A Bridge from Architecture to Subsystems |
|
|
|
Establish Global Component Criteria |
|
|
|
What Skills Do Personnel Assigned to Develop the CPDM and Global Component Criteria Need? |
|
|
|
Relationships among CPDM, Work Split, and Tasking Risk |
|
|
|
|
|
Delaying the Definition of Work Split for the Wrong Reasons |
|
|
|
|
|
|
|
|
|
|
|
Special Tasks: Infrastructure and Project Rules |
|
|
|
What is Infrastructure and How Do I Determine My Project Needs? |
|
|
|
Four Key Products for Analysis |
|
|
|
|
|
|
|
What Should You Do When Your Infrastructure Won't Support Your Plan? |
|
|
|
Project Rules --- Communicating the Lessons |
|
|
|
Establishing the Third Level of the Organization |
|
|
|
|
|
Cultural Differences in Approaches to Detailed Planning |
|
|
|
Architecture's Relationship to Leadership's Common Vision and Trust |
|
|
|
A Closer Look at Three Prerequisite Tasks |
|
|
|
|
|
|
|
Testing the Operation Concept of the Project Organization |
|
|
|
Task Direction --- When Roving Leaders and Hierarchical Leaders Collide |
|
|
|
Task Management --- A Strict vs. Integrated Approach |
|
|
|
Cross-Site or Cross-Organizational Interactions --- Using a Checklist |
|
|
|
Integrated Engineering Responsibilities --- Using Checklist |
|
|
|
Customer Communication --- Establishing a Well-Defined Policy |
|
|
|
Execution Phase Warning Signs |
|
|
|
Execution with a Focus on Conflict Management |
|
|
|
The Non-Technical Side of Project Execution |
|
|
|
|
|
A Sign of Healthy Conflict |
|
|
|
Key Warning Signs of Destructive Conflict |
|
|
|
|
|
Non-Compliance with Team Information Sharing Policy |
|
|
|
``They're Out to Steal Our Business'' Message |
|
|
|
|
|
|
|
Warnings Signs of Non-Compliance with Preventative Maintenance Techniques |
|
|
|
|
|
|
|
|
|
|
215 | (14) |
|
|
|
Summarizing Our Approach to the Collaborative Challenge |
|
|
|
A Final Note on the Informal Side |
|
|
|
Virtual Project Strategies of the Future |
|
|
|
|
|
Summarizing the Virtual Culture Concept |
|
|
|
Sample Products from a Virtual Culture |
|
|
|
The Philosophy of a Virtual Culture |
|
|
|
Virtual Cultures of the Future |
|
|
|
|
|
|
|
|
|
The Virtual Project Management Framework |
|
|
|
|
|
The Virtual Culture Foundation Layer |
|
|
|
The Virtual Culture Intermediate Layer |
|
|
|
The Virtual Culture Dynamic Layer |
|
|
|
|
|
|
Appendix A Component-Product Development Matrix (CPDM) Implementation Guidance |
|
229 | (6) |
Appendix B Definitions |
|
235 | (4) |
Appendix C Templates |
|
239 | (4) |
Appendix D Forms |
|
243 | (6) |
Appendix E Sample Forms |
|
249 | (4) |
Appendix F Criteria |
|
253 | (4) |
Appendix G Warning Signs |
|
257 | (2) |
Appendix H Checklists |
|
259 | (8) |
Appendix I Rules |
|
267 | (2) |
Appendix J Frequently Asked Questions |
|
269 | (22) |
Appendix K The ``Big Picture'' Views |
|
291 | (12) |
Appendix L Synopsis of 34 Insights and 50 Solutions |
|
303 | (6) |
Index |
|
309 | |