Agile Development at ABC - What Went Wrong?
Explore this paper's citation graph
Summary
It appears that lack of firm leadership commitment to agile, absence of a clearly defined customer to provide clearly defined requirements or push for additional software capabilities, failure to provide adequate initial or ongoing training and support to the organization as a whole, and underestimating the change management requirements were contributing factors to ABC’s struggles with implementing agile methods.
- Type
- article
- Published
- 2011-01-01
- Cited by
- 5
- References
- 18
- OpenAlex
- https://openalex.org/W27942552
- Semantic Scholar
- https://api.semanticscholar.org/CorpusID:18539362
Keywords
Agile software development, Agile usability engineering, Process management, Agile Unified Process, Lean software development
References
- Manifesto for Agile Software Development
- Scaling Software Agility: Best Practices for Large Enterprises (The Agile Software Development Series)
- An Empirical Study Examining the Usage and Perceived Importance of XP Practices
- The managerialistic ideology of organisational change management
- Primavera gets agile: a successful transition to agile development
- Future of scrum: parallel pipelining of sprints in complex projects
- Get Ready for Agile Methods, with Care
- An Analytical Survey of "On-Site Customer" Practice in Extreme Programming
- A Dynamic Framework for Classifying Information Systems Development Methodologies and Approaches
- Agile Software Development: The Business of Innovation
- Agile Requirements Engineering Practices: An Empirical Study
- Extreme Programming Explained
- Key Issues in Information Systems Management : An International Perspective
Cited by
- RE-CONCEPTUALIZING AGILE INFORMATION SYSTEMS DEVELOPMENT USING COMPLEX ADAPTIVE SYSTEMS THEORY
- Scrum Abandonment in Distributed Teams: A Revelatory Case
- Agile Software Engineering Practices and ERP: Is a Sprint too Fast for ERP Implementation
- Modeling the Dynamics of an Agile Scrum Team in the Development of a Single Software Project
- Evaluating Agile and Lean Software Development Methods from a System Dynamics Perspective