Extreme Programming Practice And Reflection In Global Center Project

Traditional software development moves the project more clearly from a requirements/specification phase, through successive designs that are evaluated and refined, until the system is built and tested. Documentation is leveraged in each step to transfer information. However, in today's world of rapidly changing the business and technology requirement, the pressures to deliver software quickly, change quickly, and change often are compelling reasons to rethink traditional software engineering practices. Agile Software Development, In particular, Extreme Programming (XP), has gained a significant amount of attention as an appropriate lightweight programming paradigm for high-speed and volatile software development.In this thesis, by examining the tailored XP practices in Global Center Project, we indicate the associated benefits such as increased capability to include emergent requirements, improved productivity, increased customer involvement, enhanced customer satisfaction, and increased risk management ability. Meanwhile, a setback experience in our project execution is presented, indicating the latent problem -- lack of the system architectural guidance -- in XP practice. Accordingly, the idea of incorporating System-Architecture-Centric methods into XP practice is examined and tentatively applied to Global Center project. Finally, we intend to summarize our observations, findings, and some recommendations for the future work.