Re: agile/xp question (formal analysis)
From: AndyW (foo__at_bar_no_email.com)
Date: 11/28/04
- Next message: Laurent Bossavit: "Re: agile/xp question (formal analysis)"
- Previous message: Laurent Bossavit: "Re: Thought Before Action."
- In reply to: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Next in thread: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Reply: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 28 Nov 2004 22:37:01 +1200
On Sat, 27 Nov 2004 22:42:59 -0500, Ronald E Jeffries
<ronjeffries@acm.org> wrote:
>On Sun, 28 Nov 2004 10:53:52 +1200, AndyW <foo_@bar_no_email.com>
>wrote:
>
>>>Then if an average inhouse team of six can produce three to six new
>>>working tested features in a week, why couldn't a bunch of parallel
>>>teams do that?
>>
>>Because of all the extra work that needs to be done on top of that.
>>Both in technical and non-technical.
>
>What is that extra work, and why can't it be substantially reduced or
>eliminated? There are Scrum of Scrum teams working all over, reporting
>very agile results in large projects.
>
>I see that people believe it's not possible to be agile in such
>situations, yet I see other people doing it, and I don't see any deep
>reasons why more projects couldn't be.
>
Its called management overhead, communications overhead and
development overhead (things like developing infrastructure and the
like).
- Next message: Laurent Bossavit: "Re: agile/xp question (formal analysis)"
- Previous message: Laurent Bossavit: "Re: Thought Before Action."
- In reply to: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Next in thread: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Reply: Ronald E Jeffries: "Re: agile/xp question (formal analysis)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|