How to manage Software Architecture documentation in Scrum Framework
Mustafa Savasci Fatih Cetin Caglar Cakir Oğuz Findik
AbstractIn software development processes, architectural documents can be prepared by the beginning of the project like Big Design Up front (BDUF) if software projects requirements are prepared with details and reviewed by the team. However, software projects with a lot of uncertainties or ambiguous requirements do not have any process to prepare and record architectural decisions during the software development. In recent years, agile software development has become very popular in the software industry. Therefore software development teams try to adopt their software processes against changing requirements and dynamic market conditions with using agile methodologies. Because of the underlying philosophy of agile, agile teams started paying more attention to working product over comprehensive documentation and big design up front. However agile software development also contains architectural and design decisions during the development. One of the agile principles also points that the best architectures, requirements, and designs emerge from the agile team during the development. Nevertheless, agile methodologies do not offer any processing cycle for architectural documentation in their process. In this article, we will propose how the architectural decisions will be documented in agile frameworks, which one is the most popular Scrum framework.