Search this site
Embedded Files
Published Patterns
  • Home
  • A Vision
  • Book Outline
    • Acknowledgments
    • Beedle Dedication
    • Beyond the Core
    • Composing Your Own Pattern Language
    • Confidence Star Summary
    • Dedications
    • History of the Patterns
    • Introduction
    • Patlets
    • Pattern Name Aliases
    • Picture Credits
    • Preface
    • Product Organization Pattern Language
    • Product Organization Pattern Language
    • Product Owner’s Note
    • The Core Patterns in Brief
    • The Future of the Patterns
    • Value Stream Pattern Language
  • External Patterns
    • Apprenticeship
    • Code Ownership
    • Community of Trust
    • Compensate Success
    • Completion Headroom
    • Day Care
    • Developer Controls Process
    • Developing in Pairs
    • Distribute Work Evenly
    • Do Food
    • Domain Expertise in Roles
    • Don’t Interrupt an Interrupt
    • Eat Your Own Dog Food
    • Engage Quality Assurance
    • Face-to-Face Before Working Remotely
    • Failed Project Wake
    • Firewall
    • Gatekeeper
    • Informal Labor Plan
    • Interrupts Unjam Blocking
    • Matron Role
    • Moderate Truck Number
    • Named Stable Bases
    • Organization Follows Market
    • Patron Role
    • Producer Roles
    • Programming Episodes
    • Recommitment Meeting
    • Sacrifice One Person
    • Self-Selecting Team
    • Size the Organization
    • Smoke-Filled Room
    • Solo Virtuoso
    • Someone Always Makes Progress
    • Stand-Up Meeting
    • Surrogate Customer
    • Take No Small Slips
    • Team per Task
    • Team Pride
    • The Water Cooler
    • Unity of Purpose
    • Wise Fool
    • Work Flows Inward
  • Product Organization Pattern Language
    • A Scaling Sequence
    • A Sequence Of Scaling
    • Birds of a Feather
    • Chief Product Owner
    • Conway's Law
    • Development Partnership
    • Development Team
      • Autonomous Team
      • Collocated Team
      • Cross-Functional Team
      • Developer-Ordered Work Plan
      • Distribute Work Evenly
      • Fertile Soil
      • Oyatsu Jinja
      • Remove the Shade
      • Self-Organizing Team
      • Small Teams
      • Stable Teams
      • Swarming: One-Piece Continuous Flow
      • Team Pulse
      • Team Sprint
    • Domain Expertise in Roles
    • Emergency Procedure
    • Illegitimus Non Interruptus
    • Improvement Community
    • Kaizen and Kaikaku
    • Kaizen Pulse
    • Leading Team
    • MetaScrum
    • Mitosis
    • Norms of Conduct
    • Organizational Sprint Pulse
    • Pop the Happy Bubble
    • Product Owner
    • Product Owner Team
    • Product Pride
    • Scrum of Scrums
    • Scrum Team
    • ScrumMaster
    • Scrumming the Scrum
    • Small Red Phone
    • Sprint Pulse
    • The Mist
  • Scrum Core Pattern Language
    • Backlog Grooming Meeting
    • Backlog Refinement Meeting
    • Daily Scrum
    • Development Team
    • Product Backlog
    • Product Owner
    • Scrum Team
    • ScrumMaster
    • Sprint
    • Sprint Backlog
    • Sprint Burndown
    • Sprint Planning Meeting
    • Sprint Retrospective
    • Sprint Review
  • Sequences
    • A Project Language of Highly Effective Teams
    • Product Backlog Sequence
    • Product Organization Sequence
    • Project Languages
    • Value Stream Sequence
    • Your Own Pattern Language
  • Unlinked Patterns
    • Impediment List
    • Involve the Managers
    • Involve the Managers - Redux
  • Value Stream
    • Daily Clean Code
    • Definition of Done
    • Estimation Points
      • Accountable Estimates
      • Pigs Estimate
      • Updated Velocity
      • Yesterday's Weather
    • Fixed Work
    • Good Housekeeping
    • Greatest Value
    • Information Radiator
      • Scrum Board
      • Sprint Burndown Chart
    • Notes on Velocity
    • Product Backlog
      • Aggregate Velocity
      • Change for Free
      • Definition of Ready
      • Enabling Specification
      • Estimation Range
      • Fixed-Date PBI
      • Granularity Gradient
      • High Value First
      • Money For Nothing
      • Product Backlog Item
      • Rechunked PBIs
      • Refined Product Backlog
      • ROI-Ordered Backlog
      • Specialized Velocities
      • Vacation PBI
      • Value and ROI
    • Product Roadmap
    • Product Wake
    • Production Episode
    • Regular Product Increment
    • Release Plan
      • Product Roadmap
      • Release Range
      • Release Staging Layers
    • Responsive Deployment
    • Rhythms: Patterns of Time
    • Running Average Velocity
    • Set-Based Design
    • Small Items
    • Sprint
      • Daily Scrum
        • ScrumMaster Incognito
      • Follow the Moon
      • Sprint Retrospective
      • Stop the Line
    • Sprint Backlog
      • Burndown Chart
      • Dependencies First
      • Developer-Ordered Work Plan
      • Small Items
      • Sprint Backlog Item
    • Sprint Goal
    • Sprint Planning
    • Sprint Review
    • Team Sprint
    • The Spirit of the Game
    • Value Areas
    • Value Stream Fork
    • Visible Status
    • Vision
    • Whack the Mole
  • Organizational Patterns of Agile Software Development
    • BookOutline
      • Appendices
        • Bibliography
        • ParkingLot
        • PhotoCredits
        • SummaryPatlets
      • CaseStudies
        • AHyperproductiveTelecommunicationsDevelopmentTeam
        • BorlandQuattroProForWindows
      • FoundationsAndHistory
        • AnthropologicalFoundations
          • BeyondProcessToStructureAndValues
          • DistillingThePatterns
          • PatternsInAnthropology
          • RolesAndCommunication
          • RolesAndCommunications
          • SocialNetworkAnalysis
          • CRCCardsAndRoles
          • ScatterplotsAndPatterns
          • SocialNetworkTheoryFoundations
        • OrganizationalPrinciples
          • PiecemealGrowth
          • PrimingTheOrganizationForChange
          • SomeGeneralRules
          • BuildingOnTheSolidCore
          • DissonancePrecedesResolution
          • ItDependsOnTheContextOfTheOrganization
          • ItDependsOnYourRoleInYourOrganization
          • MakeLoveNotWar
          • OrganizationalPatternsAreInspirationRatherThanPrescription
          • OrganizationalPatternsAreUsedByGroupsRatherThanIndividuals
          • PeopleAreLessPredictableThanCode
          • StabilityAndCrisisManagement
          • TeamBuilding
          • TeamBurnout
          • TheOpenClosedPrincipleOfTeams
          • TheRoleOfManagement
      • HistoryAndIntroduction
        • HowThePatternsCameToUs
          • CreatingSequences
          • GatheringOrganizationalData
          • HistoryAndRelatedWork
          • AnalyzingRolesAndRelationships
          • IntrospectionAndAnalysisOfOrganizations
          • IntrospectionInAndAnalysisOfOrganizations
          • ShortcomingsOfStateOfTheArt
          • TheCRC-CardMethodology
        • HowToUseThisBook
          • ApplyingThePatterns
          • ReadingThePatterns
          • UpdatingThePatterns
          • WhoShouldUseThisBook
      • PreFace
      • ThePatternLanguages
        • OrganizationConstructionPatterns
          • OrganizationalStylePatternLanguage
          • PeopleAndCodePatternLanguage
          • ArchitectAlsoImplements
          • ArchitectControlsProduct
          • ArchitectureTeam
          • CodeOwnership
          • ConwaysLaw
          • CouplingDecreasesLatency
          • DeCoupleStages
          • DeployAlongTheGrain
          • DistributeWorkEvenly
          • DivideAndConquer
          • FaceToFaceBeforeWorkingRemotely
          • FeatureAssignment
          • FewRoles
          • FormFollowsFunction
          • FunctionOwnerAndComponentOwner
          • GenericsAndSpecifics
          • HallwayChatter
          • HierarchyOfFactories
          • HubSpokeAndRim
          • LockEmUpTogether
          • LooseInterfaces
          • MoveResponsibilities
          • OrganizationFollowsLocation
          • OrganizationFollowsMarket
          • ParserBuilder
          • PrivateVersioning
          • ProducerRoles
          • ProducersInTheMiddle
          • ResponsibilitiesEngage
          • ShapingCirculationRealms
          • SmokeFilledRoom
          • StableRoles
          • StandardsLinkingLocations
          • StandUpMeeting
          • SubclassPerTeam
          • TheWaterCooler
          • ThreeToSevenHelpersPerRole
          • UpsideDownMatrixManagement
          • VariationBehindInterface
        • OrganizationDesignPatterns
          • PiecemealGrowthPatternLanguage
          • ProjectManagementPatternLanguage
          • ApplicationDesignIsBoundedByTestDesign
          • ApprenticeShip
          • BuildPrototypes
          • CommunityOfTrust
          • CompensateSuccess
          • CompletionHeadroom
          • DayCare
          • DeveloperControlsProcess
          • DevelopingInPairs
          • DevelopmentEpisode
          • DiverseGroups
          • DomainExpertiseInRoles
          • DontInterruptAnInterrupt
          • EngageCustomers
          • EngageQualityAssurance
          • FailedProjectWake
          • FireWalls
          • GateKeeper
          • GetOnWithIt
          • GroupValidation
          • HolisticDiversity
          • ImpliedRequirements
          • IncrementalIntegration
          • InformalLaborPlan
          • InterruptsUnjamBlocking
          • LegendRole
          • MatronRole
          • MercenaryAnalyst
          • ModerateTruckNumber
          • NamedStableBases
          • PatronRole
          • PhasingItIn
          • PrivateWorld
          • ProgrammingEpisode
          • PublicCharacter
          • RecommitmentMeeting
          • SacrificeOnePerson
          • ScenariosDefineProblem
          • SelfSelectingTeam
          • SizeTheOrganization
          • SizeTheSchedule
          • SkunkWorks
          • SoloVirtuoso
          • SomeoneAlwaysMakesProgress
          • SubsystemBySkill
          • SurrogateCustomer
          • TakeNoSmallSlips
          • TeamPerTask
          • TeamPride
          • UnityOfPurpose
          • WiseFool
          • WorkFlowsInward
          • WorkQueue
          • WorkSplit
    • CommonPatternLanguage
    • DiversityOfMembership
    • IndentationHint
    • OrganizationalPatterns
    • SkillMix
    • StartingPoints
    • TheCatalyst
    • ThoughtsWeaver
    • WorkAllocation
    • HistoryAndIntroduction
      • AnOverviewOfPatternsAndOrganizationalPatterns
        • OrganizationalPatternLanguages
        • WhatArePatternLanguages
        • WhatArePatterns
Published Patterns

Face To Face Before Working Remotely

Camp Carson, Colorado. Colonel Wilfrid M. Nlunt, the commanding officer shakes hands with Colonel Denetrius Xenos, military attache of the Greek ambassador to the United States — a face-to-face meeting before working remotely.

Designing a new aircraft is a big deal. A very big deal. It's very involved, very expensive, and pretty risky. It takes the coordinated efforts of many different teams. When the Boeing Corporation began work on the new 777 airplane, it brought everyone on the project together for a kickoff meeting. There were thousands of people, all together, to get the project off on the right foot. Fortunately, Boeing owns many large aircraft hangers, so it could accommodate a meeting of that size.

...market or personnel conditions sometimes require that a project be geographically distributed. In such cases, OrganizationFollowsLocation is used to partition the work. But even when the work is partitioned in this manner, it is a challenge to actually implement the partitioning effectively. It may look good on paper, but the real people will run into a host of difficulties as they work it out.

✥ ✥ ✥

The pull of local organizations is so strong that it can overwhelm common architecture, market, and social aspects of a project.

Geographic distance makes communication harder. Different time zones create logistical difficulties for conversations. The cultural differences that often go hand-in-hand with long-distance cooperative work are sometimes staggering. The obvious problem is finding common times, but there are more subtle forces at work. One project was split between the United States and England. Conference calls took place in the morning in the U.S., which was late afternoon in England. Consequently, the U.S. people were fresh, but their colleagues in England were winding down, ready to hit the local pub.

Difficulties in communication often weaken direct, effective communication paths, shunting communications to more indirect paths through the organization. Local leaders receive marching orders and pass them to their colleagues, but unintentionally add their own interpretation. Some may remember the children's game, "gossip" where a message is whispered from one player to another until it bears no resemblance to the original message.

Although partitioning the project along geographic lines is necessary it has the side effect of isolating one location from another. They must communicate at defined interfaces (see StandardsLinkingLocations), and this results in people working on these interfaces without being able to get to know the person at the other end. People naturally tend not to work as well with those they don't know. It's hard to work with someone who is no more than a remote keyboard or a faceless voice on the phone.

Therefore:

Begin a distributed project with a face-to-face meeting for everyone. This meeting should establish project unity, as well as give people a chance to get to know those they work with.

The meeting establishes unity by talking about project goals, intended markets, competitors, and the project architecture (important). (It isn't necessary that the architecture be nailed down yet; in fact, this can be a springboard for LockEmUpTogether.)

The social aspects of a meeting are vitally important. Betsy Hanes Perry notes, "It is vital to leave at least half of the on-site time as UnscheduledTime. This allows group members to have impromptu conversations with the people they're closely coupled to. If you don't provide time for these conversations, you will find that bathroom breaks stretch on forever, and that the visitors leave frustrated." Steve Berczuk adds: "At Kodak we once had a group meeting of everyone in the division, from every location. The agenda was packed so tightly that we never really got a chance to meet each other." These social interactions are one of the reasons that videoconferences are no substitute for the face-to-face meeting.

✥ ✥ ✥

Every organization needs a place to call "home". Hold the meeting in a place that is memorable because of its uniqueness, beauty, great food, or other memorable quality, so that the group can identify with that place and its good memories. Hold group activities at that place, beyond the drone of everyday business activities, that will make the place memorable.

In a large project, the prospect of an initial face-to-face meeting may be daunting. But the Boeing company brought thousands of people together at the inception of the 777 project. Of course, they do own a few planes...

The importance of this initial meeting should not be underestimated. For a distributed project, it may be the very best way to establish UnityOfPurpose. Furthermore, the social aspects of people getting to know each other go a long way toward resolving the tension between OrganizationFollowsLocation and StandardsLinkingLocations. It sets up an environment where you can do ShapingCirculationRealms successfully.

An initial meeting of everyone can easily be followed (often immediately) by a LockEmUpTogether architectural session.

It may not stop with a single meeting. You may find that regular "all hands" meetings are worth the transportation expenses.

Report abuse
Page details
Page updated
Report abuse
OSZAR »