Skip to content

XP Practice: Sit Together

November 7, 2007 by Artem Marchenko

Sit Together practice is one of the simplest to define and sometimes one of the most difficult to implement in eXtreme Programming. It namely means co-locating the whole team in a single room often called "war room". The idea behind it is to stimulate the information exchange by making it simple to just turn to the colleague and ask. Encouraging free conversation leads to the much quicker information exchange as tacit knowledge is transferred by gestures, information and buzz around.

However, it has to be taken into account that forcing the team sit together, before it is ready for it can be dangerous and difficult. To be effective sitting together requires a significant level of trust and alignment of the work - it is much less irritating to be disrupted by a side talk on a relevant topic, than by something you have no interest in. Both trust and work alignment are usually developed in the course of agile software development, but takes time.

In order to leave some time for privacy and just for letting people to have some phone calls area XP teams often have several cubicles or small rooms that can be used, when needed.

Links

  • Sit Together by James Shore. From his book "The Art of Agile Development"

This page is a part of the Extreme Programming overview

About the Author: As the Editor-in-Chief for AgileSoftwareDevelopment.com, Artem is charged with overseeing the direction for content, advertising, and the overall management of the site. Nowadays in his day life, Artem is a product manager in a global telecommunication company where he leads the development of a product developed in extremely distributed environment. Artem has been applying Agile and researching Agile since 2005. Contact Artem

Comments

It is true that tacit

December 23, 2007 by Anonymous (not verified), 1 year 27 weeks ago
Comment id: 1408

It is true that tacit knowledge is very difficult to tame .
It always enjoys to roam freely from one mind to another mind through conversations and from one company to another company when employees change jobs.

I think the best way to tame the tacit knowledge would be to document the conversations on the fly when they happen through blogs , discussions , forums (within the enterprise).
This is where web 2.0 can tame the Tacit Knowledge which can prove a boon for the Agile Software development (where more emphasis is one Communication)

Also visit my blog and give your comments :
http://agilesoftwaredevelopment.com/forum/web-20-agile-development-tacit...

Simple tools such as blogs

December 26, 2007 by Artem, 1 year 27 weeks ago
Comment id: 1419

Simple tools such as blogs and wikis indeed help communication. However, I don't think that the tools can solve most of the problems. Wikis and blogs definitely help e.g. huge distributed team. However, usually it is more effective to just colocate a small team, than to wikify a big and distributed one;)

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Best of AgileSoftwareDevelopment.com