Trust dynamics in global software engineering
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
The agile requirements refinery: Applying SCRUM principles to software product management
Information and Software Technology
1st international requirements engineering efficiency workshop: REEW 2011
ACM SIGSOFT Software Engineering Notes
Empirical Software Engineering
Release planning with feature trees: industrial case
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
International Journal of Information Management: The Journal for Information Professionals
Improving software product management: a knowledge management approach
International Journal of Business Information Systems
A taxonomy for requirements engineering and software test alignment
ACM Transactions on Software Engineering and Methodology (TOSEM)
The lean gap: A review of lean approaches to large-scale software systems development
Journal of Systems and Software
| Hi-index | 0.00 |
Requirements engineering focuses on good specification practices but has yet to find working solutions for effective requirements communication. Inadequate communication and tacit assent to a demanding customer's requests make it hard to fully understand a project's requirements. A negotiation process, called handshaking with implementation proposals, has been used to communicate requirements effectively—even in situations where almost no written requirements exist and where distance separates the customer from developers. Handshaking is an efficient, flexible technique that uses architectural options to understand requirements, to make implementation decisions that create value, and to establish the foundation for a stable project. This article describes the communication challenges, solutions, and lessons learned in developing the handshaking process and applying it in industrial practice.