Match!

The Scrum software development process for small teams

Published on Jul 1, 2000in IEEE Software2.945
· DOI :10.1109/52.854065
Linda Rising11
Estimated H-index: 11
,
N.S. Janoff1
Estimated H-index: 1
Sources
Abstract
In today's software development environment, requirements often change during the product development life-cycle to meet shifting business demands, creating endless headaches for development teams. We discuss our experience in implementing the Scrum software development process to address these concerns.
  • References (11)
  • Citations (373)
📖 Papers frequently viewed together
1999
1 Author (Kent Beck)
4,574 Citations
693 Citations
1 Author (Kent Beck)
736 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References11
Newest
#1Norm JanoffH-Index: 1
1 Citations
20 CitationsSource
#1James O. CoplienH-Index: 16
204 Citations
#1Jr. Frederick P. Brooks (UNC: University of North Carolina at Chapel Hill)H-Index: 4
Few books on software project management have been as influential and timeless as The Mythical Man-Month. With a blend of software engineering facts and thought-provoking opinions, Fred Brooks offers insight for anyone managing complex projects. These essays draw from his experience as project manager for the IBM System/360 computer family and then for OS/360, its massive software system. Now, 20 years after the initial publication of his book, Brooks has revisited his original ideas and added n...
642 Citations
#1Frederick P. BrooksH-Index: 49
1. The Tar Pit. 2. The Mythical Man-Month. 3. The Surgical Team. 4. Aristocracy, Democracy, and System Design. 5. The Second-System Effect. 6. Passing the Word. 7. Why Did the Tower of Babel Fail? 8. Calling the Shot. 9. Ten Pounds in a Five-Pound Sack. 10. The Documentary Hypothesis. 11. Plan to Throw One Away. 12. Sharp Tools. 13. The Whole and the Parts. 14. Hatching a Castrophe. 15. The Other Face. 16. No Silver Bullet -- Essence and Accident. 17. "No Silver Bullet" ReFired. 18. Propositions...
1,874 Citations
A short description is given of software process models and the issues they address. An outline is given of the process steps involved in the spiral model, an evolving risk-driven approach that provides a framework for guiding the software process, and its application to a software project is shown. A summary is given of the primary advantages and implications involved in using the spiral model and the primary difficulties in using it at its current incomplete level of elaboration. >
3,518 CitationsSource
An apparatus for investigating the course of fast chemical reactions, which are initiated in a liquid chemical system under investigation by an external perturbation, e.g. a steep temperature rise (temperature jump). The apparatus comprises first and second light paths conveying a probing light beam and a sense light beam, respectively, and an optical system of extremely high aperture which allows a wide variety of types of measurements, including absorption, fluorescense, fluorescense polarizat...
1,843 Citations
#2Murray SilversteinH-Index: 4
Last. Sara IshikawaH-Index: 4
view all 3 authors...
2,501 Citations
#1Frederick P. Brooks (UNC: University of North Carolina at Chapel Hill)H-Index: 49
The book, The Mythical Man-Month, Addison-Wesley, 1975 (excerpted in Datamation, December 1974), gathers some of the published data about software engineering and mixes it with the assertion of a lot of personal opinions. In this presentation, the author will list some of the assertions and invite dispute or support from the audience. This is intended as a public discussion of the published book, not a regular paper.
2,591 Citations
Cited By373
Newest
#1Sebastian Hönel (LNU: Linnaeus University)H-Index: 2
#2Morgan Ericsson (LNU: Linnaeus University)H-Index: 7
Last. Anna Wingkvist (LNU: Linnaeus University)H-Index: 6
view all 4 authors...
Abstract Source code is changed for a reason, e.g., to adapt, correct, or adapt it. This reason can provide valuable insight into the development process but is rarely explicitly documented when the change is committed to a source code repository. Automatic commit classification uses features extracted from commits to estimate this reason. We introduce source code density, a measure of the net size of a commit, and show how it improves the accuracy of automatic commit classification compared to ...
Source
#1Lucas Gren (Volvo Cars)H-Index: 7
#2Magdalena Lindman (Volvo Cars)H-Index: 8
When large industrial organizations change to(or start with) an agile approach to operations, managers and some employees are supposed to be "agile leaders" often without being given a clear definition of what that comprises when building agile teams. An inductive thematic analysis was used to investigate what 15 appointed leaders actually do and perceive as challenges regarding group dynamics working with an agile approach. Team maturity, Team design, and Culture and mindset were all categories...
Source
#1Lucas Gren (Chalmers University of Technology)H-Index: 7
#2Alfredo Goldman (USP: University of São Paulo)H-Index: 15
Last. Christian Jacobsson (University of Gothenburg)H-Index: 6
view all 3 authors...
With the agile approach to managing software development projects comes an increased dependability on well functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspective is related to some work practices of agile teams. Data were collected from 34 agile teams (200 individuals) from six software development organizations and one university in both Brazil and Sweden using the ...
3 CitationsSource
#1Sebastian Hönel (LNU: Linnaeus University)H-Index: 2
#2Morgan Ericsson (LNU: Linnaeus University)H-Index: 7
Last. Anna Wingkvist (LNU: Linnaeus University)H-Index: 6
view all 4 authors...
Source code is changed for a reason, e.g., to adapt, correct, or adapt it. This reason can provide valuable insight into the development process but is rarely explicitly documented when the change is committed to a source code repository. Automatic commit classification uses features extracted from commits to estimate this reason. We introduce source code density, a measure of the net size of a commit, and show how it improves the accuracy of automatic commit classification compared to previous ...
Source
The rapid growth of Information Technology led to the development of a multitude of smartphone systems worldwide. As a result, the number of educational institutions offering courses in areas such as programming and software engineering increased. However, traditional processes for software development did not keep pace with changing technologies. In the last few years, software development became more dynamic and iterative, requiring stakeholders to work as a team and deliver higher quality pro...
Source
#1Lucas Gren (University of Gothenburg)H-Index: 7
#2Magdalena Lindman (Volvo Cars)H-Index: 8
When large industrial organizations change to(or start with) an agile approach to operations, managers and some employees are supposed to be "agile leaders" often without being given a clear definition of what that comprises when building agile teams. An inductive thematic analysis was used to investigate what 15 appointed leaders actually do and perceive as challenges regarding group dynamics working with an agile approach. Team maturity, Team design, and Culture and mindset were all categories...
#1Ayesha Khalid (UOL: University of Lahore)
#2Shariq Aziz Butt (UOL: University of Lahore)H-Index: 2
view all 4 authors...
Source
#1Paul Luo Li (Microsoft)H-Index: 5
#2Amy J. Ko (UW: University of Washington)H-Index: 1
Last. Andrew Begel (Microsoft)H-Index: 1
view all 3 authors...
Great software engineers are essential to the creation of great software. However, today, we lack an understanding of what distinguishes great engineers from ordinary ones. We address this knowledge gap by conducting one of the largest mixed-method studies of experienced engineers to date. We surveyed 1,926 expert engineers, including senior engineers, architects, and technical fellows, asking them to judge the importance of a comprehensive set of 54 attributes of great engineers. We then conduc...
1 CitationsSource
#1Gleiston Guerrero-Ulloa (Universidad Técnica Estatal de Quevedo)H-Index: 1
#2Miguel J. Hornos (UGR: University of Granada)H-Index: 10
Last. Carlos Rodríguez-Domínguez (UGR: University of Granada)H-Index: 5
view all 3 authors...
This paper presents a development methodology for Internet of Things (IoT)-based Systems (IoTS) that gathers ideas from several of the most outstanding software development paradigms nowadays, such as Model-Driven Engineering (MDE) and Test-Driven Development (TDD), in addition to incorporating the principles that govern agile software development methodologies, such as SCRUM and XP. The methodology presented here, called Test-Driven Development Methodology for IoTS (TDDM4IoTS), has been propose...
Source