Systematic Mapping Protocol -- Agile strategies for software development according to technical and environmental complexity factors
Fernando Pinciroli

TL;DR
This paper presents a systematic mapping study to analyze how agile and plan-based project management strategies are selected based on technical and environmental complexity factors in software development.
Contribution
It provides a structured overview of evidence and frameworks guiding the selection of management approaches according to project complexity.
Findings
Identifies criteria for selecting management strategies based on complexity
Analyzes frameworks used to characterize project complexity
Maps evidence on agile and plan-based approach selection
Abstract
Software development projects management is a complex endeavor because it requires dealing with numerous unforeseen events that constantly arise along the way and that go against the expectations that had been established at the beginning. A good project leader is not so much who carries out what is planned, but rather who is able to deal with all the inconveniences that arise and, in the end, achieve a result that is as close as possible to what was expected [1]. In other words, what is most valued is the ability to adapt to changes, to face unforeseen events, to make the best decisions regarding a reality that is imposed as the project progresses. On the other hand, those of us who dedicate ourselves to IT projects have the tendency to cling to the tools that gave us the best results, although many times they are not the most appropriate for the case or, if they are, we continue to…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSoftware Engineering Techniques and Practices
