2006•Unpublished venueRequires access

Introducing agile development (XP) into a corporate Webmaster environment - an experience report

Matthew Ganis, David Leip, Francis Grossman, Joseph Bergin

Open publisher page 8 citations

Abstract

In this paper we examine the challenges of moving a large, traditionally waterfall-driven organization toward an agile development methodology. In particular we address the problems/successes we encountered in our attempts to adhere to the 12 practices of extreme programming given: 1) this was a first attempt with agile techniques and in particular extreme programming and 2) an organization that while supportive, is still driven by its own set of governance processes which seem to be in contradiction to extreme programming. We discuss how we prepared our development and customer teams in order to achieve an agile mindset along with the issues we encountered in our attempts to mesh IBM's internal processes with our implementation of extreme programming. Finally we address some of the lessons learned as revealed by our final project retrospective and out future plans using agile techniques.

About this research paper

What this paper is about

In this paper we examine the challenges of moving a large, traditionally waterfall-driven organization toward an agile development methodology. In particular we address the problems/successes we encountered in our attempts to adhere to the 12 practices of extreme programming given: 1) this was a first attempt with agile techniques and in particular extreme programming and 2) an organization that while supportive, is still driven by its own set of governance processes which seem to be in contradiction to extreme programming. We discuss how we prepared our development and customer teams in order to achieve an agile mindset along with the issues we encountered in our attempts to mesh IBM's internal processes with our implementation of extreme programming. Finally we address some of the lessons learned as revealed by our final project retrospective and out future plans using agile techniques.

Why it matters

OpenAlex reports 8 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

In this paper we examine the challenges of moving a large, traditionally waterfall-driven organization toward an agile development methodology. In particular we address the problems/successes we encountered in our attempts to adhere to the 12 practices of extreme programming given: 1) this was a first attempt with agile techniques and in particular extreme programming and 2) an organization that while supportive, is still driven by its own set of governance processes which seem to be in contradiction to extreme programming. We discuss how we prepared our development and customer teams in order to achieve an agile mindset along with the issues we encountered in our attempts to mesh IBM's internal processes with our implementation of extreme programming. Finally we address some of the lessons learned as revealed by our final project retrospective and out future plans using agile techniques.

Key concepts: Extreme programming, Agile software development, Extreme programming practices, Scrum, Computer science, Mindset, Agile usability engineering, IBM

Related papers

Back to paper searchBrowse research topicsOriginal source
Introducing agile development (XP) into a corporate Webmaster environment - an experience report — Research Paper | ScholarLens