> From: Jeff Grigg [mailto:[EMAIL PROTECTED]
> --- "Steve Bate" <[EMAIL PROTECTED]> wrote:
> > I'm not understanding your association of categorization and
> > dependency. Categories don't necessarily create workflow
> > dependencies [...]
>
> If only Joe is allowed to update the database, and only Sue is
> allowed to paint screens, then when Sam signs up to implement some
> business functionality that requires database and screen changes, it
> won't be finished until both Joe and Sue do their part. It may not
> be possible to start some of the work or testing until Joe and/or Sue
> do their part.
>
> If every member of the team can, in theory, perform any work task,
> then Sam, with the help of a few others, can do the entire job. Sam
> would not sit idle, waiting for someone else to complete work that he
> needs done.
This is an example where even in the theoretical scenario there are
dependencies, independent of categorization. Sam will need help from
Joe and Sue. Some other developer may also need help from Joe and/or
Sue. Someone will likely have to wait to be helped because of these
dependencies on relatively scarce resources (Joe's database expertise
and Sue's GUI expertise).
I think it's a very good idea to minimize dependencies in project
development. If, in some specific situation, categorization leads
to excessive dependencies then I believe that's a problem. One thing
I like about XP is the focus on reducing skill-related dependencies.
Steve
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/
