Collocation importance

Sitting in an open space office encourages regular interactions between people very useful for collaborative works.
Read more
Article

Collocation


Collocation – Sitting in an open space office encourages regular interactions between people very useful for collaborative works. You can see other’s activities and ask for help if needed.


Working by the same workstation. Collocation

Working by the same workstation. Direct question and answers. Very little work, time, and energy spent.


Separate workstations next to each other. Collocation

Separate workstations next to each other. Peripheral vision usage, easy to interact. Not much work, time, or energy spent.


Opposite sides of a room. Collocation

Opposite sides of a room. Availability to answer can be seen, easier interaction. Little work, time, or energy spent.


Adjacent workspaces with a wall in between.

Adjacent workspaces with a wall in between. Getting up and peeking around the doorframe to check the availability.


Different floors or adjacent buildings.

Different floors or adjacent buildings. The need of going to another office with an uncertain presence can lead to the loss of motivation. The lost opportunity cost starts to mount.


Different cities.

Different cities, (maybe different time zones). Less efficient interaction, poorer communication channels. More energy and more time, to achieve the same communication result.


Resources
Alistair Cockburn: Agile Software Development martinfowler.com martinfowler.com Agile Software Development The Cooperative Game

Similar posters

Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.
Little's law
Little's law Little’s Law is a theorem for queuing systems. It determines the average number of items in a stationary queuing system
User Story Creation
User Story Creation Creating a User Story is a continuous process based on the 3Cs phases, supported by INVEST, 5Ws, and the Definition of Done.
Radical Candor
Radical Candor Radical Candor is a framework describing four different behaviors. In order to become Radically Candid you need to understand all four types.
GSD / Get Stuff Done Whee
GSD / Get Stuff Done Whee Get Stuff Done Wheel is a framework for aligning and guiding the work of a team. It allows teams to deliver remarkable results more quickly
AIDA Model
AIDA Model The AIDA model is a model, where a persona moves through a series of steps to make a purchase decision, used in marketing, sales, planning...