Allan Kelly
Abstract
Open-access reader
Agile software development, and other applications of agile working, continue to grow both in terms of usage and in terms of knowledge and lore. As a result the Agile Coach role has become an established role; yet the role is mired in confusion. This paper aims to reduce this confusion by differentiating the agile coach role.
OpenAlex reports 1 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Agile software development, and other applications of agile working, continue to grow both in terms of usage and in terms of knowledge and lore. As a result the Agile Coach role has become an established role; yet the role is mired in confusion. This paper aims to reduce this confusion by differentiating the agile coach role.
Key concepts: Agile software development, Confusion, Agile usability engineering, Agile Unified Process, Lean software development, Extreme programming practices, Computer science, Process management