Collocation importance
Agile Leadership

Collocation importance

Sitting in an open space office encourages regular interactions between people very useful for collaborative works.
Read more
Get PDF
Tags
Agile collocate collocation collocation definition collocation examples collocation meaning Leadership Scrum Teams
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

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
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.