Reflective systems development
Scandinavian Journal of Information Systems
The 4+1 View Model of Architecture
IEEE Software
Empirical Software Engineering
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
External experiments: a workable paradigm for collaboration between industry and academia
Lecture notes on empirical software engineering
Formulation and preliminary test of an empirical theory of coordination in software engineering
Proceedings of the 9th European software engineering conference held jointly with 11th ACM SIGSOFT international symposium on Foundations of software engineering
Extreme Programming Refactored: The Case Against XP
Extreme Programming Refactored: The Case Against XP
Extreme Programming Explained: Embrace Change (2nd Edition)
Extreme Programming Explained: Embrace Change (2nd Edition)
AGILE '06 Proceedings of the conference on AGILE 2006
Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series)
Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series)
The Social Nature of Agile Teams
AGILE '07 Proceedings of the AGILE 2007
The influence of organizational structure on software quality: an empirical case study
Proceedings of the 30th international conference on Software engineering
Empirical studies of agile software development: A systematic review
Information and Software Technology
The Role of Deliberate Artificial Design Elements in Software Engineering Experiments
IEEE Transactions on Software Engineering
The software project manager's bridge to agility
The software project manager's bridge to agility
Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum
The repertory grid technique: Its place in empirical software engineering research
Information and Software Technology
IEEE Software
Challenges in enterprise software integration: An industrial study using repertory grids
ESEM '09 Proceedings of the 2009 3rd International Symposium on Empirical Software Engineering and Measurement
A comparison of model-based and judgment-based release planning in incremental software projects
Proceedings of the 33rd International Conference on Software Engineering
Information and Software Technology
Testing highly complex system of systems: an industrial case study
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
Interpretative case studies on agile team productivity and management
Information and Software Technology
Hi-index | 0.00 |
Applying agile methodology in large software development projects introduces many challenges. For example, one may expect that the combination of autonomous teams and the necessity for an overall organizational control structure may lead to conflicts, and one may expect that Agile's informal means of knowledge sharing breaks down as the number of project participants increases. Such issues may in turn compromise the project's productivity. In order to better understand potential threats to productivity in large agile development projects, we conducted repertory grid interviews with 13 project members on their perceptions of threats to productivity. The project was a large software development project consisting of 11 Scrum teams from three different subcontractors. The repertory grid sessions produced 100 issues, which were content analyzed into 10 main problem areas: (1) Restraints on collaboration due to contracts, ownership, and culture, (2) Architectural and technical qualities are given low priority, (3) Conflicts between organizational control and flexibility, (4) Volatile and late requirements from external parties, (5) Lack of a shared vision for the end product, (6) Limited dissemination of functional knowledge, (7) Excessive dependencies within the system, (8) Overloading of key personnel, (9) Difficulties in maintaining well-functioning technical environments, (10) Difficulties in coordinating test and deployment with external parties. Using critical-case reasoning, we claim that projects deploying agile practices in projects with less favorable conditions than those enjoyed in the current project, and that are larger and more complex, are likely to face similar challenges.