Search

A personal narrative is presented which explores the author's experience of training people about agile software development through storytelling in presentations. The article further discusses guidelines for crafting a story by discussing two stories entitled "The Castle Fairy Tale" and "A Soviet Economist in Rotterdam." Information about the author of the article is also presented. INSETS: CRAFTING A STORY: GUIDELINES FOR DOING IT YOURSELF;EXAMPLE 1: THE CASTLE FAIRY TALE;EXAMPLE 2: A SOVIET ECONOMIST IN ROTTERDAM.

We conducted a quasi-experiment comparing novice pair programmers to expert pair programmers. The expert pairs wrote tests with a higher instruction, line, and method coverage than the novice pairs and changed the given program skeleton to a larger extent. However, the expert pairs were also slower than the novice pairs. The pairs within both groups switched keyboard and mouse possession frequently. Furthermore, most pairs did not share the input devices equally but rather had one partner who is more active than the other. [ABSTRACT FROM AUTHOR]

The authors comment on the condition of the agile system development research. They cite the growing popularity of agile system development methods in handling rapid changes of the environment, as well as its dedication to several journal issues, conferences, and workshops are cited. However, they point out that research has been lagged behind practice and stresses the need for developers to understand its methods and to improve the level of its research.

The article discusses the foundations of adapting agile development methodologies in software development. It explores the growing popularity of Extreme Programming due to its focus on managing time to market constraints, however, the method needs to be adapted to suit the needs of different contexts. It examines the use of adaptive structuration theory to analyze data from multisite case study and describes several sources of structure that affects the appropriation of agile practices.

The article discusses the proposed Method for Method Configuration (MMC) in tailoring information systems development. It explores how the method has been used during the development of three software projects to manage method tailoring and to promote agile goals and values. It explores the content examples of the method configurations which determine the significance of MMC and its conceptual framework on eXtreme Programming.

This article introduces a methodology for developing applications incorporating components of Agile development methods with the traditional software development life cycle (SDLC), a.k.a. the ''waterfall'' model of software development. We look at the causes for failure of software development projects and propose steps in the development process to address many of the root causes of these failures (it would be implausible to state that any development methodology could eliminate the risk of failure). We also provide a critical review of Agile principles and the traditional SDLC. The steps of the new methodology are then described with rationalization for their necessity. [ABSTRACT FROM AUTHOR]

An interview with software developer Gus Power about Agile software development is presented. He says that he first started to use Agile in 2001 when he was developing an order management system for Dell. He argues on the claim that agile does not work for inexperienced developers but believes that it is the best means for bringing on new developers. He outlines the main difficulties in agile projects such as being delayed by false metrics, having no actual customer contact, and complacency.