The Agile Requirements Refinery: Applying SCRUM Principles to Software Product Management

Vlaanderen, Kevin; Brinkkemper, Sjaak; Jansen, Slinger; Jaspers, Erik

doi:10.1109/iwspm.2009.7

Cited by 37 publications

(39 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…An agile Software Product Management (SPM) method which follows the Scrum methodology is proposed by Vlaanderen et al (2011) as a way of improving and aligning requirements with the product vision. The main idea of the method is to refine the requirements of the software product through a Product Management Sprint Backlog, for which both the Business Analyst and the Scrum Master of Cegeka should be responsible.…”

Section: R1 Parallel Spm and Development Sprintsmentioning

confidence: 99%

Isu Kebutuhan Teknis dalam Pengembangan Perangkat Lunak Terdistribusi Agile

Paramartha

2018

masy. telematika dan inf.

View full text Add to dashboard Cite

There are two approaches of software development and their combination that have attracted a lot of interest from the research community lately. The first is the Distributed/Global Software Development, which entails development in multiple geographically dispersed sites. The second approach is the Agile Software Development, which incorporates an evolving development process for better adaptation to changing environments and requirements. Their combination is a challenging topic due to a lot of contradicting characteristics. In this paper, the successful communication between remote sites and especially the communication of requirements in an Agile Distributed Software Development process are investigated. The research is based on a case study at Cegeka, a Belgium ICT company with branches in the Netherlands and Romania. The Dutch and Romanian sites are engaged in agile global software development practice, facing a situation with requirements understanding. Enhancement of the awareness of the vision of the product and the vision of the company through the communication of requirements between the Business Analyst and the Scrum Master is the main challenge that this paper aims to address. However, due to the limited information we have on how the Scrum Master and the Business Analyst from Cegeka communicate, we cannot give very specific answer but just a general solution and best practices. Nonetheless it should be a good starting point for improving requirements communication within the distributed software development process between the Romanian and the Dutch sites of Cegeka. AbstrakAda dua pendekatan pengembangan perangkat lunak dan kombinasi dari kedua pendekatan tersebut menjadi bahan yang menarik banyak minat komunitas riset akhir-akhir ini. Kedua pendekatan dimaksud yaitu pengembangan perangkat lunak metode Distributed/Global, yang digunakan untuk lokasi yang tersebar secara geografis, serta pengembangan perangkat lunak metode Agile, yang dapat dengan mudah beradaptasi terhadap perubahan lingkungan dan kebutuhan. Kombinasi kedua pendekatan tersebut menjadi tantangan karena banyak karakteristik yang saling bertentangan. Dalam tulisan ini, diamati proses komunikasi yang berhasil antara dua daerah yang berjauhan, utamanya terkait kebutuhan dalam pengembangan perangkat lunak agile distributed. Penelitian ini merupakan studi kasus di Cegeka, sebuah perusahaan TIK milik Belgia yang memiliki cabang di Belanda dan Rumania. Daerah Belanda dan Rumania telah mencoba praktik agile global software development, namun pemahaman akan kebutuhannya belum sama. Peningkatan kesadaran akan visi produk dan visi perusahaan melalui komunikasi terkait kebutuhan antara Analis Bisnis dan Scrum Master adalah tantangan utama yang ingin disampaikan makalah ini. Namun, karena terbatasnya informasi terkait bagaimana Scrum Master dan Analis Bisnis dari Cegeka berkomunikasi, penelitian ini tidak dapat memberikan jawaban yang sangat spesifik namun solusi umum dan praktik terbaik. Meskipun demikian, hal ini menjadi titik awal yang baik unt...

show abstract

Section: R1 Parallel Spm and Development Sprintsmentioning

confidence: 99%

Isu Kebutuhan Teknis dalam Pengembangan Perangkat Lunak Terdistribusi Agile

Paramartha

2018

masy. telematika dan inf.

View full text Add to dashboard Cite

show abstract

“…Um dos métodos ágeis que tem ganhado popularidade devido sua simplicidade, produtividade e gerenciamento leve é o Scrum [39]. O Scrum possui a ideia central de que muitos processos não podem ser previstos durante o desenvolvimento do sistema e por isto ele adota uma abordagem flexível [44]…”

Section: Referencial Teórico 21 Métodos áGeisunclassified

“…Benefícios reportados pelo uso de métodos ágeis relacionados às atividades de ER envolvem melhoria da comunicação e compreensão das necessidades, redução da ambiguidade e capacidade de responder a mudanças. Foram identificadas ainda lições aprendidas reportados nos trabalhos analisados, tais como, o fato de se utilizar diferentes técnicas de elicitação auxilia no levantamento dos requisitos ( [8], [22], [30] e [36]); a adoção de práticas da ER tradicional e com práticas ágeis traz resultados positivos ( [7], [14], [15] e [17]); assim como faz surgir um perfil de profissional com características híbridas entre os dois modelos ( [7] e [44]).…”

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

Belo Horizonte -MG -Brasil mwerneck@pucminas.br RESUMOPor não possuírem características prescritivas, não há, nos métodos ágeis, uma definição formal sobre como as atividades de Engenharia de Requisitos (ER) devem ser executadas. Isso faz com que haja uma variedade de formas de se definir como serão levantados, priorizados, especificados e validados os requisitos. Assim, torna-se necessário compreender como as pesquisas em ER ágil têm caracterizado estas atividades. O objetivo deste trabalho foi, por meio de uma revisão sistemática da literatura, identificar as práticas e técnicas utilizadas para cada processo da ER em projetos ágeis. O trabalho identificou ainda importantes desafios e lições aprendidas que devem direcionar as evoluções nesta área. ABSTRACTSince agile methods do not have prescriptive characteristics, there is not a formal definition on how Requirements Engineering (RE) activities should be executed. This situation leads to a variety of different forms of defining how requirements are elicited, prioritized, documented and validated. So, it is necessary to comprehend how research on RE have characterized such activities. By using a systematic review approach, the objective of this study was to identify practices and techniques that have been used for each RE process in agile projects. The study also identified challenges and lessons learned that should direct improvements in this area. CCS Concepts• Software and its engineering Software creation and management Software development process management Agile software development • Software and its engineering Software creation and management Designing Software Requirements Analysis.

show abstract

“…It is commonplace to state that “software evolves,” and it is part of software developers' duty to support and operate such an evolution. The adaptive, preventive, and perfective evolution of a piece of software to address new requirements is taken into account by software development methodologies and project management methods . But this evolution is not related to the addition of immediate business value in the program.…”

Section: Introductionmentioning

confidence: 99%

A delta‐oriented approach to support the safe reuse of black‐box code rewriters

Benni

Mosser

Moha

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Large-scale corrective and perfective maintenance is often automated thanks to rewriting rules using tools such as Python2to3, Spoon, or Coccinelle. Such tools consider these rules as black-boxes and compose multiple rules by chaining them: giving the output of a given rewriting rule as input to the next one. It is up to the developer to identify the right order (if it exists) among all the different rules to yield the right program. In this paper, we define a formal model compatible with the black-box assumption that reifies the modifications (Δs) made by each rule. Leveraging these Δs, we propose a way to safely compose multiple rules when applied to the same program by (a) ensuring the isolated application of the different rules and (b) identifying unexpected behaviors that were silently ignored before. We assess this approach on two large-scale case studies: (a) identifying conflicts in the Linux source-code automated maintenance and (b) fixing energy antipatterns existing in Android applications available on GitHub.

show abstract

The Agile Requirements Refinery: Applying SCRUM Principles to Software Product Management

Abstract: Although agile software development methods such as SCRUM and DSDM are gaining popularity,

Cited by 37 publications

References 14 publications

Isu Kebutuhan Teknis dalam Pengembangan Perangkat Lunak Terdistribusi Agile

Isu Kebutuhan Teknis dalam Pengembangan Perangkat Lunak Terdistribusi Agile

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

A delta‐oriented approach to support the safe reuse of black‐box code rewriters

Contact Info

Product

Resources

About