Agile Technical Management of Industrial Contracts: Scrum Development of Ground Segment Software at the European Space Agency

Santos, Rui; Flentge, Felix; Bégin, Marc-Elian; Navarro, Vicente

doi:10.1007/978-3-642-20677-1_21

Cited by 8 publications

(6 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Product Owner [29,30] Sprint planning Scrum Team [6,31,32, 33] Sprint reviewing Scrum Team [34,35] Estimation Scrum Team Member [36] Integration Scrum Team Member [6,37] Travelling none [26,28] Project management none [24,29,38,39,40] Sprint planning identifies those stories on the product backlog that will fit into a single sprint, taking into account team velocity and capacity, and story estimates. Sprint reviewing is part of the Sprint Retrospective ceremony where the team identifies what went well, what could be improved, and might be added or removed from their process to be more effective.…”

Section: Prioritizationmentioning

confidence: 99%

A Study of the Scrum Master’s Role

Noll

Razzak

Bass

et al. 2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Scrum is an increasingly common approach to software development adopted by organizations around the world. However, as organizations transition from traditional plan-driven development to agile development with Scrum, the question arises as to which Scrum role (Product Owner, Scrum Master, or Scrum Team Member) corresponds to a Project Manager, or conversely which Scrum role should the Project Managers adopt?In an attempt to answer this question, we adopted a mixed-method research approach comprising a systematic literature review and a case study of a commercial software development team. Our research has identified activities that comprise the Scrum Master role, and which additional roles are actually performed by Scrum Masters in practice. We found ten activities that are performed by Scrum Masters. In addition, we found that Scrum Masters also perform other roles, most importantly as Project Managers. This latter situation results in tension and conflict of interest that could have a negative impact on the performance of the team as a whole. These results point to the need to re-assess the role of Project Managers in organizations that adopt Scrum as a development approach. We hypothesize that it might be better for Project Managers to become Product Owners, as aspects of this latter role are more consistent with the traditional responsibilities of a Project Manager.

show abstract

Section: Prioritizationmentioning

confidence: 99%

A Study of the Scrum Master’s Role

Noll

Razzak

Bass

et al. 2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Pemberitahuan yang dilakukan semakin cepat dalam tim Scrum terhadap masalah ini, maka akan semakin besar membatasi pemborosan sumber daya [20]. Sedangkan rekayasa dalam tim yaitu perangkat lunak yang memiliki banyak fitur dan fungsi yang ditambahkan namun tidak diperlukan oleh pelanggan karena kurangnya komunikasi dengan pemangku kepentingan, perencanaan yang buruk atau pengetahuan tim Scrum yang terbatas [19].…”

Section: Gambar 4 Kelompok Tantangan Dalam Adopsi Agileunclassified

Tantangan Adopsi Agile di Perguruan Tinggi di Indonesia

Sujono¹,

Setiawan²,

Haryono³

2020

Jurnal Informatika

View full text Add to dashboard Cite

Tingkat kesuksesan dalam pengembangan proyek perangkat lunak di berbagai negara masih rendah. Berdasarkan data yang ditemukan, di Amerika Serikat dan Eropa masih berkisar antara 16%-31%, di Afrika Selatan 34%, dan di Indonesia sebesar 27%. Agile merupakan pendekatan yang relatif baru dalam pengembangan perangkat lunak. Banyak organisasi telah mengadopsi Agile di semua atau beberapa proyek mereka. Temuan penelitian di berbagai industri dan negara, menunjukkan bahwa metode Agile memiliki dampak positif pada dimensi keberhasilan proyek. Namun upaya untuk melakukan adopsi Agile tidak sepenuhnya berjalan lancar, ditemukan berbagai tantangan yang mempengaruhi kesuksesannya. Penelitian ini dilakukan dengan tujuan untuk mengindentifikasi tantangan yang dihadapi dalam adopsi Agile di Perguruan Tinggi di Indonesia dengan menggunakan teori Scrum Adoption Challenges Detection Model (SACDM). Penelitian kuantitatif berbasis survei dan wawancara ini dilakukan di Badan Sistem Informasi (BSI), Universitas Islam Indonesia. Responden yang mengisi kuesioner sebanyak 41 orang yaitu Development (51,2%), Operational (22%), Product Owner (14,6%), dan Scrum Master dan Manajemen BSI (12,2%). Analisis data dilakukan dengan menggunakan uji statistik yaitu uji validitas dan analysis of variance. Berdasarkan hasil analisis, telah teridentifikasi 12 variabel tantangan dalam adopsi Agile dalam penelitian ini.

show abstract

“…While many of them meet the criteria, we decided to choose the two most descriptive cases, the ones which can answer best the questions in [16] for Sprint planning, Maham , M. (2008) [14] and Paasivaar, M. & Lasseniu, C. (2016) [18] for Sprint retrospective, and Santos, R. (2011) [19] and Eloranta, V.P. (2016) [7] for Sprint review.…”

Section: -Search Enginesmentioning

confidence: 99%

Agile Methods Knowledge Representation for Systematic Practices Adoption

Kiv¹,

Heng²,

Kolp³

et al. 2019

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

The popularity of agile methods is constantly increasing. Information and feedback on how these frameworks were adopted can easily be found in academia and industrial knowledge bases. Such a collective experience allowed the development of many approaches in the aim of simplifying the adoption process and maximizing the chances of success. These approaches provide practitioners with guidelines to help them find the practice that suits their team best. Nonetheless, these approaches are not systematic and practitioners need to go through a long process. For instance, they need to identify the important situational factors that can have a positive/negative effect on the agile practice adoption. Available experiences thus require lots of effort to be discovered. This research proposes an agile methods knowledge representation using an ontology so that the knowledge and experience on agile adoption reported in literature may be reusable and systematic. Based on this model, added knowledge and inference rules, practitioners will systematically be able to decide which practice to select and adopt, i.e, for a given goal, practitioners can retrieve which practices to achieve; from a situation, teams can tell what can be harmful and what can be useful for adopting a practice or what problems they may encounter; etc.

show abstract

Agile Technical Management of Industrial Contracts: Scrum Development of Ground Segment Software at the European Space Agency

Cited by 8 publications

References 1 publication

A Study of the Scrum Master’s Role

A Study of the Scrum Master’s Role

Tantangan Adopsi Agile di Perguruan Tinggi di Indonesia

Agile Methods Knowledge Representation for Systematic Practices Adoption

Contact Info

Product

Resources

About