The role of boundary objects in the fuzzy front end of IT development
- Publication Type:
- Conference Proceeding
- Citation:
- Proceedings of the Australian Software Engineering Conference, ASWEC, 2014, pp. 162 - 169
- Issue Date:
- 2014-01-01
Closed Access
| Filename | Description | Size | |||
|---|---|---|---|---|---|
| 06824121.pdf | Published version | 203.58 kB |
Copyright Clearance Process
- Recently Added
- In Progress
- Closed Access
This item is closed access and not available.
Different domains develop their own world views making collaboration between subject matter experts difficult. Despite the difficulties, IT project personnel routinely manage to establish common understanding. Documented software development methodologies say little about how that common understanding emerges or what might aid better understanding. This research sought to determine how people of diverse world views communicated their ideas and how they established that they had been understood. Of particular interest was the relevance and operation of boundary objects. The investigation quickly revealed that innovative problems required more abstract boundary objects over which different stakeholders could exchange meaningful understanding but that assuring understanding had been accomplished was invariably reflected explanation. The findings have implications for software development methodologies, pointing out a need for more awareness of a range of boundary objects when understanding must be achieved between diverse stakeholders such as business owners and IT specialists. © 2014 IEEE.
Please use this identifier to cite or link to this item: