Studies

Here is a list of all studies. Click on an ID to see more information.

Showing 1 to 25, 114 total. 12345Next »

ID Study Name Type Format Description Organization Year Reference
101Abrahamsson2002BookBook2002Abrahamsson, P., Salo, O., Ronkainen, J. & Warsta, J. (2002). Agile software development: review and analysis. VTT Publications.
98Abrahamsson2003Empirical StudyObservation2003Abrahamsson, P., Siponen, M. & Ronkained, J. (2003). New directions on agile methods: a comparative analysis. In Proceedings of the International Conference on Software Engineering, May 3-5 2003.
74Abrahamsson2004Empirical StudyCase Study4 developersa large Finnish research institute2004Abrahamsson; P. & Koskela; J. (2004). Extreme programming: a survey of empirical data from a controlled case study; in IEEE.
102Agrawal2007Empirical StudyCase Study1990Agarwal, Ritu and Tanniru, Mohan R. , Knowledge Acquisition Using Structured Interviewing: An Empirical Investigation, Journal of Management Information Systems, Vol. 7 No. 1, Summer 1990 pp. 123 - 140
109Alvarez&Urla2002Empirical StudyExperiment Report2002 Rosío Alvarez,Jacqueline Urla, Tell me a good story: using narrative analysis to examine information requirements interviews during an ERP implementation, ACM SIGMIS Database - Special issue on Critical analysis of ERP systems: the macro level, Volume 33 Issue 1, Winter 2002
108Alvarez2002Empirical StudyExperiment Report2002 R. Alvarez,Discourse Analysis of Requirements and Knowledge Elicitation Interviews, 35th Annual Hawaii International Conference on System Sciences (HICSS'02)-Volume 8
88Ambler2002BookBook2002Ambler, S. (2002). Agile Modeling: Effective Practices for eXtreme Programming and the Unified Process. New York: John Wiley & Sons, Inc.
27Aranda2007Empirical StudyCase StudyNANA2007Aranda; J.; Easterbrook; S.; & Wilson; G. (2007). Requirements in the wild: How small companies do it. Requirements Engineering Conference; 2007. RE '07. 15th IEEE International; 39-48
14Arisholm2007Empirical StudyControlled Experiment99 developers; junior to seniorNA2007Arisholm; E.; Gallis; H.; Dyba; T.; & Sjoberg; D. I. K. (2007). Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise. In IEEE Transactions on Software Engineering 33(2); 65-86.
60Ash2010Empirical StudyInterviewing SurveyNANA2010Ash; S. (2010) Compare DSDM and XP. accessed via: http://c2.com/cgi-in/wiki?CompareDsdmAndXp; in 2010
65Augustine2005Empirical StudyExperiment ReportNANA2005Augustine; S.; Payne; B.; Sencindiver; F. & Woodcock; S. (2005). Agile project management: steering from the edges. In Communications of the ACM; 48(12); 85-89.
58Banda2009Empirical StudyExperiment ReportNANA2009Banda; J (2009). Applying Queuing Theory to Sprints; available online at: http://juanbandaonscrum.blogspot.com/2009/09/applying-queuing-theory-to-sprints.html
61Barritt2002Empirical StudyExperiment ReportNAWessex Water2002Barritt; D. (2002). IEC 61131 and DSDM in real-time process control applications. In Computing & Control Engineering Journal; 13(2); 94-100.
51Beck1999Empirical StudyCase Study10 ~ 15 programmersNA1999Beck; K. (1999). Embracing change with extreme programming. In Computer; 32(10); 70-77.
37Beck2001BookBookNANA2001Beck; K.; & Fowler; M. (2001). Planning Extreme Programming; Addison Wesley.
41Beck2003BookBookNANA2003Beck; K. (2003). Test-driven development: by example; Addison-Wesley.
1Begel2007Empirical StudyInterviewing Survey492 respondants Microsoft2006Begel; A.; & Nagappan; N. (2007). Usage and Perceptions of Agile Software Development in an Industrial Context: An Exploratory Study. First International Symposium on Empirical Software Engineering and Measurement; 2007 (ESEM 2007). ; 255-264.
70Benefield2008Empirical StudyExperiment ReportNAYahoo!2008Benefield; G. (2008). Rolling out agile in a large enterprise. In IEEE: proceedings of the 41st Hawaii international conference on system sciences - 2008.
12Berczuk2007Empirical StudyExperiment ReportNANA2007Berczuk; S. (2007a). Back to Basics: The Role of Agile Principles in Success with an Distributed Scrum Team. Agile; 382-388.
64Boby2004Empirical StudyControlled ExperimentTwo 8-person groups at each of 3 companiesJohn Deere; Rolemodel Software; Ericsson2004Boby; G. & Williams; L. (2004). A structured experiment of test-driven development. In Information and software technology; 46; 337-342.
55Charles2001Empirical StudyExperiment ReportNANA2001Charles; P.; & Jan Willem; H. (2001). Using Extreme Programming in a Maintenance Environment. In IEEE Softw.; 18(6); 42-50.
18Choi2008Empirical StudyControlled Experiment68 undergraduate + 60 graduate studentsNA2007Choi; K. S.; Deek; F. P.; & Im; I. (2008). Exploring the underlying aspects of pair programming: The impact of personality. In Information and Software Technology; 50(11); 1114-1126.
15Chong2007Empirical StudyEthnography2 teams NA2005Chong; J.; & Hurlbutt; T. (2007). The Social Dynamics of Pair Programming. Proceedings of the 29th international conference on Software Engineering; 354-363; IEEE Computer Society.
113Christel1992Empirical StudyObservation1992Michael Christel, Issues in Requirements Elicitation, Technical Report,CMU/SEI-92-TR-012, September 1992
13Cockburn2001Empirical StudyControlled ExperimentNANA2001Cockburn; A.; & Williams; L. (2001). The costs and benefits of pair programming. (Ed.).In: Extreme programming examined (pp. 223-243); Addison-Wesley Longman Publishing Co.; Inc.