Refactoring the Development Process: Experiences with the Incremental Adoption of Agile Practices

Hodgetts, Paul

doi:10.1109/adevc.2004.17

Cited by 21 publications

(18 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…For example, Hodgetts [17] reports on one team that had only one database expert, but too much work for one expert. When this caused a bottleneck, the team decided to use PP to spread the database knowledge among developers.…”

Section: Knowledge Transfer In Pair Programmingmentioning

confidence: 99%

Knowledge transfer in pair programming: An in-depth analysis

Plonka

Sharp

Linden

et al. 2015

International Journal of Human-Computer Studies

View full text Add to dashboard Cite

Whilst knowledge transfer is one of the most widely-claimed benefits of pair programming, little is known about how knowledge transfer is achieved in this setting. This is particularly pertinent for novice−expert constellations, but knowledge transfer takes place to some degree in all constellations.We ask "what does it take to be a good "expert" and how can a "novice" best learn from a more experienced developer?". An in-depth investigation of video and audio excerpts of professional pair programming sessions using Interaction Analysis reveals: six teaching strategies, ranging from "giving direct instructions" to "subtle hints";; and challenges and benefits for both partners. These strategies are instantiations of some but not all teaching methods promoted in cognitive apprenticeship; novice articulation, reflection and exploration are not seen in the data. The context of pair programming influences the strategies, challenges and benefits, in particular the roles of driver and navigator and agile prioritisation which considers business value rather than educational progression. Utilising these strategies more widely and recognizing the challenges and benefits for both partners will help developers to maximise the benefits from pairing sessions. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 1 Introduction "Two heads are better than one" is a common idiom referring to the advantages of collaborative work. *ManuscriptThe value of collaboration is explicitly encouraged in software development through a practice known as pair programming. Pair programming (PP) is a software development technique where two developers work closely together to solve a development problem [41,1].Several benefits of PP have been claimed including improved understandability and maintainability of code and design [35,37], decreased defect rates [24,18,23,10,25] and knowledge transfer [21,20,23,32,34,35,36,38,40]. This paper focuses on knowledge transfer in PP. This is common when a more experienced developer teaches a less experienced developer, for example, to bring new staff up to speed [3,42]. However, given that developers never have identical knowledge, a certain degree of knowledge transfer would be expected within every PP constellation.Pairing with someone who has a different knowledge level can be problematic [2,7] and developers tend to interact differently in this situation in comparison to pairing with other developers with similar knowledge levels [9,7]. For example, Plonka et al. [29] showed that less knowledgeable developers (novices) can disengage in PP sessions and can sometimes not follow their more knowledgeable partner (expert). These three questions are addressed through a qualitative analysis (using Interaction Analysis [19]) of video recordings of professional developers working together on their day to day t...

show abstract

Section: Knowledge Transfer In Pair Programmingmentioning

confidence: 99%

Knowledge transfer in pair programming: An in-depth analysis

Plonka

Sharp

Linden

et al. 2015

International Journal of Human-Computer Studies

View full text Add to dashboard Cite

show abstract

“…The incremental adoption of agile practices in the Government Workflow Project, a project initiated by the government of a major California county to automate the workflow of key business processes in the criminal justice system, is described in [ER4]. The project team ended up performing more up-front analysis and using small batch size for estimations as a response to frustrating velocity fluctuations and inconsistent completion of features.…”

Section: B Lean Principles Guiding Agile Practicesmentioning

confidence: 99%

The Combination of Agile and Lean in Software Development: An Experience Report Analysis

Wang

2011

2011 AGILE Conference

View full text Add to dashboard Cite

Abstract-There has been a noticeable focus shift from agile methods such as eXtreme Programming (XP) and Scrum to lean software development in the last several years, which is indicated as "from agile to lean". However, the reality may not be as simple or linear as the term implies. To provide a better understanding of the combined use of agile and lean approaches in software development, a set of experience reports were analysed. These reports were published in the past conferences dedicated to agile software development and report experiences of using both agile and lean. The results of the analysis show that agile and lean can be combined in different manners for different purposes in software development. Lean is often applied as guiding principles for agile development. When combined at practice level, flowbased lean processes tend to substitute time-boxed agile processes.

show abstract

“…Practice: Value stream mapping, FIFO queue [ER26] (not revealed) Financial service Practice: Visualise all work items, Root cause analysis, Kaizen [ER22] (not revealed) Telecommunication Practice: Use pull systems, Kanban board, Value stream mapping, Kaizen, Pull the andon cord [ER15,ER25] Systematic Software systems Practice: Kaizen, PDCA cycle, Root cause analysis, Jidoka Table 9: The cases in the "lean within agile" category Lean concepts and principles have been used as thinking tools to make sense and guide the use and adaptation of agile practices in [ER1]. The Government Workflow Project, a project initiated by the government of a major California county to automate the workflow of key business processes in the criminal justice system, has adopted agile practices incrementally.…”

Section: Learning Management Systemmentioning

confidence: 99%