Agile software development with Scrum

By Andraž Cej. 2010

1,795 citations recorded by the source corpus.

View Paper: https://www.semanticscholar.org/paper/a34084fc597b941b62613677b0e02f070569a846

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

The impact of agile practices on communication in software development (2008, methodology): “The practices used in this study are based on the literature of Beck (2000) and Schwaber and Beedle (2002).”
Can Agile Project Management be Adopted by Industries Other than Software Development? (2014, methodology): “The term “agile project management” became known as a result of the dissemination of a set of methods developed specifically for the software industry, including Scrum (Schwaber & Beedle, 2001; Schwaber, 2004), Lean Software Development (Poppendieck & Poppendieck, 2003), Crystal (Cockburn, 2004), Fe”
A systematic literature review on agile requirements engineering practices and challenges (2015, methodology): “…methods such as Scrum, test-driven development, etc. Hasnain’s ﬁndings suggest that more empirical results are required on agile methods, in particular XP (Extreme Programming) (Beck, 1999) and Scrum (Schwaber & Beedle, 2001), in order to discuss the details from the practitioner’s point of view.”
Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development (2009, unknown): “The in-house method might fulﬁll all the same goals and values as XP, Scrum, and other agile methods but might do so by radically different means.”
A Control Theory Perspective on Agile Methodology Use and Changing User Requirements (2009, methodology): “Some well-known agile methodologies include eXtreme Programming (XP) (Beck 1999), Scrum (Rising and Janoff 2000, Schwaber and Beedle 2002), Feature Driven Design (Coad et al. 1999), Test Driven Development (Beck 2003), Crystal (Cockburn 2001), and Lean Programming (Poppendeick 2001).”
Agile Software Development Methods: Review and Analysis (2017, methodology): “In the following, the description of Scrum practices is given based on Schwaber and Beedle (2002).”
Controlling the uncontrollable: ‘Agile’ teams and illusions of autonomy in creative work (2011, methodology): “One of the most influential methodologies, labelled Scrum (Schwaber and Beedle, 2002), combines regular internal communication with intensive iterative cycles to solve production problems adaptively within an ‘empowered’ team structure.”
Teamwork quality and project success in software development: A survey of agile development teams (2016, background): “19 2001, and the first book on Scrum was published in 2001 (Schwaber and Beedle, 2001).”
A teamwork model for understanding an agile team: A case study of a Scrum project (2010, background): “A Scrum team is given significant authority and responsibility for many aspects of their work, such as planning, scheduling, assigning tasks to members, and making decisions: ''The team is accorded full authority to do whatever it decides is necessary to achieve the goal " [43].”
Does risk management contribute to IT project success? A meta-analysis of empirical evidence (2010, methodology): “Over the last decade, there appears to have been a growing interest in the development of new methodologies for the management of IT projects, such as e.g. Agile (see e.g. Schwaber and Beedle, 2002) and RUP (see e.g. Kruchten, 2004).”