"Mega" is defined as problems that are very large in either cost ($25-200M) or in effort (more than 50 people).
We observed that it would be good to start the project with a regular XP team and stabilize the early user stories and the general structure or the system through a number of iterations before growing more teams. How new teams are built/organized was an open issue (MegaExtremeProgrammingTeamOrganization?). Another issue raised by the participants was how AcceptanceTests would need to be adapted (MegaExtremeProgrammingAcceptanceTests).
Was this a workshop where people were discussing their experiences trying to adapt XP to large projects, or a workshop where people were theorizing about how to do it if they ever got a chance? <see revision above>
How does MegaExtremeProgramming relate to ExtremeProgrammingMayScaleUp and LargeExtremeProgramming?
On big multi-team XP projects, you might try pairing cross-team to make some changes.
Contributors: JeffGrigg (who does not claim to speak for the XP community)
This page mirrored in ExtremeProgrammingRoadmap as of April 29, 2006