Travelled to:1 × Canada
1 × Spain
2 × South Africa
5 × USA
Collaborated with:∅ D.Damian N.Bettenburg R.Premraj J.Aranda I.Kwan T.Wolf T.H.D.Nguyen S.Marczak U.Stege M.Paasivaara C.Lassenius P.Räty S.Just C.Weiß T.Zimmermann
Talks about:predict (3) develop (3) communic (2) network (2) social (2) failur (2) build (2) talk (2) use (2) bug (2)
♂ Person: Adrian Schröter
DBLP: Schr=ouml=ter:Adrian
Facilitated 2 volumes:
ChaChWebChContributed to:
2013
20122011201020102009
2008
20082007Wrote 10 papers:
- ICSE-2013-PaasivaaraLDRS #agile #distributed #education #re-engineering #student #using
- Teaching students global software engineering skills using distributed scrum (MP, CL, DD, PR, AS), pp. 1128–1137.
- CSCW-2012-SchroterADK #communication
- To talk or not to talk: factors that influence communication around changesets (AS, JA, DD, IK), pp. 1317–1326.
- MSR-2011-Schroter #challenge #eclipse
- MSR Challenge 2011: Eclipse, Netbeans, Firefox, and Chrome (AS), pp. 227–229.
- ICSE-2010-Schroter #recommendation
- Failure preventing recommendations (AS), pp. 397–400.
- ICSE-2010-Schroter10a #developer #interactive #predict
- Predicting build outcome with developer interaction in Jazz (AS), pp. 511–512.
- MSR-2010-SchroterBP #debugging #developer #question #stack
- Do stack traces help developers fix bugs? (AS, NB, RP), pp. 118–121.
- ICSE-2009-WolfSDN #analysis #communication #developer #network #predict #social #using
- Predicting build failures using social network analysis on developer communication (TW, AS, DD, THDN), pp. 1–11.
- FSE-2008-BettenburgJSWPZ #debugging #question #what
- What makes a good bug report? (NB, SJ, AS, CW, RP, TZ), pp. 308–318.
- RE-2008-MarczakDSS #network #social
- Information Brokers in Requirement-Dependency Social Networks (SM, DD, US, AS), pp. 53–62.
- MSR-2007-Schroter #fault #predict
- Predicting Defects and Changes with Import Relations (AS), p. 31.