On the responsibilities of software architects and software engineers in an agile environment: who should do what?

Authors:
Antony Tang;Ton Gerrits;Peter Nacken;Hans van Vliet
Affiliations:
VU University, Amsterdam, Netherlands;Océ Technologies, Venlo, Netherlands;Océ Technologies, Venlo, Netherlands;VU University, Amsterdam, Netherlands
Venue:
Proceedings of the 4th international workshop on Social software engineering
Year:
2011

Citing 12
Cited 0

Software Architecture in Practice

Software Architecture in Practice
Balancing Agility and Discipline: A Guide for the Perplexed

Balancing Agility and Discipline: A Guide for the Perplexed
Organizational Patterns of Agile Software Development

Organizational Patterns of Agile Software Development
The software architect

Communications of the ACM - ACM at sixty: a look back in time
The Duties, Skills, and Knowledge of Software Architects

WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Architectural Knowlege Management Strategies: Approaches in Research and Industry

SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
Editorial: Editorial

Journal of Systems and Software
Empirical studies of agile software development: A systematic review

Information and Software Technology
Controversy Corner: What do software architects really do?

Journal of Systems and Software
Agility and Architecture: Can They Coexist?

IEEE Software
Software architecture awareness in long-term software product evolution

Journal of Systems and Software
Post-agility: What follows a decade of agility?

Information and Software Technology

Quantified Score

Hi-index	0.00

Visualization

Abstract

As there is considerable freedom for software workers to decide what to do in an agile environment, there is a need to be explicit about social aspects such as task ownership between roles and the agility in owning those tasks. We have conducted interviews and a survey at a large organization to explore these issues. The results indicate that there are areas where architects and software engineers have different views on task ownership. Some of the less exciting tasks such as documentation and issue clarification then easily become a hot potato nobody wants.