ScalingAgileProcesses

From SPA Wiki

Jump to: navigation, search

The following are brief notes scribbled down as the discussion took place, divided into the "Yes, they do" and "No, they don't" camps:

Yes, they scale:
  • To make bigger things, start with bigger pieces
  • Agility not just XP
  • Unproven either way, except by experience (which shows they do)
  • Small agile teams, combining to large scale
  • Different aspects of scale
  - Functionality
  - Development
  - Same code base
  - Abstract and meaningless?
  • XP process can be changed, adapted - once understood
  • If a process is to scale, it must be agile
  • Consider down-scaling as well as up-scaling
  • Melt down your Lego bricks
  • Management of big projects must be agile
  • Decouple building components from building end product: Product Line Architecture/Agile mix
  • Apoptosis
  • XP downscaling (e.g. to two developers) - OH YES IT DOES! (NB: in response to "XP does not scale down")
  • Fixed price contracts: feedback provided by XP very useful (managing scale)
  • DSDM (?)
No, they don't:
  • Descaling work is not scaling the process
  • XP doesn't scale
  • A large team cannot communicate as efficiently as a small team
  • XP should be called eXtreme Project Mgt
  • Yes
  • No process scales if you use it exactly the way it is described
  • You'll get hierarchies anyway - this is human nature
  • You can't have 100(0) people work on the same codebase unless they communicate
  • Non-Agile processes don't scale
  • No process scales past 100 people
  • XP does not scale down
  • 3rd party stuff (COTS) has to be integrated with the dev cycle & iterations
  • XP stays the same and we have to add a lot of things to make it work => RUP?