Agile Development Teams Need Business Analysts |
|
| Saturday, 10 November 2007 12:31 |
During the past few years there has been a trend developing in the software industry toward agile development processes. Unfortunately for the business analyst (BA), much of the literature regarding agile development focuses on the perspective of the developer, largely ignoring the role of the business analyst. BAs play a key role capturing requirements on large, software-intensive projects. Yet agile methodology emphasizes face-to-face communication over written documentation. Teams are co-located where programmers and their "customers" interact directly as a means of eliciting requirements. Organizations that are moving toward agile development may wonder if a has a role in agile software development. The answer, as addressed by this paper, is a resounding "Yes." During the past few years there has been a trend developing in the software industry toward agile development processes. Unfortunately for the business analyst (BA), much of the literature regarding agile development focuses on the perspective of the developer, largely ignoring the role of the business analyst. BAs play a key role capturing requirements on large, software-intensive projects. Yet agile methodology emphasizes face-to-face communication over written documentation. Teams are co-located where programmers and their "customers" interact directly as a means of eliciting requirements. Organizations that are moving toward agile development may wonder if a has a role in agile software development. The answer, as addressed by this paper, is a resounding "Yes."Read more >>
Set as favorite
Bookmark
Email this
Hits: 892 Trackback(0)Comments (0)
|


During the past few years there has been a trend developing in the software industry toward agile development processes. Unfortunately for the business analyst (BA), much of the literature regarding agile development focuses on the perspective of the developer, largely ignoring the role of the business analyst. BAs play a key role capturing requirements on large, software-intensive projects. Yet agile methodology emphasizes face-to-face communication over written documentation. Teams are co-located where programmers and their "customers" interact directly as a means of eliciting requirements. Organizations that are moving toward agile development may wonder if a has a role in agile software development. The answer, as addressed by this paper, is a resounding "Yes."
