> OK. I had heard that some of your teams work on specific projects
> and even have names relating to the project. I guess I was
> misinformed.
If the reason for the team being formed was a new project, it makes
sense for that team to be named after that project.
And when the customer puts things on hold, it makes sense to have
those people work on another team's cards.
And when another team needs help it makes sense to move some bodies
around.
And when people need a change, it makes sense to move some bodies
around. One person is thinking about changing teams on a monthly
basis. I think that would work out nicely. Others may want to stay
where they are for a year or more. I think that also works out nicely.
And when project X needs a lot of enchancements to project Y, which
project X depends on (my current project is built off of three others,
depends on two more, and depends on file transfer support from another
team entirely), it may be that project X does the work or it may be
that project Y does the work or it may be some other group entirely
who decides to have a mini-iteration with those cards.
These decisions are made by people instead of processes. People tend
to be a lot more flexible, creative, and knowledgeable than fixed
processes. They may use a process to guide them, but they use their
own intelligence to make sure the decision is the right one.
So sure, the teams are named after projects, but like the pirate's
code, it's more like a guideline...
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
