Transition to Agile Development - Rediscovery of Important Requirements Engineering Practices

Many organizations have started to use agile development processes to speed up the development cycle and to improve the ability of the company in reacting to changing requirements. Adopting agile practices may happen as a revolution where all old practices are removed or as a more gradual process. I...

Full description

Saved in:
Bibliographic Details
Main Authors: Savolainen, J, Kuusela, J, Vilavaara, A
Format: Conference Proceeding
Language:English
Subjects:
agility
best practices
Companies
Computer architecture
Hardware
Programming
requirements engineering
Software
Software architecture
Online Access:Request full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Many organizations have started to use agile development processes to speed up the development cycle and to improve the ability of the company in reacting to changing requirements. Adopting agile practices may happen as a revolution where all old practices are removed or as a more gradual process. In this paper, we discuss lessons learnt in two agile transition processes. Based on our experience, agile processes can be used in embedded software development for products. The challenges include the varying size of user requirements, the role of system requirements, and architecturally significant requirements. It is difficult for large organizations to be agile. Work allocation for a large number of different teams with different competencies tends to decrease speed, and increase the role of design and management. We conclude that agile development in this context needs very skilled developers and has to be a combination of new and old practices.
ISSN:1090-705X
2332-6441
DOI:10.1109/RE.2010.41