Re: agile/xp question (formal analysis)

From: AndyW (foo__at_bar_no_email.com)
Date: 11/27/04 

Date: Sat, 27 Nov 2004 12:42:12 +1200

On Fri, 26 Nov 2004 17:23:52 -0500, Ronald E Jeffries
<ronjeffries@acm.org> wrote:

>On Sat, 27 Nov 2004 09:23:41 +1200, AndyW <foo_@bar_no_email.com>
>wrote:
>
>>Last one was a small $125 million CSM package for a telco. I think the
>>initial feature set took about 14 months to achieve before the first
>>end-to-end run was performed. Three main development teams included
>>those working on the framework (included IPC, RPC and IP protocol
>>teams, as well as a couple of Database teams), Platform people, UI
>>guys, and Application dev teams of which there were three split up
>>into the 3 main teams of 25 people each. About 300 or so people in
>>all - although a fair percentage worked in different countries and may
>>have been part of implementation and sales teams.
>>
>>That would be probably the smallest.
>
>Well, I certainly wouldn't know how to do anything that big, though
>I'd not be daunted too much by a 25 person team.
>
>But I don't see why nothing could be done end to end /in principle/
>though of course once you split out separate framework from
>application, you're pretty much screwed for incremental delivery.

Not quite - what tends to happen is you have many teams each working
on a feature or some componant of the application. Each team would be
following a methodology (usually the same across teams), so in this
light you could perform agile/mini waterfall.

Teams work in parallel to each other, so the size and speed is
dependant on the number of teams you have working at any given time.
Once a team finishes a feature it moves on to the next one.

At this level a team is defined as maybe 20 or 30 people and a feature
would be some major component of architecture - for example the
database system, the framework, and application business objects such
as the customer services object, product definition object etc.

Think of one of these teams as being your 'average' inhouse
development team for a small project. Each may be split up into
sub-teams (of 6 people) with a line manager and there will be a couple
of BAs a team manager, an architect etc.

Relevant Pages

  • Re: Using windows application project on a mobile device
    ... Binary Serialization isn't supported out of the box by the .NET Compact ... If your application relies heavily upon this feature you may need ... present on the .NET Compact Framework (but won't affect how the resultant ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Cant double click joins in VFP8 view designer
    ... I've used another framework for a few ... tracing through the code of the framework to see why this or that feature ... We currently use StoneField on an app that has 100 tables, ... They don't have a "visual" Designer, but that's not why the original view ...
    (microsoft.public.fox.programmer.exchange)
  • Re: Rule-based AI in C
    ... Making rules dependent on other rules is indeed ... consider the minimal feature set a virtue. ... "framework" and fit ones code/ideas into its state of operation rather ... Because when writing your own implementation, ...
    (rec.games.roguelike.development)
  • Re: Terminal Services
    ... the system pagefile is a feature of the OS. ... GDI is a framework that can be used by applications to provide ... the OS does not create windows for the application, ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Rule-based AI in C
    ... Making rules dependent on other rules is indeed ... As I wrote in the original post, ... consider the minimal feature set a virtue. ... "framework" and fit ones code/ideas into its state of operation rather ...
    (rec.games.roguelike.development)