Extreme programming explained: embrace change
Extreme programming explained: embrace change
Agile Software Development with Scrum
Agile Software Development with Scrum
The Scrum Software Development Process for Small Teams
IEEE Software
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Towards requirements-driven information systems engineering: the Tropos project
Information Systems - The 13th international conference on advanced information systems engineering (CAiSE*01)
ER '02 Proceedings of the 21st International Conference on Conceptual Modeling
Towards Modeling and Reasoning Support for Early-Phase Requirements Engineering
RE '97 Proceedings of the 3rd IEEE International Symposium on Requirements Engineering
Modelling strategic relationships for process reengineering
Modelling strategic relationships for process reengineering
Reducing wasted development time via continuous testing
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
Nonfunctional Requirements: From Elicitation to Conceptual Models
IEEE Transactions on Software Engineering
From Goals to Aspects: Discovering Aspects from Requirements Goal Models
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Agile, open source, distributed, and on-time: inside the eclipse development process
Proceedings of the 27th international conference on Software engineering
The Effect of Pairs in Program Design Tasks
IEEE Transactions on Software Engineering
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
| Hi-index | 0.00 |
Agile software development methods suggest that sharing tasks between a pair of developers has advantages over letting them work as individuals. This effect has been observed in designing and coding tasks too. However, it is not yet known whether or not pairing on requirements engineering tasks could deliver a similar benefit at an early phase of software projects. Based on first-hand experience in pairing development of the OpenOME tool, we analyse the evolving stakeholder requirements using the i*/Tropos method. Our findings show that sharing tasks of different roles becomes more effective when those roles are played by one stakeholder, possibly due to smaller communication delay at a shorter distance.