Normal view MARC view

Why do we rework? Organizational dyadic interactions and design rework in software development

Author: Sosa, Manuel INSEAD Area: Technology and Operations Management Series: Working Paper ; 2009/50/TOM Publisher: Fontainebleau : INSEAD, 2009.Language: EnglishType of document: INSEAD Working PaperAbstract: Rework is the (full or partial) repetition of tasks due to newly available information. Actors engage in design rework when they realize that previously made assumptions were incorrect and certain corrective action needs to be taken. We study rework at the dyadic level: What characterizes organizational dyadic interactions that make one realize the need to carry out rework? We investigate how knowledge and social network attributes of dyadic interactions trigger the realization of the need to rework. Hypotheses are tested in a sociometric study conducted within the development department of a software company.
Tags: No tags from this library for this title. Log in to add tags.
Item type Current location Collection Call number Status Date due Barcode Item holds
INSEAD Working Paper Asia Campus
Archives
Print Available BC008862
INSEAD Working Paper Europe Campus
Archives
Print Available BC008861
Total holds: 0

Rework is the (full or partial) repetition of tasks due to newly available information. Actors engage in design rework when they realize that previously made assumptions were incorrect and certain corrective action needs to be taken. We study rework at the dyadic level: What characterizes organizational dyadic interactions that make one realize the need to carry out rework? We investigate how knowledge and social network attributes of dyadic interactions trigger the realization of the need to rework. Hypotheses are tested in a sociometric study conducted within the development department of a software company.

Do not digitize

There are no comments for this item.

Log in to your account to post a comment.
Koha 18.11 - INSEAD Catalogue
Home | Contact Us | What's Koha?