Abstract is missing.
- A case study of distances in a large co-located software development organisationElizabeth Bjarnason, Baldvin Gislason Bern, Linda Svedberg. 1-8 [doi]
- A collaborative approach to teaching software startups: findings from a study using challenge based learningRafael Chanin, Afonso Sales, Alan R. Santos, Leandro Bento Pompermaier, Rafael Prikladnicki. 9-12 [doi]
- A framework for understanding chatbots and their futureElahe Paikari, André van der Hoek. 13-16 [doi]
- An exploratory study for scoping software product lines in a collaborative wayMarta Cecilia Camacho Ojeda, Julio Ariel Hurtado Alegria, Francisco Javier Álvarez Rodriguez. 17-20 [doi]
- An initial understanding of task interdependence in software engineering: a case studyGeorge Marsicano, Victor L. de Oliveira, Leila M. R. de Sousa Mariz, Fabio Q. B. da Silva. 21-28 [doi]
- Code review for newcomers: is it different?Vladimir Kovalenko, Alberto Bacchelli. 29-32 [doi]
- Context in programming: an investigation of how programmers create contextSouti Chattopadhyay, Nicholas Nelson 0002, Thien Nam, McKenzie Calvert, Anita Sarma. 33-36 [doi]
- Crowdsourcing security: opportunities and challengesLalit Mohan Sanagavarapu, Y. Raghu Reddy. 37-40 [doi]
- Designing a capability-centric web tool to support agile team composition and task allocation: a work in progressSai Datta Vishnubhotla, Emilia Mendes, Lars Lundberg. 41-44 [doi]
- Diversity in software engineeringÁlvaro Menezes, Rafael Prikladnicki. 45-48 [doi]
- Guidelines towards better participation of older adults in software development processes using a new SPIRAL method and participatory approachWieslaw Kopec, Radoslaw Nielek, Adam Wierzbicki. 49-56 [doi]
- How do practitioners perceive assurance cases in safety-critical software systems?Jinghui Chen, Micayla Goodrum, Ronald A. Metoyer, Jane Cleland-Huang. 57-60 [doi]
- Influencers of quality assurance in an open source communityAdam Alami, Yvonne Dittrich, Andrzej Wasowski. 61-68 [doi]
- Leveraging motivational theories for designing gamification for RENaomi Unkelos-Shpigel, Irit Hadar. 69-72 [doi]
- Myagile: sociological and cultural effects of agile on teams and their membersRobert Biddle, Andreas Meier 0004, Martin Kropp, Craig Anslow. 73-76 [doi]
- On gender, ethnicity, and culture in empirical software engineering researchLucas Gren. 77-78 [doi]
- Psychological safety and norm clarity in software engineering teamsPer Lenberg, Robert Feldt. 79-86 [doi]
- Researching cooperation and communication in continuous software engineeringYvonne Dittrich, Jacob Nørbjerg, Paolo Tell, Lars Bendix. 87-90 [doi]
- Rethinking coordination in large-scale software developmentTorgeir Dingsøyr, Finn Olav Bjørnson, Nils Brede Moe, Knut H. Rolland, Eva Amdahl Seim. 91-92 [doi]
- Sketching with a purpose: moving from supporting modeling to supporting software engineering activitiesMatthias Book, André van der Hoek. 93-96 [doi]
- Some reasons why actual cross-fertilization in cross-functional agile teams is difficultHelena Barke, Lutz Prechelt. 97-103 [doi]
- The structure of software design discussionsGiovanni Viviani, Calahan Janik-Jones, Michalis Famelis, Gail C. Murphy. 104-107 [doi]
- Toward collecting and delivering knowledge for software design at the whiteboardAdriana Meza Soria, André van der Hoek. 108-109 [doi]
- Who gets a patch accepted first?: comparing the contributions of employees and volunteersGustavo Pinto 0001, Luiz Felipe Dias, Igor Steinmacher. 110-113 [doi]
- Why we engage in FLOSS: answers from core developersJailton Coelho, Marco Tulio Valente, Luciana Lourdes Silva, André C. Hora. 114-121 [doi]