In the age of the smart machine: the future of work and power
In the age of the smart machine: the future of work and power
Making customer-centered design work for teams
Communications of the ACM
A set of principles for conducting and evaluating interpretive field studies in information systems
MIS Quarterly - Special issue on intensive research in information systems
Extreme programming applied: playing to win
Extreme programming applied: playing to win
Agile software development
Agile modeling: effective practices for extreme programming and the unified process
Agile modeling: effective practices for extreme programming and the unified process
Agile software development ecosystems
Agile software development ecosystems
Where now for development methodologies?
Communications of the ACM
Agile Project Management With Scrum
Agile Project Management With Scrum
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
Object-Oriented Systems Analysis and Design (2nd Edition)
Object-Oriented Systems Analysis and Design (2nd Edition)
Crystal clear a human-powered methodology for small teams
Crystal clear a human-powered methodology for small teams
Acceptance of agile methodologies: A critical review and conceptual framework
Decision Support Systems
Engineering the social: The role of shared artifacts
International Journal of Human-Computer Studies
Hi-index | 0.00 |
Since the late 1990s, agile or lightweight software development methodologies have experienced a meteoric rise of interest among systems developers who consider traditional systems development methodologies (such as Structured Systems Development, Information Engineering, and Rational Unified Process) too inflexible for building systems having unpredictable and changing requirements. Agile methodologies try to adapt to rapid requirement changes by having short, iterative development cycles and by encouraging frequent, open communication with customers. However, agile methodologies are still in the process of devising systematic approaches on how to be adaptive to unpredictable and changing requirements and how to incorporate customers into the systems development process. In this study, we show how an ethnographic research process called Strip Resolution can be applied as a systematic complement to projects applying agile development principles. We illustrate, in detail, how the Strip Resolution Process (SRP) enabled us, in the role of systems developers, to adapt to changing and unpredictable user requirements and to incorporate customers into the systems development process.