rachelclairedavies
2004-10-16 14:12:08 UTC
In this Sit Together practice, do you include the wider project team
including other roles such as Customer, Testers and perhaps even
Project Manager? Or does this only apply to Developers?
Rachel
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xpbookdiscussiongroup/
<*> To unsubscribe from this group, send an email to:
xpbookdiscussiongroup-unsubscribe-***@public.gmane.org
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
including other roles such as Customer, Testers and perhaps even
Project Manager? Or does this only apply to Developers?
Rachel
Develop in an open space big enough for the whole team. Meet the
need for privacy and "owned" space by having small private spaces
nearby or by limiting work hours so team members can get their
privacy needs met elsewhere.
I was called to consult at a floundering project on the outskirts
ofneed for privacy and "owned" space by having small private spaces
nearby or by limiting work hours so team members can get their
privacy needs met elsewhere.
I was called to consult at a floundering project on the outskirts
Chicago. Why the project was floundering was a mystery, because
theteam consisted of the best technical talent in the company. I
walkedfrom cubicle to cubicle trying to figure out what was wrong with
their computer program.
After a couple of days, it struck me: I was walking a lot. The
senior people of course had corner offices, one in each corner of
atheir computer program.
After a couple of days, it struck me: I was walking a lot. The
senior people of course had corner offices, one in each corner of
floor of a substantial building. The team interacted only a few
minutes each day. I suggested that they find a place to sit
together. When I returned a month later, the project was humming
along. The only space they could find to sit together was in the
machine room. They were spending four to five hours a day in a
cold,minutes each day. I suggested that they find a place to sit
together. When I returned a month later, the project was humming
along. The only space they could find to sit together was in the
machine room. They were spending four to five hours a day in a
drafty, noisy room; but they were happy because they were
successful.I took two lessons from that experience. One is that no matter
whatthe client says the problem is, it is always a people problem.
Technical fixes alone are not enough. The other lesson I took was
how important it is to sit together, to communicate with all our
senses.
You can creep up on sitting together, if necessary. Put a
comfortable chair in your cubicle to encourage conversation. Spend
half a day programming in a conference room. Ask for a conference
room for a one-week trial of a more open workspace. All of these
areTechnical fixes alone are not enough. The other lesson I took was
how important it is to sit together, to communicate with all our
senses.
You can creep up on sitting together, if necessary. Put a
comfortable chair in your cubicle to encourage conversation. Spend
half a day programming in a conference room. Ask for a conference
room for a one-week trial of a more open workspace. All of these
steps towards finding a workspace that is effective for your team.
Tearing down the cubicle walls is not the place to start with XP.
IfTearing down the cubicle walls is not the place to start with XP.
the team members' sense of safety is tied to having their own
littlespace, removing that sense of safety before replacing it with the
safety of shared accomplishment is likely to produce resentment
andsafety of shared accomplishment is likely to produce resentment
resistance. With a little encouragement, teams can shape their own
space. A team that knows that physical proximity enhances
communication and that has learned the value of communication will
put two and two together and begin to open up their own space.
Does the practice of sitting together mean that multisite teams
can't "do XP"? Chapter 21, "Purity", explores this question in
morespace. A team that knows that physical proximity enhances
communication and that has learned the value of communication will
put two and two together and begin to open up their own space.
Does the practice of sitting together mean that multisite teams
can't "do XP"? Chapter 21, "Purity", explores this question in
depth; but the simple answer is no, teams can be distributed and
doXP. Practices are theories, predictions. "Sit Together" predicts
that the more face time you have, the more humane and productive
thethat the more face time you have, the more humane and productive
project. If you have a multisite project and everything is going
well, keep doing what you're doing. If you have problems, think
about ways to sit together more, even if it means traveling.
Copyright (c) 2004, Kent Beck and Cynthia Andres
------------------------ Yahoo! Groups Sponsor --------------------~-->well, keep doing what you're doing. If you have problems, think
about ways to sit together more, even if it means traveling.
Copyright (c) 2004, Kent Beck and Cynthia Andres
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/xpbookdiscussiongroup/
<*> To unsubscribe from this group, send an email to:
xpbookdiscussiongroup-unsubscribe-***@public.gmane.org
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/