Match!

Agile requirements: opportunity or oxymoron?

Published on May 1, 2004in IEEE Software2.945
· DOI :10.1109/MS.2004.1293075
K. Orr1
Estimated H-index: 1
Abstract
We show that, in today's world, a requirement without agility is just as bad as agility without requirements. We have discovered a consensus that systems analysis and requirements definition, in particular, have fallen on hard times. Ten or 15 years ago we taught people structured analysis, information engineering, data modeling, and working with computer-aided software engineering tools to turn those requirements into running programs. Rather than understanding the user's business and information needs, some agile approaches attempt to give users what they say they want as quickly as possible. Every system of consequence needs good requirements. Without good requirements, the project risks increase dramatically. The better the requirements, the better people understand what they're trying to build (or acquire).
  • References (0)
  • Citations (38)
📖 Papers frequently viewed together
2003
3 Authors (F. Paetsch, ..., Frank Maurer)
320 Citations
795 Citations
2001
1,858 Citations
78% of Scinapse members use related papers. After signing in, all features are FREE.
References0
Newest
Cited By38
Newest
#1Mohamad KassabH-Index: 12
#2Joanna DeFrancoH-Index: 4
Last. Valdemar Vicente Graciano Neto (UFG: Universidade Federal de Goiás)H-Index: 5
view all 3 authors...
Agile development practices have become widely accepted as an effective project management approach in order to have rapid delivery of high-quality software. As with traditional waterfall projects, effective communication is also a necessity for the success of an agile project. However, the agile principles set a different tone for project development. The difference in tone is also reflected on how requirements are captured, analyzed and communicated under the agile umbrella. Little contemporar...
Source
#1Mohamad Kassab (PSU: Pennsylvania State University)H-Index: 12
#2Giuseppe DestefanisH-Index: 12
Estimating the effort is an important task in software project management. A realistic effort estimation right from the start in a project gives the project manager confidence about any future course of action, since many of the decisions made during development depend on, or are influenced by, the initial effort estimations. Nevertheless, little contemporary data exists for documenting actual practices of software professionals for requirements effort or size estimation. We have conducted an ex...
Aug 1, 2015 in SEAA (Software Engineering and Advanced Applications)
#1Ville T. Heikkila (UVic: University of Victoria)H-Index: 11
#2Daniela Damian (UVic: University of Victoria)H-Index: 33
Last. Maria Paasivaara (Aalto University)H-Index: 20
view all 4 authors...
Agile software development (ASD) methods have gained popularity in the industry and been the subject of an increasing amount of academic research. Although requirements engineering (RE) in ASD has been studied, the overall understanding of RE in ASD as a phenomenon is still weak. We conducted a mapping study of RE in ASD to review the scientific literature. 28 articles on the topic were identified and analyzed. The results indicate that the definition of agile RE is vague. The proposed benefits ...
32 CitationsSource
#1Mohamad Kassab (PSU: Pennsylvania State University)H-Index: 12
Even though there is ample information available on solid requirements engineering practices, anecdotal evidence still indicates poor practices in industry. The key issue in implementing an improvement is to first identify the areas that need most improvement. Three surveys were conducted in 2003, 2008 and 2013 on the state of practice of requirements engineering. Surveys data obtained includes characteristics of projects, practices, organizations, and practitioners related to requirements engin...
24 CitationsSource
#1David GibbsH-Index: 1
#1Daniel DresnerH-Index: 1
#2Joy GarfieldH-Index: 4
Failing to elicit requirements is as much of a risk in the traditional, negative sense as successfully defining requirements is a positive step towards successful systems development. The discipline of risk management has long since had to deal with the spectre of emergent risk and its inherent lack of predictability. Just as risk management considers how any number of vulnerabilities in a system may be exploited by accident or by malicious intent that preys upon exposure to otherwise independen...
Aug 1, 2014 in SEAA (Software Engineering and Advanced Applications)
#1Mohamad Kassab (PSU: Pennsylvania State University)H-Index: 12
Collecting, understanding, and managing requirements are critical aspects in all development methods including agile methods as well. Nevertheless, little contemporary data exists for document actual practices of software professionals for software requirements engineering activities in agile environments. To remedy this deficiency and provide useful data to other researchers we conducted a survey study that drew participants from wide range of professions, industries and geographic locations. W...
10 CitationsSource
#1Daniel Dresner (University of Manchester)H-Index: 1
#2Joy GarfieldH-Index: 4
The tendency to throw controls at perceived and real system vulnerabilities, coupled with the likelihood of these controls being technical in nature, has the propensity to favour security over usability. However there is little evidence of increased assurance and it could encourage work stoppages or deviations that keep honest users from engaging with the system. The conflicting balance of trust and controls, and the challenge of turning that balance into clear requirements, creates an environme...
2 Citations
The Vortex of Continuous Development of Embedded Systems: An Inquiry into Agility Orchestration BY David Anthony Bishop May 6, 2014 Committee Chair: Richard Baskerville Major Academic Unit: Robinson College of Business Agile methodologies have become a popular and widely accepted method for managing software development. Since the inception of the Agile Manifesto over ten years ago, agile development techniques have superseded waterfall methods in many, if not most, software development organiza...
#1Zia Ur RehmanH-Index: 1
view all 6 authors...
One of the key measures of the adaptability of a wander is its ability to attain satisfaction on time and on arrangement, paying little personality to the turbulent and sketchy environment it may work inside. Cost estimation and emulating are in this way key when making a system. Cost estimation has long been a testing errand in structures change and despite the way that much examine has watched standard schedules, little is contemplated estimation in the quick framework stadium. This is surpris...